-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support GPG and SSH keys #55
Comments
Re SSH: >>> securesystemslib.interface.import_ed25519_privatekey_from_file(".ssh/id_ed25519")
Traceback (most recent call last):
File "<input>", line 1, in <module>
k = intf.import_ed25519_privatekey_from_file(".ssh/id_ed25519")
File "/Users/lukp/code/securesystemslib/securesystemslib/interface.py", line 549, in import_ed25519_privatekey_from_file
key_object = securesystemslib.keys.decrypt_key(encrypted_key.decode('utf-8'), password)
File "/Users/lukp/code/securesystemslib/securesystemslib/keys.py", line 1689, in decrypt_key
securesystemslib.pyca_crypto_keys.decrypt_key(encrypted_key, passphrase)
File "/Users/lukp/code/securesystemslib/securesystemslib/pyca_crypto_keys.py", line 843, in decrypt_key
json_data = _decrypt(encrypted_key, password)
File "/Users/lukp/code/securesystemslib/securesystemslib/pyca_crypto_keys.py", line 986, in _decrypt
raise securesystemslib.exceptions.CryptoError('Invalid encrypted file.')
CryptoError: Invalid encrypted file. Update: |
Re GPG: We have implemented GPG support in |
securesystemslib provides an API to import and export public and private keys in PEM (RSA, ECDSA, also cf. #54) or in a proprietary format (Ed25519).
It would be convenient to extend the API so that users can load, e.g. their existing GPG or SSH keys. Note that securesystemslib does not necessarily have to provide an API to generate those keys. As @aaaaalbert has mentioned, user might even prefer to use their own well-known toolchain.
The text was updated successfully, but these errors were encountered: