A panic is not a security issue. Memory corruption/stack overflow is. In Go the latter is accomplished through CGo and unsafe pointers/operations.
Continuous panics can be considered a security issue as a DoS attack but IMO at least there are many ways to generate continuous errors that are similar (and are best mitigated through external controls/monitoring). > On Jan 13, 2021, at 7:59 AM, Kevin Chadwick <m8il1i...@gmail.com> wrote: > > On 1/13/21 11:17 AM, Axel Wagner wrote: >> Assuming generics like interfaces, potentially erode type safety. >> >> >> Can you elaborate? Because that statement seems exactly contrary to >> established >> wisdom. > > Clearly Go without interfaces, especially an empty interface is safer. Perhaps > Generics reduce that risk via constraints etc.? > >> How many security issues and/or production panics to date might have been >> avoided by avoiding interface use all together? >> >> >> I assume panics in production are sufficiently common > > Really. If you avoid interfaces and pointers. Is it even possible to > panic...maybe with channels. I don't use exceptions personally. Perhaps that > is > what you mean? > > I'm not trolling or anything. I just feel that a risk analysis section by > those > that understand all the details, might be useful to people, before deciding > on a > thumbs up or down? > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/5274cf02-a9a7-357d-e498-b979c1b02f15%40gmail.com. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/C5D91D76-A284-421E-AF91-CDCF2ABF211B%40ix.netcom.com.