Skip to main content
Removed unnecessary signature
Source Link
Ramhound
  • 43k
  • 35
  • 107
  • 137

Windows 10 command line ssh-keygen -b 2048 -mPKCS8 doesn't change the .pub file created to PKCS8 (it's always the one-liner).

I can do this to get the actual format output to the screen: ssh-keygen -ef test.key -mPKCS8

but if I tell it to use PKCS8 when generating, it seems to ignore it?

Is this as intended or a bug or am I doing something wrong?

TIA!!

Windows 10 command line ssh-keygen -b 2048 -mPKCS8 doesn't change the .pub file created to PKCS8 (it's always the one-liner).

I can do this to get the actual format output to the screen: ssh-keygen -ef test.key -mPKCS8

but if I tell it to use PKCS8 when generating, it seems to ignore it?

Is this as intended or a bug or am I doing something wrong?

TIA!!

Windows 10 command line ssh-keygen -b 2048 -mPKCS8 doesn't change the .pub file created to PKCS8 (it's always the one-liner).

I can do this to get the actual format output to the screen: ssh-keygen -ef test.key -mPKCS8

but if I tell it to use PKCS8 when generating, it seems to ignore it?

Is this as intended or a bug or am I doing something wrong?

added command line used.
Source Link

Windows 10 command line ssh-keygen -b 2048 -mPKCS8 indicate it supports -m but doing so doesn't change the .pub file created to PKCS8 (it's always the one-liner).

I can do this to get the actual format output to the screen: ssh-keygen -ef test.key -mPKCS8

but if I tell it to use PKCS8 when generating, it seems to ignore it?

Is this as intended or a bug or am I doing something wrong?

TIA!!

Windows 10 command line ssh-keygen indicate it supports -m but doing so doesn't change the .pub file created (it's always the one-liner).

I can do this to get the actual format output to the screen: ssh-keygen -ef test.key -mPKCS8

but if I tell it to use PKCS8 when generating, it seems to ignore it?

Is this as intended or a bug or am I doing something wrong?

TIA!!

Windows 10 command line ssh-keygen -b 2048 -mPKCS8 doesn't change the .pub file created to PKCS8 (it's always the one-liner).

I can do this to get the actual format output to the screen: ssh-keygen -ef test.key -mPKCS8

but if I tell it to use PKCS8 when generating, it seems to ignore it?

Is this as intended or a bug or am I doing something wrong?

TIA!!

Source Link

Why doesn't windows 10 ssh-keygen honor the -m option?

Windows 10 command line ssh-keygen indicate it supports -m but doing so doesn't change the .pub file created (it's always the one-liner).

I can do this to get the actual format output to the screen: ssh-keygen -ef test.key -mPKCS8

but if I tell it to use PKCS8 when generating, it seems to ignore it?

Is this as intended or a bug or am I doing something wrong?

TIA!!