A simple slice OOB causes a panic - this is why many robust servers will catch & recover so a single OOB due to bug triggered by rare input/state doesn’t crash the server for 1000’s of users. It might still cause problems due to resource exhaustion, but properly designed exception/error handling should prevent/limit that.
> On Feb 24, 2021, at 5:29 PM, Kevin Chadwick <m8il1i...@gmail.com> wrote: > > On February 24, 2021 11:16:46 PM UTC, robert engels <reng...@ix.netcom.com> > wrote: >> I’m sorry but that is not correct. If you have a “server process” that >> handles requests for 1000’s of clients - terminating the process due to >> an exception/panic easily leads to a DoS attack. The bad actor only >> needs to send similar requests infrequently to affect thousands of >> users - especially with round-robin servicing - you can take down >> 1000’s of servers with 1:1 requests. >> > > I figured after that I should have more politely said that. I am not sure > what scenario you are thinking of but it doesn't apply to what I am doing. > > Panics should not be triggerable by external influences, in any case. > > -- > 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/CDB3583B-6171-4025-B635-CC680FDDDF0D%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/E3AE3FB6-A7D6-4539-A07E-8E5A71AA30D0%40ix.netcom.com.
