pfg

41 ms·

331.
by pfg 10y ago
That's right, they don't have a pinning mechanism for site operators. They have something called Certificate Reputation[1] which works alongside SmartScreen and should theoretically be of use for attacks like this, but I haven&#x2
332.
by pfg 10y ago
Yes, this is exactly the thing that HPKP would prevent from happening.
333.
by pfg 10y ago
I don't know where they got the information about the certificate being issued 5 months prior to the attack, but that's not what Certificate Transparency shows. Here's the certificate that was issued on the day of the attack[
334.
by pfg 10y ago
Other problems with DNSSEC aside, the crazy thing here is the suggestion to replace the Web PKI with a system that has taken longer to migrate towards safe key sizes than the existing solution. 1024-bit keys for end-entity certificates we
335.
How Hackers Hijacked a Bank’s Entire Online Operation(wired.com)
4 points by pfg 10y ago|0 comments
336.
by pfg 10y ago
They've rolled out a new version of video/voice calls this month[1] which supposedly improved the quality quite a bit. I haven't personally tried it yet, though. [1]: https://whispersystems.org/blog/signa
337.
by pfg 10y ago
> The thing which is really sad is that there are no end to end encrypted group chats. In iMessage specifically, or in general? WhatsApp/Signal do use E2E-crypto for group chats.
338.
by pfg 10y ago
iMessage does not allow for any out-of-band key verification. It's correct that that Apple (and anyone compromising them) is in a position to change the recipient's key or add new ones without the sender noticing anything's g
339.
by pfg 10y ago
I'm curious: what's the reason for doing this rather than just logging the IP addresses that hit your server directly? Is this a way to get around VPNs that leak the real IP via DNS? Or does this allow you to get something back fr
340.
by pfg 10y ago
Chrome's long-term plan is to show no visual indicator for (valid) HTTPS, and a non-secure indicator for HTTP[1], so that's essentially what you're describing. IIRC Firefox has similar plans. HTTPS deployment numbers don&#x27
341.
by pfg 10y ago
To be more specific: EV validates that the entity requesting the certificate is who they claim to be, in addition to demonstrating domain ownership. No validation level makes any kind of guarantee regarding the legitimacy or accuracy of con
342.
by pfg 10y ago
The schedule they're proposing tries to specifically avoid as much of this as possible. This is probably as close to "no impact for average users" as you can get if you don't want to accept that too-big-to-fail is a thin
343.
by pfg 10y ago
That's unlikely, as they currently do not offer certificates to the general public. I imagine if they do at some point, it might be as part of something like their version of Amazon's ACM for their Cloud offerings, or for custom d
344.
by pfg 10y ago
This is roughly what Little Flocker[1] does on macOS. [1]: https://www.littleflocker.com/
345.
by pfg 10y ago
Thinking about this a bit, it seems to be that clients talking to a server with OCSP stapling support could still make use of cached OCSP responses by simply omitting the "status_request" extension in the client hello, which would
346.
by pfg 10y ago
Google is a platinum sponsor for Let's Encrypt, which is slowly taking away market share from almost all commercial CAs[1]. They've also removed special treatment for EV certificates on mobile browsers (and are regularly thinking
347.
by pfg 10y ago
It's hard to say if you're implying this is any different with other validation levels like OV and EV. The validation methods that CAs may use for OV/EV are the same ones they may use for DV. The only difference is that they
348.
by pfg 10y ago
They do have a one-year deprecation policy[1] for pretty much all of their GA offerings on GCP[2]. [1]: https://cloud.google.com/terms/ [2]: https://cloud.google.com/terms/deprecation
349.
by pfg 10y ago
If you use certbot-auto to install the client, part of the installation process involves compiling some crypto library (IIRC) which tends to fail on low-memory systems, hence the need for swap. Packaged versions of certbot (from your distri
350.
by pfg 10y ago
iCloud and iCloud keychain are not really the same thing. iCloud keychain is designed not to disclose user passwords in the event of an iCloud account compromise, for example, among other things. The iOS Security Guide[1] has more details o
351.
by pfg 10y ago
The only thing that forces me to keep Thunderbird around are mailing lists. I haven't found anything else that doesn't break quoting or messes with word/line wrapping in plaintext mails. To be fair, even Thunderbird requires
352.
by pfg 10y ago
The legal thing does make reference to the technical thing in Europe[1] (and probably elsewhere too), by making digital signatures (which use crypto) legally binding. The question is more how courts would rule in a case where a colliding do
353.
by pfg 10y ago
Even root CAs have been known to not comply with the randomized serial number requirement occasionally, see [1] for a recent example, with the most recent (SHA-1) certificate being issued in August of last year. [1]: https://bugz
354.
by pfg 10y ago
Recent versions of Chrome will show a warning if you try to browse to a site that uses a SHA-1 certificate. Mozilla is doing the same thing as of Firefox 51, but they're enabling this gradually to measure impact. Microsoft has an updat
355.
by pfg 10y ago
I get a SHA256 certificate for that site. What user agent are you using? Is there some kind of middlebox on your network, or do you use AV software that intercepts TLS connections?
356.
by pfg 10y ago
Presumably they're talking about digital signatures. I don't know how common that is in the U.S., but it's used quite a bit in many European countries as a means to sign contracts and such. (I also don't know enough abou
357.
by pfg 10y ago
Worth noting that Facebook stopped offering SHA-1 back in November[1]. Cloudflare still offers SHA-1 for paying customers (via a root certificate pulled from trust stores, i.e. which are only supported on outdated devices/browsers). No
358.
Announcing the first SHA-1 collision(security.googleblog.com)
3030 points by pfg 10y ago|485 comments
359.
by pfg 10y ago
It was also registered previously (at the time of issuance) and later released by Squarespace, as mentioned in the update.
360.
by pfg 10y ago
It's possible to disable SMS-based 2FA. Perhaps you need another backup option before you're allowed to remove the SMS option. In my case, I was able to do it with two U2F keys, TOTP and backup codes enabled. You might need to rem

More ›