News for hackers. Stuff that matters.
Re:OpenBSD Recent Security Innovations by rurban on Thursday June 06, 2019 @12:36AM (#20111628)
Totally uncool and a dead end. Nobody else will do it that way. "The promises argument is specified as a string, with space separated keywords". caps as strings to be tokenized at runtime are slow, insecure and not validated at compile-time. Never trust a parser in core. This needs to be a bitmask of course. Don't let ruby programmers add OS API's.
Re:OpenBSD Recent Security Innovations by gpvos on Thursday June 06, 2019 @12:50AM (#20111682)
The intended ad hominem in the last sentence does very much not apply.
Re:OpenBSD Recent Security Innovations by unixhero on Thursday June 06, 2019 @02:57AM (#20112199)
Nah no ad hominem taken! I thought it was funny. I write Ruby, and love it, and wouldn't go near OS API design with a tenth foot pole.
Re:OpenBSD Recent Security Innovations by jabot on Thursday June 06, 2019 @04:18AM (#20112556)
That's about 3cm. Pretty close ;-)
Re:OpenBSD Recent Security Innovations by gpvos on Thursday June 06, 2019 @05:37AM (#20112935)
I wouldn't touch it, but watching it up close is quite interesting.
Re:OpenBSD Recent Security Innovations by ksec on Thursday June 06, 2019 @02:56AM (#20112196)
What has it got to do with Ruby ?
Re:OpenBSD Recent Security Innovations by rurban on Thursday June 06, 2019 @07:33AM (#20113477)
Just an example. Could be perl also, but ruby was the fashion then.
Re:OpenBSD Recent Security Innovations by enriquto on Thursday June 06, 2019 @03:55AM (#20112451)
> Never trust a parser in core.

So, we have to part ways with our dear printk ?

Re:OpenBSD Recent Security Innovations by rurban on Thursday June 06, 2019 @07:34AM (#20113488)
That would be fantastic, sure. It's a security nightmare. Know about the printf_s extensions? Maintainability?