Re: Letting openssl tools understand openssh keys?

I listed that as one *possible* use, but my point was more that there is 
presently no tool that can digest and parse-to-readable this blob of 
base64-encoded-pem-with-a-\-\-\-\-BEGIN\-FOO that looks like every other 
blob of base64-encoded-pem-with-a-\-\-\-\-BEGIN\-FOO that openssl asn1 
parse *can* understand, and rather than getting errors, it would be useful 
to get at least a dump of the data.

I'm talking about the "new secure format", not the legacy one which is 
defined by an RFC, the one that I linked to an article describing the 
format of.

-Dan

On Monday, August 11, 2025 at 3:21:03 PM UTC-7 Alan Buxey wrote:

> Trying to do this inline or do you have access to the keys?  If doing an 
> audit and you have key access then there is an OpenSSH tool that can help:
>
>
> ssh-keygen -y -P "" -f "$path_to_keyfile"
>
> If there's a password then it'll error. If not then it'll return no error
>
> There are a few OpenSSH ASN.1 formats, the legacy and the new secure 
> format etc there are also other ways of examining the key files to check 
> whether there is an encrypted element, that varies depending on type of key
>
> Regards
>
> Alan
>

-- 
You received this message because you are subscribed to the Google Groups "openssl-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openssl-users+unsubscribe-MCmKBN63+Bmbup2nOX2J7Q@public.gmane.org
To view this discussion visit https://groups.google.com/a/openssl.org/d/msgid/openssl-users/4a0289d0-caa2-45e7-842d-2e11c36bde20n%40openssl.org.