Feature Request: Aegis encrypted export

[jonas-w]

Hey thank you for this neat little tool.
When i first tried to import my aegis json file it spit out a huge error. Then i realized it's because of the encryption used when exporting aegis.

Yes, I'm aware that i can export from aegis without encryption! But it would be convenient if it would take encrypted json files :)

EDIT:
Probably this function for decryption

[replydev]

Hi thank you, this feature is very neat.

I found some time to implement it. I will surely refactor the code, and i will release it in the next version. If you are impatient you can compile the crypto branch by yourself.

Regards

[jonas-w]

Hey thank you, i just found the time to compile it myself. Works like a charm!

1. I think the -k flag is a bit weird for aegis encrypted

2. Isn't the --path flag redundant?

   Wouldn't something like cotp import -k /path/to/db work too? Or has this something to do with how you parse the arguments?

[replydev]

As far i know the path arg is required. What flag would you choose instead of -k?

[jonas-w]

Sorry for leaving you hanging! No worries with the path argument just thought it was redundant.

Maybe as a feature enhancement (just thought about it, because of the -k flag):

• Use for both encrypted and decrypted the -a argument
• but parsing the json and search if it's encrypted or not
• when decrypted just import and if encrypted ask for password