currentlyUserInfoSshSessionFactory just looks in the .jsch-userinfo file for the passphrase, that's the only option
ideallyUseerInfoSshSessionFactory could ask for a passphrase the first time per session then save it encrypted (see issue #14) using AES. If the AES key is a randon number stored in JGit as a constant, then it will be different every session, and so passed .jsch-userinfo files would be invalid and deleted, and user would be prompted to reenter their passphrase. If that doesn't work some other system, like once per day IE use the date as the AES key.
currently
UserInfoSshSessionFactoryjust looks in the.jsch-userinfofile for the passphrase, that's the only optionideally
UseerInfoSshSessionFactorycould ask for a passphrase the first time per session then save it encrypted (see issue #14) using AES. If the AES key is a randon number stored in JGit as a constant, then it will be different every session, and so passed.jsch-userinfofiles would be invalid and deleted, and user would be prompted to reenter their passphrase. If that doesn't work some other system, like once per day IE use the date as the AES key.