Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
OrpheanBeholder
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
1.
▲
by
OrpheanBeholder
10y ago
> Matthew Green was _insistent_ about making an altcoin "Let me reiterate, I would 10,000x rather have put Zerocash in Bitcoin." - https://twitter.com/matthew_d_green/status/78154154453702656... &g
2.
▲
by
OrpheanBeholder
10y ago
I went and dug up where I had read Green talk about this and it turns out it was in a conversation with you. It seems you and him disagree, he says ZCash couldn't/wouldn't have happened in Bitcoin and you say it could. Is you
3.
▲
by
OrpheanBeholder
10y ago
Monero wasn't developed by a group of highly respected cryptographers and the privacy it offers is plausible deniability not zero knowledge.
4.
▲
by
OrpheanBeholder
10y ago
> Is this the one that forked off BitCoin due to differences centered around how it didn't make its investors/founders enough money You must be thinking of something else. Matthew Green has said he would have much rather got th
5.
▲
by
OrpheanBeholder
10y ago
According to Matthew Green, they tried for years to get this (or one of the earlier versions) into Bitcoin and Bitcoin weren't having it. Their options were to make an entirely new coin, with the problems you point out, or to let the c
6.
▲
by
OrpheanBeholder
10y ago
> (a) Previously unknown TOR endpoints get found out because they invariably are the source of vandalism and/or spam. The English Wikipedia uses the MediaWiki TorBlock extension to automatically block Tor exits from editing, it ha
7.
▲
by
OrpheanBeholder
10y ago
Okay, let's have a sensible conversation about your completely idle suggestion to create a new library in some other language, that would have to maintain compatibility with the OpenSSL API otherwise no one will use it, or rewrite ever
8.
▲
by
OrpheanBeholder
10y ago
Are you volunteering? Good luck and be sure not to repeat the various vulnerabilities that weren't related to memory safety.
9.
▲
by
OrpheanBeholder
10y ago
No one is claiming that LibreSSL has fixed all the OpenSSL bugs, the parent certainly didn't. LibreSSL has historically been vulnerable to less of the bugs than OpenSSL and, for a long time, none of the sev:high bugs.
10.
▲
by
OrpheanBeholder
10y ago
Some TLS implementations return a randomised date for the handshake anyway, which is why constraints works the way it does. TLS 1.3 killing it is just gravy. If you're worried about a caching proxy you can set the constraint to a URL t
11.
▲
by
OrpheanBeholder
10y ago
> There have been efforts to augment NTP with authentication, but they still assume a world where each client trusts one or more time servers absolutely. OpenNTPD has "constraints" where it makes HTTP requests (using TLS) to we
12.
▲
by
OrpheanBeholder
10y ago
ajacoutot@ and jasper@ work for m:tier.
13.
▲
by
OrpheanBeholder
10y ago
However, contrary to most articles titled with a question, this article is answering the question rather than posing it.
14.
▲
by
OrpheanBeholder
10y ago
The OpenBSD project doesn't have the resources to provide this so m:tier employs a couple of OpenBSD developers to provide this option for people who want it. Not sure what is embarrassing about this.
15.
▲
by
OrpheanBeholder
10y ago
Get the host fingerprints over TLS then? https://www.openbsd.org/anoncvs.html
16.
▲
by
OrpheanBeholder
10y ago
> A bit ironic openssh.com doesn't have HTTPS You can however access the release notes (or any other file/page from the website for that matter) over SSH using CVS $ cvs -d anoncvs@anoncvs.ca.openbsd.org:/cvs get w
17.
▲
by
OrpheanBeholder
10y ago
It was posted to the tarsnap-announce mailing list: http://mail.tarsnap.com/tarsnap-announce/msg00035.html
18.
▲
by
OrpheanBeholder
10y ago
LLVM doesn't support all the architectures that OpenBSD supports.
19.
▲
by
OrpheanBeholder
10y ago
OWS quite often use anarchist figures and quotes in their example images for blog posts, this is nothing new.
20.
▲
by
OrpheanBeholder
10y ago
Some of these don't make sense. The point of bcrypt, scrypt, and pbkdf2 is the difficulty of them is configurable. Digging into the comments on that gist, it says that the bcrypt benchmark used a workfactor of 5 (= 32 rounds). The lowe