home.social

#publickeyinfrastructure — Public Fediverse posts

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

  1. Vehicle-To-X (V2X) Market in the European Union | Report – IndexBox

    European Union Vehicle-To-X (V2X) Market 2026 Analysis and Forecast to 2035 Executive Su…
    #Europe #EU #automotivemarketreport #C-V2X(3GPPRelease14+) #DSRC(IEEE802.11p) #Dual-moderadiounits #Emergencyvehiclealert #EuropeanUnion #forecast #Gridloadbalancing&peakshaving #Intersectionmovementassist #marketanalysis #PublicKeyInfrastructure(PKI)forsecurity #Roadhazardwarning #Vehicle-to-X(V2X)
    europesays.com/europe/32993/

  2. PKI in a Nutshell
    A blog by Ronald

    This blog briefly describes theoretically how Public Key Infrastructure (PKI) works. It also introduces the key concepts used in PKI. This is done by describing encryption, decryption, hashing, signing, and authentication using mathematical notations.

    #dev #softwaredevelopment #Security #PKI #PublicKeyInfrastructure #Certificates #PublicKey #PrivateKey #Keystore #Truststore

    jdriven.com/blog/2026/04/PKI-i

  3. PKI in a Nutshell
    A blog by Ronald

    This blog briefly describes theoretically how Public Key Infrastructure (PKI) works. It also introduces the key concepts used in PKI. This is done by describing encryption, decryption, hashing, signing, and authentication using mathematical notations.

    #dev #softwaredevelopment #Security #PKI #PublicKeyInfrastructure #Certificates #PublicKey #PrivateKey #Keystore #Truststore

    jdriven.com/blog/2026/04/PKI-i

  4. PKI in a Nutshell
    A blog by Ronald

    This blog briefly describes theoretically how Public Key Infrastructure (PKI) works. It also introduces the key concepts used in PKI. This is done by describing encryption, decryption, hashing, signing, and authentication using mathematical notations.

    #dev #softwaredevelopment #Security #PKI #PublicKeyInfrastructure #Certificates #PublicKey #PrivateKey #Keystore #Truststore

    jdriven.com/blog/2026/04/PKI-i

  5. PKI in a Nutshell
    A blog by Ronald

    This blog briefly describes theoretically how Public Key Infrastructure (PKI) works. It also introduces the key concepts used in PKI. This is done by describing encryption, decryption, hashing, signing, and authentication using mathematical notations.

    #dev #softwaredevelopment #Security #PKI #PublicKeyInfrastructure #Certificates #PublicKey #PrivateKey #Keystore #Truststore

    jdriven.com/blog/2026/04/PKI-i

  6. PKI in a Nutshell
    A blog by Ronald

    This blog briefly describes theoretically how Public Key Infrastructure (PKI) works. It also introduces the key concepts used in PKI. This is done by describing encryption, decryption, hashing, signing, and authentication using mathematical notations.

    #dev #softwaredevelopment #Security #PKI #PublicKeyInfrastructure #Certificates #PublicKey #PrivateKey #Keystore #Truststore

    jdriven.com/blog/2026/04/PKI-i

  7. Explore global digital identity projects—from Aadhaar to Estonia’s eID—and uncover the lessons, risks, and opportunities shaping eGov worldwide. hackernoon.com/would-you-trust #publickeyinfrastructure

  8. Explore global digital identity projects—from Aadhaar to Estonia’s eID—and uncover the lessons, risks, and opportunities shaping eGov worldwide. hackernoon.com/would-you-trust #publickeyinfrastructure

  9. Explore global digital identity projects—from Aadhaar to Estonia’s eID—and uncover the lessons, risks, and opportunities shaping eGov worldwide. hackernoon.com/would-you-trust #publickeyinfrastructure

  10. Explore global digital identity projects—from Aadhaar to Estonia’s eID—and uncover the lessons, risks, and opportunities shaping eGov worldwide. hackernoon.com/would-you-trust #publickeyinfrastructure

  11. Explore global digital identity projects—from Aadhaar to Estonia’s eID—and uncover the lessons, risks, and opportunities shaping eGov worldwide. hackernoon.com/would-you-trust

  12. Explore the evolution of PKI, from centralized certificate authorities to decentralized systems like SDSI, TOFU, IRMA, and Sovrin. hackernoon.com/a-timeline-of-p #publickeyinfrastructure

  13. Explore the evolution of PKI, from centralized certificate authorities to decentralized systems like SDSI, TOFU, IRMA, and Sovrin. hackernoon.com/a-timeline-of-p #publickeyinfrastructure

  14. Explore the evolution of PKI, from centralized certificate authorities to decentralized systems like SDSI, TOFU, IRMA, and Sovrin. hackernoon.com/a-timeline-of-p #publickeyinfrastructure

  15. Explore the evolution of PKI, from centralized certificate authorities to decentralized systems like SDSI, TOFU, IRMA, and Sovrin. hackernoon.com/a-timeline-of-p #publickeyinfrastructure

  16. Explore the evolution of PKI, from centralized certificate authorities to decentralized systems like SDSI, TOFU, IRMA, and Sovrin. hackernoon.com/a-timeline-of-p

  17. PKI isn’t bulletproof. Explore the technical, legal, economic, and social risks behind digital certificates and public key infrastructures. hackernoon.com/why-public-key- #publickeyinfrastructure

  18. PKI isn’t bulletproof. Explore the technical, legal, economic, and social risks behind digital certificates and public key infrastructures. hackernoon.com/why-public-key- #publickeyinfrastructure

  19. PKI isn’t bulletproof. Explore the technical, legal, economic, and social risks behind digital certificates and public key infrastructures. hackernoon.com/why-public-key- #publickeyinfrastructure

  20. PKI isn’t bulletproof. Explore the technical, legal, economic, and social risks behind digital certificates and public key infrastructures. hackernoon.com/why-public-key- #publickeyinfrastructure

  21. PKI isn’t bulletproof. Explore the technical, legal, economic, and social risks behind digital certificates and public key infrastructures. hackernoon.com/why-public-key-

  22. Europe is betting big on digital identity. But can decades-old PKI tech secure it, or will its flaws derail the EU’s digital future? hackernoon.com/53-years-of-pub #publickeyinfrastructure

  23. Europe is betting big on digital identity. But can decades-old PKI tech secure it, or will its flaws derail the EU’s digital future? hackernoon.com/53-years-of-pub #publickeyinfrastructure

  24. Europe is betting big on digital identity. But can decades-old PKI tech secure it, or will its flaws derail the EU’s digital future? hackernoon.com/53-years-of-pub #publickeyinfrastructure

  25. Europe is betting big on digital identity. But can decades-old PKI tech secure it, or will its flaws derail the EU’s digital future? hackernoon.com/53-years-of-pub #publickeyinfrastructure

  26. Europe is betting big on digital identity. But can decades-old PKI tech secure it, or will its flaws derail the EU’s digital future? hackernoon.com/53-years-of-pub

  27. Just spent some quality time figuring out why HTTPS requests with incorrect system time would fail - even though the time was between the certificate NotBefore and NotAfter.

    OCSP stapling was the culprit. This adds a more strict "window of system time validity" due to the way the protocol works. The obvious reason for the smallish window is to allow caching, while reducing the replay attack possibilities. Thus, the system clock can't be backdated more than a few hours, regardless of certificate NotBefore. The system time can be more off towards the future.

    In our use case, we don't need to worry about revocation and hence we will just kill OCSP use. With this, we will still have the limits set by the certificate NotBefore and NotAfter, but at least they're more predictable and somewhat laxer.

    #pki #publickeyinfrastructure #tls

  28. Just spent some quality time figuring out why HTTPS requests with incorrect system time would fail - even though the time was between the certificate NotBefore and NotAfter.

    OCSP stapling was the culprit. This adds a more strict "window of system time validity" due to the way the protocol works. The obvious reason for the smallish window is to allow caching, while reducing the replay attack possibilities. Thus, the system clock can't be backdated more than a few hours, regardless of certificate NotBefore. The system time can be more off towards the future.

    In our use case, we don't need to worry about revocation and hence we will just kill OCSP use. With this, we will still have the limits set by the certificate NotBefore and NotAfter, but at least they're more predictable and somewhat laxer.

    #pki #publickeyinfrastructure #tls

  29. Just spent some quality time figuring out why HTTPS requests with incorrect system time would fail - even though the time was between the certificate NotBefore and NotAfter.

    OCSP stapling was the culprit. This adds a more strict "window of system time validity" due to the way the protocol works. The obvious reason for the smallish window is to allow caching, while reducing the replay attack possibilities. Thus, the system clock can't be backdated more than a few hours, regardless of certificate NotBefore. The system time can be more off towards the future.

    In our use case, we don't need to worry about revocation and hence we will just kill OCSP use. With this, we will still have the limits set by the certificate NotBefore and NotAfter, but at least they're more predictable and somewhat laxer.

    #pki #publickeyinfrastructure #tls

  30. Just spent some quality time figuring out why HTTPS requests with incorrect system time would fail - even though the time was between the certificate NotBefore and NotAfter.

    OCSP stapling was the culprit. This adds a more strict "window of system time validity" due to the way the protocol works. The obvious reason for the smallish window is to allow caching, while reducing the replay attack possibilities. Thus, the system clock can't be backdated more than a few hours, regardless of certificate NotBefore. The system time can be more off towards the future.

    In our use case, we don't need to worry about revocation and hence we will just kill OCSP use. With this, we will still have the limits set by the certificate NotBefore and NotAfter, but at least they're more predictable and somewhat laxer.

    #pki #publickeyinfrastructure #tls

  31. Just spent some quality time figuring out why HTTPS requests with incorrect system time would fail - even though the time was between the certificate NotBefore and NotAfter.

    OCSP stapling was the culprit. This adds a more strict "window of system time validity" due to the way the protocol works. The obvious reason for the smallish window is to allow caching, while reducing the replay attack possibilities. Thus, the system clock can't be backdated more than a few hours, regardless of certificate NotBefore. The system time can be more off towards the future.

    In our use case, we don't need to worry about revocation and hence we will just kill OCSP use. With this, we will still have the limits set by the certificate NotBefore and NotAfter, but at least they're more predictable and somewhat laxer.

    #pki #publickeyinfrastructure #tls