#x509

2025-07-01

KEKS кодек и криптографические сообщения

Данная статья напоминает о проблемах X.509 PKI и реализаций ASN.1. Предлагает компактный, быстрый, детерминированный, потоковый и простой формат кодирования данных KEKS, а также криптографические сообщения для подписи и шифрования данных с поддержкой пост-квантовых алгоритмов.

habr.com/ru/articles/923810/

#c #go #python #keks #asn1 #x509 #openssl #криптография #pqc #hpke #pgp #cms

2025-06-29

Building Your Own PKI with Step-CA – From Root CA to Proxmox Integration with ACME!

In this #HowTo we create an own, decentralized PKE with #stepca, enable #ACME and integrate a #Proxmox node to obtain a certificate.

#proxmox #stepca #opensource #howto #homelab #enterprise #pki #security #decentralized #x509 #certificates

gyptazy.com/building-your-own-

cyberschubicyberschubi
2025-06-23

🔐 Un certificat auto-signé n’est pas une sécurité.
Il ne prouve rien, ne garantit rien, n’est reconnu par personne.

Si ton système est partagé, connecté ou critique : PKI obligatoire.

Même en test, même en préprod.

Une dette technique dangereuse, pas une “solution pragmatique”.

2025-06-20

Are there any good alternatives to #openpgp as gerneral purpose signature and encryption protocol thing with a "web of trust" idea in the back instead of hierarchical one like in #x509 ?

#openpgp does what it should do and i like packet approach. But imo it has become too complex in its try to stay backwards compatible an beeing "too generic" ...

just to be sure I'am not looking for an alternative to sign and encrypt emails but, a framework/protocol for distrib machine 2 machine communication

2025-06-17

What if #TLS used #PGP instead of #x509?

2025-06-09

Nutzt du Client Authentication mit TLS-Zertifikaten?

#TLS #letsencrypt #EKU #X509

2025-06-03

Es gab doch mal diesen Vorstoß, daß Browser- unf Betriebssystemhersteller in der EU verpflichtet werden sollen, EU-CAs für #x509 als vetrauenswürdig aufzunehmen - was ja auch jeglicher #Chatkontrolle stark in die Hände spielte...

Gibt es dazu Neuerungen? Und wie hießen die nochmal? qwacs oder so?

#tls #ca

2025-05-20

Can’t wait for @jwildeboer ’s https://nerdcert.eu/ to take off and be included in the usual bundles like Debian ca-certificates as a big FU to Google, who mandate webbrowser-consumer-only key usages for certificates soon, and to Let’s Encrypt who are following Google mindlessly and try to argue people with these uses to death instead of standing up for people’s freedom and keep existing, working uses of SSL/TLS merely because those are not webbrowser-consumer uses.

#nerdcert #LetsEncrypt #SSL #TLS #X509 #CA

2025-05-15

@rl_dane @ShinjiLE if you or someone else wants to help argue, the thread is at https://community.letsencrypt.org/t/do-not-remove-tls-client-auth-eku/237427 (Discourse, so JS webbrowser), I’m exhausted.

#LetsEncrypt #SSL #TLS #certificates #X509 #X509v3 #sendmail #SMTP #XMPP #Jabber

C.Suthorn :prn:Life_is@no-pony.farm
2025-05-09

#fedihelp #fedihilfe

I am looking for a free provider of #x509 #certificates for use with #CAI #ContentAuthenticityInitiative #C2PA #ContentCredentials. #Adobe and #PixelStream seem to offer this #service, but not for #free. Basicalky something like #LetsEncrypt, only for #images.

#c2patool #Laica #nikon #freelens #truepic #zebra

Rainer "friendica" Sokollrainer@friendica.sokoll.com
2025-05-08

#X509 Zertifikatsketten, ich hab' da mal ne Frage. Mein Serverchen friendica.sokoll.com liefert 2 Zertifikate aus: seines und das intermediate.
Das Zertifikat für den Server selbst:

❯ openssl x509 -in friendica.sokoll.com-server.pem -noout -subject -issuer
subject=CN=friendica.sokoll.com
issuer=C=US, O=Let's Encrypt, CN=E5

Schaut auf diesen issuer!
Dann das Intermediate, was als zweites mitgeliefert wird:
❯ openssl x509 -in friendica.sokoll.com-intermediate.pem -noout -subject -issuer
subject=C=US, O=Let's Encrypt, CN=E5
issuer=C=US, O=Internet Security Research Group, CN=ISRG Root X1

Die Verknüpfung beider Zertifikate findet über issuer beim Server statt, dem das subjectbeim intermediate entspricht? Strenggenommen sollte man wohl nicht von intermediate reden, sondern einfach von "übergeordnetes Kettenglied"?

Jedenfalls: Müssen issuer und subject kongruent sein oder reicht es, wenn der jeweilige CN identisch ist?

2025-05-04

If you didn’t automated #TLS #X509 certificate renewal yet, it is pretty much the time to do so.

feistyduck.com/newsletter/issu

DACBARBOS Branddacbarbos
2025-04-25

MT @digicert@x.com
cert lifetimes are shrinking to 47 days by 2029. The message is clear: isn’t optional anymore. As DigiCert’s Dean Coclin says, “success depends on + treating as a strategy, not a set-it-and-forget-it task.” 🔐
digicert.com/blog/tls-certific

2025-04-16

Do any email sysadmin understand what's the difference between StartTLS and x509 scores in the MECSA report?
How to go from orange to green score? What requirements must the certificate have and is it possible with LetsEncrypt?

relevant links mecsa.jrc.ec.europa.eu/faq#sec and mecsa.jrc.ec.europa.eu/en/tech

#security #letsencrypt #email #sysadmin #postfix #certificate #x509 #europe #selfhosted

Example of results for the MECSA scrore for the confidential delivery part
Alexandre Dulaunoyadulau@infosec.exchange
2025-03-11

Use OpenSSL as a very inefficient video player by @wr

You should check out his repository for demos and a presentation covering all the funny and interesting details of X.509 parsing!

🔗 github.com/wllm-rbnt/trapped-b

🔗 github.com/wllm-rbnt/trapped-b

#openssl #infosec #opensource #x509

Playing a animated gif by reading a certificate in OpenSSL.
Kushal Das :python: :tor:kushal@toots.dgplug.org
2025-02-26

Who assigns #x509 #certificate #extension #OID numbers?

Jürgenelbosso
2025-02-22

Heh - ich glaube ich komme jetzt langsam aus meiner wieder raus. Nachdem ich heute Vormittag nach dem nochmal kurz auf Nickerchen geschaltet habe, habe ich bis eben im durchgezogen - wird auf jeden Fall wieder ein Artikel für die im - vllt sogar ein Projekt auf (dafür muss ich aber noch aufräumen) Thema: ( ) und so...

2024-12-17

TIL that #Apple does not support EC keys with 521 bits and does not support SHA512 digests for EC keys at all in #X509

This means that if your CA *or* your server certificate uses 521 bit EC keys or SHA512 in conjunction with arbitrary length EC keys, there is no way to get iOS clients to connect to your service. Not even Firefox on iOS will accept the certs. Neither will Safari on MacOS.

And I thought this was mandatory for proper #TLS 1.3 support 🤔
Any idea why Apple did this?
#cryptography

Screenshot of supported signature algorithms in Firefox on iOS. Algorithms starting with "ecdsa_secp521r1" are missing, as are algorithms starting with "ecdsa_" and ending in "_sha512".

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst