pstrateman

41 ms·

481.
by pstrateman 12y ago
The tide moves 6ft+ from high to low. As long as the flow rate is less than 3ft/day then you can just wait for low tide.
482.
by pstrateman 13y ago
The worlds only 1m high hydroelectric dam.
483.
by pstrateman 13y ago
> The Canadian government runs several PKIs with tens of thousands of active certs, many thousands of revoked, no problems at all, because of CDPs. Because thousands is off by several orders of magnitude. Real public CAs are going to hav
484.
by pstrateman 13y ago
> That is, how are the intermediate certificates supposed to be revoked if certificate revocation does not work relibably ? It's a much smaller amount of information, so a normal CRL can be used effectively. You really cannot use a
485.
by pstrateman 13y ago
Because querying the OCSP servers directly results in a crazy amount of traffic. Implemented in the most paranoid manner possible every https request would result in an OCSP request. That would be millions of requests per second for a large
486.
by pstrateman 13y ago
I should note that blocking OCSP requests will not cause revoked.grc.com to function. The server is using OCSP stapling, which means the OCSP certificate is being sent directly by the https server, an attack would obviously not be sending a
487.
by pstrateman 13y ago
Certificate revocation does not work. There are two methods of revoking a certificate, Certificate Revocation Lists and OCSP (Online Certificate Status Protocol). CRL lists do not scale at all and are almost universally do not include all r
488.
by pstrateman 13y ago
TCP Keepalive is a much better solution for this problem. Nearly all bitcoin pools utilize TCP keepalive to maintain connections with miners. These are systems in which performance and DoS resistance are paramount.
489.
by pstrateman 13y ago
Implementing a system to detect transactions being confirmed is orders of magnitude more complicated than send and forget. I've sent literally tens of thousands of bitcoins transactions and have never once had a transaction that wasn&#
490.
by pstrateman 13y ago
The claim that this was caused by transaction malleability rings hollow. The reference client (github.com/bitcoin/bitcoin) does not resend transactions because of malleability. The only way you can have double transfers due to mal
491.
by pstrateman 13y ago
Forgot the link... https://github.com/bitcoin/bitcoin/pull/3180
492.
by pstrateman 13y ago
I actually removed the 100ms sleep. I believe the change was made in release 0.8.6