Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
agwa
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
88 ms
·
961.
▲
by
agwa
12y ago
It is my privacy, and just because a private building owner can legally violate that privacy doesn't mean that they should or must[1], or that the users of that building shouldn't question the stated reasons that their privacy is
962.
▲
by
agwa
12y ago
OK, how about comparing the rate of property crime in buildings using traditional, non-electronic locks, with buildings using electronic locks that track access? The point here is that so far no evidence has been put forward to support all
963.
▲
by
agwa
12y ago
No, it's asking them to prove a positive. CSAIL has been using the card system for 10 years now. If logging card access has all the pubic safety benefits that proponents claim it has, it should be possible to point to "criminals
964.
▲
by
agwa
12y ago
Those are a lot of hypotheticals. As RMS said in his article: > Such claims must be put to the test. The NSA claimed that surveilling everyone in the US was vital for preventing terrorism. When it had to give details, it became clear t
965.
▲
by
agwa
12y ago
The most obvious example of why Debian is an OS, not a "Linux distro," is because you can install the kfreebsd architecture and then you're not using Linux at all.
966.
▲
by
agwa
12y ago
Ouch. Stuff like this is just a confused deputy security vulnerability waiting to happen. Whenever I write code to fetch a resource based on user input (and a crawler following a link is a form of user input) I check to make sure I'm
967.
▲
by
agwa
12y ago
> the indexed result pages are http:// not https:// - but to my knowledge google forces https:// everywhere. Google only forces HTTPS for certain User-Agent strings. I just tried fetching http:/
968.
▲
by
agwa
12y ago
> They'll be so flush with money that the only reasonable way to use it will be to do their own series 'A'. The other way to use that money would be to have gigantic batches. Remember, pg and sama have said that they'
969.
▲
by
agwa
12y ago
Thanks for checking it out! Yeah, it's really just a matter of documenting the API ;-) Unfortunately it does rely on being able to receive an email, as this is a requirement of virtually all certificate authorities, though the email a
970.
▲
by
agwa
12y ago
I'm working on this problem: https://sslmate.com/ Right now it's just a command line client, but a public API is in the works. And this week we'll be announcing a solution to the cert rotation problem (basic
971.
▲
by
agwa
12y ago
First, it requires more than just a request flag, since that flag only affects the signature algorithm in your certificate signing request. Your certificate authority has to actually support signing certificates with SHA-2, and also needs
972.
▲
by
agwa
12y ago
I think you're putting too much faith in blocking third party cookies. Through collusion with Google (such as an IFRAME or JSONP), sites can get your Google ID from your Google cookie without needing to consult your IP address or use
973.
▲
by
agwa
12y ago
Don't read too much into the fact that they own restaurants. They are probably very small businesses and don't make much money. They're likely sole proprietorships or general partnerships so they aren't a separate lega
974.
▲
by
agwa
12y ago
I'm not sure why websites would even care what IP address you're coming from if they've got a cookie, which provides an even stronger way to track you. They might care what the network prefix is, since that would identify yo
975.
▲
by
agwa
12y ago
If you're letting yourself be tracked through your web browser, it really doesn't matter what IP address you use.
976.
▲
by
agwa
12y ago
Almost everything involving a bank costs money. Checking accounts have both monthly fees and overdraft fees. Check books cost money. If you're well-off, as virtually all HN commenters are, the fees aren't a big deal or they
977.
▲
by
agwa
12y ago
Because even with traditional privacy addresses, the first 64 bits of your address never change, and you can be tracked that way. If you happen to share those first 64 bits with many other people, then privacy addresses provide value, but
978.
▲
by
agwa
12y ago
> C++11 certainly introduced very few necessary features I have to ask whether you've actually done any significant amount of programming in C++, both C++11 and pre-C++11.
979.
▲
by
agwa
12y ago
The proper solution is Stable Privacy addresses, recently standardized in RFC7217 [1]. The interface ID is essentially hash(secret || prefix || mac-address), so it stays the same when you're on the same network, but changes as soon as
980.
▲
by
agwa
12y ago
Will www.google.com continue to be available over HTTP? If so, the old browsers will still be able to use Google search by simply avoiding HTTPS. That would lessen the impact on Google, in contrast to sites that follow best practice and u
981.
▲
by
agwa
12y ago
> choice between "HTTPS being secure" and "supporting insanely old/insecure software", I think there are really three outcomes: 1. HTTPS is widely used, it's secure, insanely old/insecure software is no
982.
▲
by
agwa
12y ago
Is it possible to specify both a RSA-SHA1 cert and a RSA-SHA256 cert that way, or would it have to be RSA-SHA1 and ECDH-SHA256? Apache/OpenSSL would have to assume that pre-TLSv1.2 clients support only SHA1 because there's no sign
983.
▲
by
agwa
12y ago
And the upcoming version (which is overdue--I've been busy) will support encrypting with GPG with multiple recipients, like BlackBox.
984.
▲
by
agwa
12y ago
There's no solution exactly like HSTS, though DANE+DNSSEC provides a solution to the downgrade (and cert validation) problem. Postfix has an implementation. Unfortunately it requires DNSSEC, which has issues. Also, EFF is working on
985.
▲
by
agwa
12y ago
The downgrade concern mentioned in the post is moot with server-to-server SMTP because we have to intentionally allow downgrades to account for old mail servers. The other concerns with STARTTLS still apply to server-to-server SMTP, but sin
986.
▲
by
agwa
12y ago
Thankfully, setuid() no longer fails on Linux because of RLIMIT_NPROC, as of 2011[1]. Still, I agree with you 100%: check your syscall return values, especially security-critical syscalls like setuid! [1] http://lwn.net/Art
987.
▲
by
agwa
12y ago
Sometimes there are legitimate reasons for relying on the CWD, such as avoiding time-of-check/time-of-use race conditions. The *at syscalls provide a better alternative, but (at least as of a few years ago) they weren't widely im
988.
▲
by
agwa
12y ago
I have the 4th edition of C++PL, and while I haven't read it cover to cover (it is long ) the parts I've read have been excellent and definitely meet or exceed the standards of the earlier editions.
989.
▲
by
agwa
12y ago
Adopting HTTPS is very important for the Web, but the lack of HTTPS in this case is just a red herring. The real problem is that it's way too easy to exploit systems through the web browser. If the entire Web switched to HTTPS, gover
990.
▲
by
agwa
12y ago
Yes, the point about downgrades is moot when it comes to server-to-server SMTP, since downgrades have to be allowed to be interoperable. The downgrade problem isn't moot with other protocols (like IMAP or client-to-server SMTP) which a
More ›