#pkcs12 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #pkcs12, aggregated by home.social.
-
🏦 **Představuji: RBC Premium API Python Library v1.0.2**
Po dlouhé práci jsem dokončil a vydal kompletní Python client knihovnu pro Premium API Raiffeisenbank České republiky. Tato knihovna významně zjednodušuje integraci s bankovními službami pro české vývojáře a firmy.
🎯 **Co knihovna nabízí:**
**Kompletní API pokrytí:**
• Správa účtů a zůstatků
• Přehledy transakcí (včetně spořicích účtů)
• Import plateb
• Stahování výpisů
• Aktuální FX kurzy
• Batch operace**Profesionální implementace:**
• Automaticky generováno z OpenAPI 3.0 specifikace
• Plná podpora mTLS autentizace s PKCS#12 certifikáty
• Type hints pro bezpečný vývoj
• Komprehenzivní error handling
• Dodržování rate limitů (10/s, 5000/den)**Developer Experience:**
• 14 praktických příkladů použití
• Kompletní dokumentace všech endpoints
• Snadná instalace přes pip
• Podpora Python 3.9+🔧 **Technické detaily:**
Knihovna je postavena na OpenAPI Generator 7.13.0 s vlastními šablonami optimalizovanými pro Python. Řeší běžné problémy s imports, forward references a poskytuje utility pro extrakci certifikátů z P12 souborů.📈 **Proč je to důležité:**
V době digitalizace bankovnictví potřebují firmy spolehlivé nástroje pro integraci s bankovními API. Tato knihovna odstraňuje technické bariéry a umožňuje vývojářům soustředit se na business logiku místo na low-level HTTP komunikaci. (+ jsem se na tom naučil commandovat copilota na složitějším projektu)📦 **Jak začít:**
```bash
pip install rbczpremiumapi
```Více informací, příklady a dokumentace najdete na:
🔗 PyPI: https://pypi.org/project/rbczpremiumapi/
🔗 GitHub: https://github.com/Vitexus/python-rbczpremiumapiTěším se na vaše zpětné vazby a případné příspěvky k dalšímu rozvoji!
#Python #API #Banking #FinTech #OpenSource #RaiffeisenBank #VitexSoftware #CzechTech #OpenAPI #mTLS #PKCS12
-
He escrito una cosa que te vendrá bien si tienes un certificado en #pkcs12 y de repente tu navegador no es capaz de importarlo, cosa que está pasando con los certificados emitidos por el gobierno español: “Solucionando Problemas de Compatibilidad del Certificado de la #FNMT” https://gvisoc.com/solucionando-problemas-pkcs12/
-
Strangely enough, #BigTech vendors have obscured some fundamental facts about all of this.
#X509 certificates are understood natively by every modern computing OS. Ditto secure #PKCS12 credentials stores.
A single-click on credentials packaged using these open standard doc types and the OS handles the rest via built-in #UI/#UX.
The public credentials doc is whatever you choose as your profile doc e.g, a simple #HTML file, @Mastodon profile page, etc.
-
We are finalizing a new release of our @youid browser extension that includes a major new #LinkInBio feature that helps users acquire more control over their digital profile and associated #Identity #Authenticity.
Items contained in the ZIP bundle generated by #YouID include: an #HTML based profile doc, #PKCS12 credentials bundle, #vCard, #QRCode, etc.
Example: https://id.myopenlink.net/public_home/KingsleyUyiIdehen/Public/index.html
/cc @Mastodon
#SSI #NetID #Privacy #Web30 #LinkedData #SemanticWeb #HTTPS #TLS #SMIME #KnowledgeGraph
-
Credentials (#X509 cert and private keys) belong in a local credentials store e.g., "keystore" for #Windows, #keychain for #macoOS, etc.
If the native OS doesn't offer a keystore, as per list above, then a #PKCS12 will suffice.
The problem, as already outlined, is that #Email vendors have been blindsided by their business models.
Most ironically, every modern OS has native support re #UI/#UX for handling X.509, PKCS12, etc..
-
@ben,
Here’s what a user has to do:1. Copy a #SHA hash of #PublicKey from what #YouID outputs (via a #html doc) to their @Mastodon profile page
2. Download #PKCS12 doc
3. Double click on downloaded #PKCS12 and leave OS #UI/#UX to handle credentials storage to its native credentials store (e.g., #macos #keychain).
1-3 works on any modern #OS since they all understand what a #PKCS12 file management.
Personally, I don’t believe these steps are beyond the capabilities of end-users.
-
@ben ,
It isn’t more complicated if there’s a user-friendly solution delivered as an app or browser extension for:1. Generating Certificate
2. Extracting #PublicKey hash in copy & paste friendly form
3. Packaging credentials in a #PKCS12 file (understood by all modern operating systems)
That’s exactly what our #YouID browser extension offers 😀
/cc @Mastodon
-
@bobwyman @Mastodon @blaine @brewsterkahle @christina @sheldrake @dsearls @jpanzer ,
Currently, #Identity #Authenticity on this platform is handled via a single option that depends on an ability to place #HTML in a page you control.
The #HTTPS based system I demonstrate simply requires possession of credentials (#X509 cert and #PrivateKey) stored in your local keystore (e.g., Keychain on #macOS) or a #PKCS12 file.
-
Yes!
Which is why end-users need to control their #identity, period.
Big Challenge:
End-users want convenience above all else, which presents a big problem to the pursuit of self-sovereign identity (#SSI).The following, automated by software, is still a challenge:
Credentials (#X509 cert, Public Key, and Private Key) bundled in a #PKCS12 file (that's supported by every modern OS re extraction and storage to a local keystore or keychain) -
/cc @blaine @digibrarian
-
Anyone know how to create a #pkcs12 container holding only a keypair with #openssl that I can import into browsers?
I tried:
openssl genrsa 4096 > me.key
openssl pkcs12 -inkey me.key -nocerts -export > me.p12And this *seems* to work, but doing:
openssl pkcs12 -in me.p12 -nocerts -infoasks for a PEM passphrase and dies with what looks like a traceback that complains about the given passphrase being too short – but the keypair in there has no passphrase…
paste here: https://paste.xinu.at/lg40/