Enable passphrase-protected key files in the api.

[yassinm]

I am trying to use sops and i am finding that it requires non encrypted ket.txt file to be on the file system. I am trying to add a functionality that would make it possible. The api call currently exposed by age and used by sops only supports plain text key.txt files when the api is called

Unfortunately according to this the parsing of encrypted key files is not currently exposed via the API. To me (at least) it makes sense to make ssh key files part of the main package but not the part that detects if the key file is an ecrypted one. Is there a rationale why this is not exposed now as part of the api ? or why supporting encrypted key files via the api is an anti pattern ?