home.social

#secretkey — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #secretkey, aggregated by home.social.

fetched live
  1. This is the part of 2FA/TOTP that many people don’t realize:

    Your phone isn’t receiving the 6-digit code from the server.

    Instead, your authenticator app acts like a specialized cryptographic calculator. 🧮🔐

    It takes a shared secret key, combines it with the current time, and applies the TOTP algorithm to generate a temporary 6-digit code.

    At the same time, the server independently performs the same calculation using its copy of the secret key and the same time counter.

    Same secret + same time counter + same algorithm = same result.

    That’s why your authenticator app can generate the correct code without receiving it from the server.

    It’s a simple idea, but a brilliant application of cryptography.

    You can even test this yourself: add the same TOTP secret to both Google Authenticator and Microsoft Authenticator. Even if you set them up at different times, both apps can independently generate the same 6-digit code at the same time.

    And here’s another important point:

    The algorithm doesn’t need to be secret.

    TOTP is based on publicly known, standardized cryptographic algorithms such as HMAC. What needs to remain secret is the shared secret key.

    So:

    🧮 Algorithm/math: Can be publicly known.
    🔑 Secret key: Must remain private. Never share it.
    ⏱️ Time: Isn’t secret.
    🔐 Security: Comes from protecting the secret key, not from hiding the algorithm.

    That’s a core principle of modern cryptography: A cryptographic system should remain secure even when the algorithm is publicly known. The secret is the key.

    #2FA #TwoFactor #Security #Cybersecurity #SecretKey #Authentication #Cryptography #Math #TOTP #OTP #AuthenticatorApp #Internet #SecurityResearch

  2. This is the part of 2FA/TOTP that many people don’t realize:

    Your phone isn’t receiving the 6-digit code from the server.

    Instead, your authenticator app acts like a specialized cryptographic calculator. 🧮🔐

    It takes a shared secret key, combines it with the current time, and applies the TOTP algorithm to generate a temporary 6-digit code.

    At the same time, the server independently performs the same calculation using its copy of the secret key and the same time counter.

    Same secret + same time counter + same algorithm = same result.

    That’s why your authenticator app can generate the correct code without receiving it from the server.

    It’s a simple idea, but a brilliant application of cryptography.

    You can even test this yourself: add the same TOTP secret to both Google Authenticator and Microsoft Authenticator. Even if you set them up at different times, both apps can independently generate the same 6-digit code at the same time.

    And here’s another important point:

    The algorithm doesn’t need to be secret.

    TOTP is based on publicly known, standardized cryptographic algorithms such as HMAC. What needs to remain secret is the shared secret key.

    So:

    🧮 Algorithm/math: Can be publicly known.
    🔑 Secret key: Must remain private. Never share it.
    ⏱️ Time: Isn’t secret.
    🔐 Security: Comes from protecting the secret key, not from hiding the algorithm.

    That’s a core principle of modern cryptography: A cryptographic system should remain secure even when the algorithm is publicly known. The secret is the key.

    #2FA #TwoFactor #Security #Cybersecurity #SecretKey #Authentication #Cryptography #Math #TOTP #OTP #AuthenticatorApp #Internet #SecurityResearch

  3. This is the part of 2FA/TOTP that many people don’t realize:

    Your phone isn’t receiving the 6-digit code from the server.

    Instead, your authenticator app acts like a specialized cryptographic calculator. 🧮🔐

    It takes a shared secret key, combines it with the current time, and applies the TOTP algorithm to generate a temporary 6-digit code.

    At the same time, the server independently performs the same calculation using its copy of the secret key and the same time counter.

    Same secret + same time counter + same algorithm = same result.

    That’s why your authenticator app can generate the correct code without receiving it from the server.

    It’s a simple idea, but a brilliant application of cryptography.

    You can even test this yourself: add the same TOTP secret to both Google Authenticator and Microsoft Authenticator. Even if you set them up at different times, both apps can independently generate the same 6-digit code at the same time.

    And here’s another important point:

    The algorithm doesn’t need to be secret.

    TOTP is based on publicly known, standardized cryptographic algorithms such as HMAC. What needs to remain secret is the shared secret key.

    So:

    🧮 Algorithm/math: Can be publicly known.
    🔑 Secret key: Must remain private. Never share it.
    ⏱️ Time: Isn’t secret.
    🔐 Security: Comes from protecting the secret key, not from hiding the algorithm.

    That’s a core principle of modern cryptography: A cryptographic system should remain secure even when the algorithm is publicly known. The secret is the key.

    #2FA #TwoFactor #Security #Cybersecurity #SecretKey #Authentication #Cryptography #Math #TOTP #OTP #AuthenticatorApp #Internet #SecurityResearch

  4. This is the part of 2FA/TOTP that many people don’t realize:

    Your phone isn’t receiving the 6-digit code from the server.

    Instead, your authenticator app acts like a specialized cryptographic calculator. 🧮🔐

    It takes a shared secret key, combines it with the current time, and applies the TOTP algorithm to generate a temporary 6-digit code.

    At the same time, the server independently performs the same calculation using its copy of the secret key and the same time counter.

    Same secret + same time counter + same algorithm = same result.

    That’s why your authenticator app can generate the correct code without receiving it from the server.

    It’s a simple idea, but a brilliant application of cryptography.

    You can even test this yourself: add the same TOTP secret to both Google Authenticator and Microsoft Authenticator. Even if you set them up at different times, both apps can independently generate the same 6-digit code at the same time.

    And here’s another important point:

    The algorithm doesn’t need to be secret.

    TOTP is based on publicly known, standardized cryptographic algorithms such as HMAC. What needs to remain secret is the shared secret key.

    So:

    🧮 Algorithm/math: Can be publicly known.
    🔑 Secret key: Must remain private. Never share it.
    ⏱️ Time: Isn’t secret.
    🔐 Security: Comes from protecting the secret key, not from hiding the algorithm.

    That’s a core principle of modern cryptography: A cryptographic system should remain secure even when the algorithm is publicly known. The secret is the key.

    #2FA #TwoFactor #Security #Cybersecurity #SecretKey #Authentication #Cryptography #Math #TOTP #OTP #AuthenticatorApp #Internet #SecurityResearch

  5. This is the part of 2FA/TOTP that many people don’t realize:

    Your phone isn’t receiving the 6-digit code from the server.

    Instead, your authenticator app acts like a specialized cryptographic calculator. 🧮🔐

    It takes a shared secret key, combines it with the current time, and applies the TOTP algorithm to generate a temporary 6-digit code.

    At the same time, the server independently performs the same calculation using its copy of the secret key and the same time counter.

    Same secret + same time counter + same algorithm = same result.

    That’s why your authenticator app can generate the correct code without receiving it from the server.

    It’s a simple idea, but a brilliant application of cryptography.

    You can even test this yourself: add the same TOTP secret to both Google Authenticator and Microsoft Authenticator. Even if you set them up at different times, both apps can independently generate the same 6-digit code at the same time.

    And here’s another important point:

    The algorithm doesn’t need to be secret.

    TOTP is based on publicly known, standardized cryptographic algorithms such as HMAC. What needs to remain secret is the shared secret key.

    So:

    🧮 Algorithm/math: Can be publicly known.
    🔑 Secret key: Must remain private. Never share it.
    ⏱️ Time: Isn’t secret.
    🔐 Security: Comes from protecting the secret key, not from hiding the algorithm.

    That’s a core principle of modern cryptography: A cryptographic system should remain secure even when the algorithm is publicly known. The secret is the key.

    #2FA #TwoFactor #Security #Cybersecurity #SecretKey #Authentication #Cryptography #Math #TOTP #OTP #AuthenticatorApp #Internet #SecurityResearch