Future plans? Moving keys to file-based storage.

Hey, I was curious what your plan is for improvements on this module. I saw your Feature list in the v3 branch, but wanted to see if there was a way to plug in and help.

I had walked away from this module a while back, I believe there was some incompatibility with cipher specs offered and what my Info Sec team allowed. So I couldn't use this module. (It looks like you have added some ciphers since then.)

I had opened #167, and had provided a solution for it #169. But it seems you were wanting to go file-based for compatibility with Linux/Mac OS, so it never got incorporated.

Would it be of interest to build a function that can CRUD against a .ssh/known_hosts file?
(I would just have to think where to store the file on a Windows host. Maybe creating a folder in %AppData%, much like PSReadline does.)
(I also don't own a Mac, so I am not sure if this is different than Linux/Unix.)

Let me know your thoughts.

Review the v3 Feature list and the context in issues #167 and #169 before assessing file-based storage for .ssh/known_hosts. Done would require an agreed cross-platform location and a defined CRUD scope, rather than the general planning question currently posed.