Tag Info

New answers tagged

0

Sending a verification code is a good option to make use of the information that you have in the database. For the type of algorithm, you can use a complex or a simple ones. The simple one that I have in mind is the timestamp and add salting to it. Like how cryptography works. As for the expiry time, make it like 3 mins would be sufficient. The number of ...


0

I think that you're asking how to generate a timestamp response as defined in timestamp-protocol: RFC3161, with openssl to generate and sign the response using a PKCS#11 (HSM in your case) as a TSA signer. I think that there is no native way to use PKCS#11with openssl to do this. (maybe with some plugin like: opensc pkcs11 engine for openssl). If you take ...


1

Regardless of what is contained in the paper a standard ntp request datagram does contain a timestamp that represents the time the datagram was sent. From page 22 of the RFC: Origin Timestamp (org): Time at the client when the request departed for the server, in NTP timestamp format. The answer to the question "Does ntp leak system time?" is "Yes. A ...


2

No, the paper means something else. The paper talks about connecting multiple times to the same Tor Hidden service to increase the load, and at the same time measuring clock skew from candidate IP addresses. If the candidate shows clock skew during the attack, the server can be identified.



Top 50 recent answers are included