Currently in v2.2.0 the seed phrase of a newly created wallet is stored encrypted with AES-256 in the config directory. However, the keyring.cfg can have the private key easily extracted using a script I created. It would be best to alter __keyring to decrypt the keyring.cfg file which was encyrpted with the aes helper. This way the keyring rejects attacks at extracting the private key from previous scripts.
Currently in v2.2.0 the seed phrase of a newly created wallet is stored encrypted with AES-256 in the config directory. However, the keyring.cfg can have the private key easily extracted using a script I created. It would be best to alter
__keyringto decrypt the keyring.cfg file which was encyrpted with the aes helper. This way the keyring rejects attacks at extracting the private key from previous scripts.