I am unsure if anyone had already suggested this, or even if it's in the pipeline or a feature I have not seen in the config... but I was
wondering if it was possible or will be possible to add a public SSH key to Mystic for a user so that instead of logging in via SSH with a
username and password, a public key can be used so that no login details
I don't think this is something I am planning to add anytime soon.
The SSH server already presents a public key, but for authentication I think you'd have to manually generate a private SSL key for each individual user and send it to them (technically this could be automated by Mystic using e-mail or something).
But then the user would have to download the key and import it into the SSH client's keystore. Their client would have to support doing this, which I am not sure any BBS-related SSH clients do.
I am not even sure that cryptlib allows for both authentication by SSL key
and password at the same time, I would have to check that it can even support it. I am not sure the average user would grasp this concept and be willing
to jump through so many hoops to get up and going.
--- Mystic BBS v1.12 A42 2019/01/25 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)