Hacker GitHub

← All repos

g0tmi1k/debian-ssh

View on GitHub ↗ ★ 410 Shell

Debian OpenSSL Predictable PRNG (CVE-2008-0166)

9 mentions on Hacker News by 8 people: 0 stories, 9 comments · first 2017-08-02 · latest 2025-05-14

Mentions per year 9 mentions · busiest year 2018 (2)
20082026
  1. …missed heartbleed entirely Missed it? Not at all, Debian pioneered that style of bugs years before! https://github.com/g0tmi1k/debian-ssh
    comment by rs_rs_rs_rs_rs · 2025-05-14 · in Multiple security issues in GNU Screen
  2. Ouch, that one's bad: https://github.com/g0tmi1k/debian-ssh#the-bug >These lines were removed because they caused the Valgrind and Purify tools to produce warnings about the use of uninitialized data in any code that was linked to OpenSSL.…
  3. CVE-2008-0166 It was really bad. https://github.com/g0tmi1k/debian-ssh
  4. …thinks they can improve the software. That lead to things like removing randomness from SSH keys: https://github.com/g0tmi1k/debian-ssh
    comment by alphager · 2023-10-08 · in Why is Debian the way it is?
  5. …software work better with the Debian way of configuring things; sometimes much more catastrophic: https://github.com/g0tmi1k/debian-ssh
  6. I would have thought https://github.com/g0tmi1k/debian-ssh would be the most famous issue in many people's memories of poor (read: absent) PRNG use. ;)
  7. …vulnerabilities into software too. The famous Debian SSH key generation issue comes to mind. https://github.com/g0tmi1k/debian-ssh
    comment by shittyadmin · 2018-08-20 · in Flatpak 1.0 Released, Ready for Prime Time
  8. …not heard of this one before. There are real world risks associated with spurious warnings. [1]: https://github.com/g0tmi1k/debian-ssh
  9. Not even the maintainers really understand what they are doing : https://github.com/g0tmi1k/debian-ssh > There was an #ifndef PURIFY there for a reason. It's because the openssl authors knew that line would cause trouble in a memory…
    comment by Ltfe · 2017-08-02 · in ⁠Btrfs has been deprecated in RHEL