dc352

9 ms·

31.
Malware transmits data via LCD – changing red by 3%(zdnet.com)
5 points by dc352 7y ago|0 comments
32.
European parliament says it will not use facial recognition tech(theguardian.com)
95 points by dc352 7y ago|39 comments
33.
Microsoft Teams – cursory audit shows some 15 certificates expired recently(keychest.net)
2 points by dc352 7y ago|0 comments
34.
by dc352 7y ago
... and we'now fixed a CORS issues that caused some problems to pull the list of test servers :(
35.
Show HN: Network Speed Test Against Digital Ocean (NYC, FRA, TOR, SGP)(keychest.net)
7 points by dc352 7y ago|1 comments
36.
Thoughts on SSL/TLS(reddit.com)
1 points by dc352 7y ago|0 comments
37.
Show HN: Certbot hook to a web service (pure Linux shell)(gitlab.com)
2 points by dc352 7y ago|0 comments
38.
Let's Encrypt / ACME for newbies – how it works(keychest.net)
3 points by dc352 7y ago|0 comments
39.
PoC for CVE-2020-0601 – NSA discovered vulnerability(github.com)
1 points by dc352 7y ago|0 comments
40.
Show HN: Fun – unbreakable pen&paper encryption(keychest.net)
15 points by dc352 7y ago|0 comments
41.
Cryptographic Vulnerability in MS Windows – how without maths(keychest.net)
1 points by dc352 7y ago|0 comments
42.
by dc352 7y ago
The only way to do it (I'm lazy so didn't read any of the documents - my gut feeling of an engineer) ... is to use ECDH, which provides EC params in ServerKeyExchange. CryptoAPI might have used those and just pull the public key f
43.
by dc352 7y ago
I suspect you're overcomplicating the attack with all the math and we can ignore most of it. The only way the attacker can tell the MS Crypto API is via the TLS protocol. You can only do it if it's relevant. The only option for t
44.
Let's Encrypt Uptime Full and Partial – 2019 (99.92/96.4) vs. 2017 (99.86/98)(keychest.net)
1 points by dc352 7y ago|0 comments
45.
Show HN: Find instantly subdomains with HTTPS cert expired in last 4 weeks(keychest.net)
3 points by dc352 7y ago|0 comments
46.
Let's Encrypt clients – a long list
2 points by dc352 7y ago|0 comments
47.
A bunch of PKI / vulnerability testing tools(pki.r-itservices.at)
3 points by dc352 7y ago|0 comments
48.
Show HN: HTTPS Cert – from a domain name to a complete PFX bundle(vimeo.com)
1 points by dc352 7y ago|0 comments
49.
Show HN: ACMEv2 proxy producing JSON logs(gitlab.com)
1 points by dc352 7y ago|0 comments
50.
Let's Encrypt (ACMEv2) proxy to detect client failures(community.letsencrypt.org)
2 points by dc352 7y ago|0 comments
51.
One-line web servers – a long list(gist.github.com)
3 points by dc352 7y ago|0 comments
52.
HTTPS Monitoring Tools and 12 more tips(keychest.net)
4 points by dc352 7y ago|0 comments
53.
How Cool Is That, IRS, US AirForce, DHS, on One Let's Encrypt Cert(linkedin.com)
3 points by dc352 7y ago|0 comments
54.
Attack on ECC in Crypto++/OpenJDK – Minerva and Its Background(keychest.net)
2 points by dc352 7y ago|0 comments
55.
Automating Issuance of Non-LetsEncrypt Certs(medium.com)
3 points by dc352 7y ago|0 comments
56.
Somewhat personal story of building a cloud service (and some hardware too)(magicofsecurity.com)
2 points by dc352 7y ago|0 comments
57.
Minerva Attack (libgcrypt, wolfSSL/Crypt, MatrixSSL, Crypto++)–Humble Beginnings(magicofsecurity.com)
1 points by dc352 7y ago|0 comments
58.
by dc352 7y ago
our disks in London went down at about 8:45pm UTC (10 mins 100% disk utilization alert triggered at 5 to) and DO recovery message was sent out at about 2am UTC. We switched our service (keychest.net) on at 3:15am
59.
by dc352 7y ago
that would be pretty cool but to have that, you need a high-network-latency solution, i.e., pretty much cold back-up. For some time I thought it's pretty last century option but having been experimenting for some time now, it's th
60.
by dc352 7y ago
That wouldn't be at the top of my list. We have "Volumes" for databases and they were inaccessible for like 6 hours. I don't think any DNS is involved in mounting these. But hey, there's always a lot of crap hidden

More ›