Hacker Newsnew | past | comments | ask | show | jobs | submit | efficientarch's commentslogin

The title change of this submission means that many early comments now make no sense. Original title was something like "Ask HN: Is anything like this available as open source"


Thanks, wouldn't have caught it otherwise.

To whoever changed it: why didn't you just make a second thread?


I think it's the historic actions of the person rather than their ideas that are bothering people. But I can't speak for them, of course.


Also see this explanation from Troy Hunt, which hasn't made the front page. https://news.ycombinator.com/item?id=7558597


TL, DR:

Troy Hunt: ”The Heartbleed bug itself was introduced in December 2011, in fact it appears to have been committed about an hour before New Year’s Eve (read into that what you will). The bug affects OpenSSL version 1.0.1 which was released in March 2012 through to 1.0.1f which hit on Jan 6 of this year. The unfortunate thing about this timing is that you’re only vulnerable if you’ve been doing “the right thing” and keeping your versions up to date! Then again, for those that believe you need to give new releases a little while to get the bugs out before adopting them, would they really have expected it to take more than two years? Probably not.”


Debian squeeze (oldstable) is not vulnerable, because it's still running 0.9.8o-4squeeze14.

0.9.8o was released 2010-06-01, almost 4 years ago!


http://patch-tracker.debian.org/package/openssl/0.9.8o-4sque...

It's had a lot of security fixes backported to it in the four years since the upstream release.


Respectfully disagree. The only ones that will be upvoted a lot will presumably be the funny ones, not the lame ones.


This is a thoughtful comment and a model of how to disagree on Hacker News. Thank you.

I wish you were right, but I'm afraid you have an overly rosy view of upvotes. For example, https://news.ycombinator.com/item?id=7506762 shot to #1 in just a few minutes.


Speaking of moderation ideas, now that there is some new blood, here's another random one. I'm not sure it's any good, and it's kind of vague, but... how about if an article gets flagged enough, the upvoters are "named and shamed" in some (not highly visible) way. It might provide a small incentive to not vote for lame stuff.


It feels wrong to out people's votes, which are normally private. The objections I've been making to inappropriate comments are public only because the comments themselves are.


Fair enough. I wouldn't want my comment votes public, but I can't think of any stories where I would mind terribly. I could see reasonable people thinking otherwise, though.


I like the idea but I think it's probably too complex to implement fairly.


CERN using comic sans was hardly funny, yet it made the front page.


"Like all brilliant ideas, my solution is simple". Too modest.


Cogent article explaining bitcoin in layman's terms, in a balanced fashion.


Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: