TLS/SSL certs from the free Let�s Encrypt service are currently valid
for 90 days. But the validity is being reduced to 64 days from
February, with the aim of reducing the vulnerability window if a
certificate key should get compromised. And yes, even further
reductions are planned in the future.
Lawrence D’Oliveiro wrote:^^^^
TLS/SSL certs from the free Let’s Encrypt service are currently valid
for 90 days. But the validity is being reduced to 64 days from
February, with the aim of reducing the vulnerability window if a
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^certificate key should get compromised. And yes, even further
reductions are planned in the future.
Uh... can SHA-2 be brute forced within 64 days or less with current
fastest computers?
Uh... can SHA-2 be brute forced within 64 days or less with current
fastest computers?
JJ <[email protected]> writes:
Lawrence D�Oliveiro wrote:^^^^
TLS/SSL certs from the free Let�s Encrypt service are currently valid
for 90 days. But the validity is being reduced to 64 days from
February, with the aim of reducing the vulnerability window if a
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^certificate key should get compromised. And yes, even further
reductions are planned in the future.
Uh... can SHA-2 be brute forced within 64 days or less with current
fastest computers?
That�s not the risk being mitigated here.
(And no, it can�t. The largest public real-life hash searcher generates
about 2^92 SHA256 hashes in 64 days, nowhere near enough for collision
search and comedically inadequate for preimage search.)
I get a feeling that, a standard to require daily site certificate
update would be made to strengthen security.
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,142 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 93:06:28 |
| Calls: | 14,704 |
| Calls today: | 2 |
| Files: | 186,497 |
| D/L today: |
2,343 files (777M bytes) |
| Messages: | 2,551,657 |