#pkcs7 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #pkcs7, aggregated by home.social.
-
#cryptography fediverse I'm having some major trouble with PKCS7 signing in forge-js and can't seem to find the issue. I've got a script working in python but when I write the same signing function in JS using forge then the output bytes are very similar, but not the same. Lots of additional 11000010 (194) and 11000011 (195) values, and some bytes also have +64 added to them (01000000). Some other differences too but they're not immediately obvious, there is a lot which is identical though, just scattered bytes in among the output.
I'm reaching out as I'm really stuck and have hit an impasse with this. Does anyone have any experience with using forge for signing? I can share code snippets and outputs if it's any help but I've been on this for weeks now with no advancement. Not used to using JS for this kind of thing but it's a requirement of the project I'm working on.
-
Payment Gateway rejecting Digitally Signed Payment Message
https://security.stackexchange.com/questions/267928/payment-gateway-rejecting-digitally-signed-payment-message
#digitalsignature #openssl #pkcs7 #pfx -
What's your #email package?
I've had issues sending digitally signed emails, using a self-signed certificate, when using #Thunderbird.As for #PKCS7 file issues, they occur if the recipient uses #GMAIL.
-
That isn't my experience.
My experience is as follows:
When I send digitally signed emails, recipients have issues with my mails due to their native #email package not supporting self-signed certs or their hosted email app not understanding (or liking) #pkcs7 attachments (that hold the content hash and senders digital signature).
Fundamentally, digitally signed and/or encrypted emails have been stifled by vendor myopia.
