- 273comments
- 73comments
- 85comments
- 164comments
- 13comments
- 32comments
- 279comments
- 418comments
- 105comments
- 14comments
- 3comments
- 240comments
- 380comments
- —discuss
- 14comments
- 28comments
- 452comments
- 38comments
- 24comments
- 12comments
- 7comments
- 14comments
- —discuss
- 37comments
- 9comments
- 19comments
- 96comments
- 151comments
- 118comments
- 1comments
Really commendable work fixing up the upstream python project. I don't think there's anything to be embarrassed about in the timeline.
I would prefer to do a super proper disclosure with coordinated release dates and everything. My first submitting to SourceHut security ML ended up making the vuln existence somewhat public before upstream ever knew.
HN hug of death, strikes again.
That might have been DNS, the website itself is on sourcehut pages. Should be fine now for a while.
I love sourcehut, and I can't really think anything to replace it. But here's my shot. It's a popular myth that independently from the project size, someone should always take the main stream product in the field than small projects because most of the people would use the main stream product and there's an higher chance that vulnerabilities get already exploited/recognized/fixed. Is that true or not? TL;DR: in the evaluation of such products (sourcehut but even self hosted stuff), should we also take account about the project history and the exposition to threats?
haven’t been properly rickrolled in years, wasn’t expecting that!
You're welcome!
Oh my God, it's OSC 8 again. Because copy-pasting an URI from the terminal window is so 2003, and goodness gracious, having to look at an actual URL instead of an arbitrarily inaccurate description of it? That's, like, 1993. When I wrote my variant of ansi2html, I aggressively stripped out every C0 and C1, and all of the possible APC/DCS/OSC/PM sequences.
Meanwhile, internal links between different parts of a man page still don't exist (unless you use GNU Info but seriously, I'd rather use lynx on a folder of HTML files instead).
OSC 8 hyperlinks are extremely useful for tables and other kinds of compact displays.
They're also extremely useful for introducing CVEs into terminal emulators; I think I've seen about 5 of those on HN — including one OSC sequence that would cause the terminal emulator to just straight up automatically launch the web browser with whatever URLs were sent its way, no prompts no nothing.
nitpick: typo "Vulnerabile" :)
Build logs are such a tricky attack surface; sanitizing arbitrary build output is practically impossible without breaking useful formatting. Always assume untrusted input.