On Mon, Sep 19, 2022 at 01:32:40AM +, A Z wrote:
> A#) openssl req -x509 -nodes -newkey rsa:4096 -keyout private.key -out
> public.key
>
> B#) openssl smime -encrypt -binary -aes-256-cbc -in message.txt -out
> encrypted.dat -outform DER public.key
>
> C#) openssl smime -decrypt -in
A#) openssl req -x509 -nodes -newkey rsa:4096 -keyout private.key -out
public.key
B#) openssl smime -encrypt -binary -aes-256-cbc -in message.txt -out
encrypted.dat -outform DER public.key
C#) openssl smime -decrypt -in encrypted.dat -binary -inform DEM -inkey
private.key -out decrypted.txt
> From: openssl-users On Behalf Of Michael
> Ströder via openssl-users
> Sent: Sunday, 18 September, 2022 04:27
>
> On 9/18/22 06:09, Philip Prindeville wrote:
> >> On Sep 15, 2022, at 4:27 PM, Michael Wojcik via openssl-users us...@openssl.org> wrote:
> >> You still haven't explained your
On 9/18/22 06:09, Philip Prindeville wrote:
On Sep 15, 2022, at 4:27 PM, Michael Wojcik via openssl-users
wrote:
You still haven't explained your threat model, or what mitigation
the application can take if this requirement is violated, or why
you think this is a "best practice". >
The threat
