News for hackers. Stuff that matters.
Re:A survey of BSD kernel vulnerabilities [pdf] by tedunangst on Thursday July 27, 2017 @11:06PM (#14871637)
There are numbers greater than zero and less than 20.
Re:A survey of BSD kernel vulnerabilities [pdf] by RJIb8RBYxzAMX9u on Friday July 28, 2017 @12:25AM (#14871954)
And there's the Chinese proverb, roughly translated and paraphrased: "solder who ran away 50 paces mocks another who ran 100 paces for his cowardice" [0].

I get it, preventing local privilege escalation on *NIX is hard, and I appreciate OpenBSD's focus and stance on security, v.s. say Linus's more laid-back attitude. And having arguably fewest of them is an achievement, even if it's not zero. Let's focus on making OpenBSD better and not belittling other's shortcomings.

[0] https://zh.wikipedia.org/zh/%E4%BA%94%E5%8D%81%E6%AD%A5%E7%A...

Re:A survey of BSD kernel vulnerabilities [pdf] by 43224gg252 on Friday July 28, 2017 @09:24AM (#14874054)
Does OpenBSD have so few vulnerabilities because no one looks for them (compared to Linux/Windows) or because it's actually more secure?

I have an OS I coded my self that no one has ever found a vulnerability on.

Re:A survey of BSD kernel vulnerabilities [pdf] by ender341341 on Friday July 28, 2017 @01:32PM (#14875981)
I would imagine that it's a bit of both, but 1 point of comparison in OpenBSD's favor would be libressl vs openssl, the number & severity of issues in the OpenBSD maintained project has been significantly lower.
Re:A survey of BSD kernel vulnerabilities [pdf] by nopcode on Monday July 31, 2017 @10:34PM (#14897509)
I was at the defcon presentation & talked with Ilja after.

The answer is a bit of both.

Re:A survey of BSD kernel vulnerabilities [pdf] by snikeris on Friday July 28, 2017 @03:30PM (#14876853)
No one can answer this question.
Re:A survey of BSD kernel vulnerabilities [pdf] by calebl on Friday July 28, 2017 @01:03AM (#14872105)
FYI, since you're here: visiting your site on FF in Windows 10 is throwing an insecure error, saying you're using an invalid certificate. 100% possible that's somehow an error on my end - but just in case it isn't, thought you'd want to know. Sample URL throwing it: https://www.tedunangst.com/flak/post/books-chapter-three

Side note: I'm hugely grateful for all your work on OpenBSD.

Re:A survey of BSD kernel vulnerabilities [pdf] by ams6110 on Friday July 28, 2017 @01:39AM (#14872224)
Same in FF on Mac OS X:

www.tedunangst.com uses an invalid security certificate. The certificate is not trusted because the issuer certificate is unknown. The server might not be sending the appropriate intermediate certificates. An additional root certificate may need to be imported.

Error code: SEC_ERROR_UNKNOWN_ISSUER

And in Chrome:

Attackers might be trying to steal your information from www.tedunangst.com (for example, passwords, messages, or credit cards). NET::ERR_CERT_AUTHORITY_INVALID

Re:A survey of BSD kernel vulnerabilities [pdf] by vancan1ty on Friday July 28, 2017 @02:04AM (#14872311)
Despite the browsers' dire warnings, you are still far more protected visiting a website with a self-signed certificate than visiting a plain http website.
Re:A survey of BSD kernel vulnerabilities [pdf] by JdeBP on Friday July 28, 2017 @03:18PM (#14876761)
M. Unangst xyrself said:

> Yesterday, reading this page in plaintext was perfectly fine, but today, add some AES to the mix, and it’s a terrible menace, unfit for even casual viewing.

-- https://www.tedunangst.com/flak/post/moving-to-https

Re:A survey of BSD kernel vulnerabilities [pdf] by j_s on Friday July 28, 2017 @02:41AM (#14872435)
Not sure how well this stacks up against automating LetsEncrypt these days.
Re:A survey of BSD kernel vulnerabilities [pdf] by vancan1ty on Friday July 28, 2017 @03:04AM (#14872514)
March 24, 2017 -- "During the past year, Let's Encrypt has issued a total of 15,270 SSL certificates that contained the word 'PayPal' in the domain name or the certificate identity. Of these, approximately 14,766 (96.7%) were issued for domains that hosted phishing sites" [1]

LetsEncrypt isn't perfect either. You've got to be cognizant of what details you are sharing over the connection, regardless of who signs the certificate.

[https://it.slashdot.org/story/17/03/25/2222246/over-14k-lets...]

Re:A survey of BSD kernel vulnerabilities [pdf] by j_s on Friday July 28, 2017 @03:22AM (#14872579)
I agree!

> You've got to be cognizant of what details you are sharing over the connection, regardless of who signs the certificate.

So why not cut out the browser errors, for free? Somehow this vaguely feels like Don Quixote straining hard to hold onto the original definition of the term "hacker".

Props to this guy for sticking to his beliefs; I don't mean for this to be interpreted as saying anything should be changed.

Re:A survey of BSD kernel vulnerabilities [pdf] by dchest on Friday July 28, 2017 @06:16AM (#14873192)
There's no reason phishing sites shouldn't have encrypted connection. Case closed.
Re:A survey of BSD kernel vulnerabilities [pdf] by ams6110 on Friday July 28, 2017 @02:13AM (#14872347)
more protected from what?
Re:A survey of BSD kernel vulnerabilities [pdf] by vancan1ty on Friday July 28, 2017 @02:30AM (#14872395)
- protected from third parties reading the data in transit

- protected from alteration of the data in transit without either end's knowledge

and, IF you have a means to authenticate the owner of the certificate outside of the regular certificate signing process

- protection from impersonation of the other end of the connection

Re:A survey of BSD kernel vulnerabilities [pdf] by vancan1ty on Friday July 28, 2017 @02:33AM (#14872405)
my point is that TLS can still be useful without the participation of a certificate authority. but you have to be careful.
Re:A survey of BSD kernel vulnerabilities [pdf] by ams6110 on Friday July 28, 2017 @10:32AM (#14874497)
Right. I've visited Ted's site in the past, and had no certificate warnings. Now, suddenly, I am getting warnings. So isn't that the exact scenario in which I should be very suspicious?

It's just a blog; I'm not submitting anything, but still it's an indicator that something fishy might be going on.

Re:A survey of BSD kernel vulnerabilities [pdf] by danieldk on Friday July 28, 2017 @02:16AM (#14872356)
Re:A survey of BSD kernel vulnerabilities [pdf] by patrec on Friday July 28, 2017 @01:14AM (#14872139)
Given that one is one of the the most widely used OSs in the world and one is a fringe OS, which surely must affect likelihood of detection, I'm not sure any number above zero makes this a favorable comparison for OpenBSD.
Re:A survey of BSD kernel vulnerabilities [pdf] by Crontab on Friday July 28, 2017 @05:51AM (#14873118)
Ted: I wanted to let you know that the one-page archive listing on Flak is no longer working.