|
Canada-0-READAPTATION Κατάλογοι Εταιρεία
|
Εταιρικά Νέα :
- Can we trust onetimesecret? - Information Security Stack Exchange
So for example you ask the other person to use the place you met for the first time as a password for the first layer Then you ask them something else for the second one and so on, until you are confident only the correct person could know all the answers
- secret sharing - Best method to send credentials to clients . . .
There are options to protect it with a password, to limit the number of views, to limit the time, etc Creating such an account and using this feature is free Like other methods, you can send the link in one encrypted channel, and pass the password in another channel
- Why even use a one-time pad if the key distribution is fully secured?
A one-time pad can be broke if the message to be encrypted is significantly longer (like multiple times) than the number of characters bytes in the pad This amounts to repeated use of the same "one-time pad" and is equally vulnerable to decryption
- How can I decode a message that was encrypted with a one-time pad?
One-Time Pad is unbreakable, assuming the pad is perfectly random, kept secret, used only once, and no plaintext is known This is due to the properties of the exclusive-or (xor) operation
- authentication - Sending passwords to someone remotely - Information . . .
27 When I need to send something a single time, I have used One Time Secret It's an open-source web app that allows you to enter information that can only be viewed once After the recipient has opened the page, the information is deleted, and the only thing remaining in your chat logs or email is a bad link
- authentication - How does Google Authenticator work? - Information . . .
Google Authenticator supports both the HOTP and TOTP algorithms for generating one-time passwords With HOTP, the server and client share a secret value and a counter, which are used to compute a one time password independently on both sides
- authentication - one-time JWT token with JWT ID claim - Information . . .
And the jwt itself is one-time too, because once the password is changed, the jwt won't be verifiable any more Which is "better" than the approach you've detailed, because a server-wide secret key isn't needed for this use case
- What is the simplest safe way to convey a password to another person . . .
"One time secret" does a good job, but it does depend on you trusting the site Deciding whether to use it depends on the information that you sending
- How to set up two YubiKeys to have the same secret?
This would allow the user to keep one key in a "useful" location (e g on their person), and one key in a "safe" backup location, such as a safe at home Is it possible to set up two YubiKeys to have the same secrets, so they can be used interchangably?
- Can a Time-based One-time Password (TOTP) key be decoded from generated . . .
The HMAC-based One-Time Password (HOTP) algorithm (RFC 4226 (informational)) that forms the foundational part of TOTP says that the shared secret should be at least 120 bits in length, and recommends 160 bits for its key
|
|