Hi all,

I've been browsing through version 1.1.0 of apache SSHD for the last few
weeks and have a prototype of the Sftp Subsystem that provides encrypted
reads/writes to the local file system rather than writing to file in
cleartext.  These are some security concerns on our end.

The prototype works, but now I'm rethinking my approach in light of the
fact that I extended the SftpSubsystem and am unsure about its future
moving forward.  Given the fact that its implementation (e.g. process
calling doX") favors heavy self-use, I'm afraid that by extending the class
I'm going to give myself a lot of trouble upgrading SSHD version in the
future.

To that end, would you best recommend that
1) my worries are unfounded and we continue extending SftpSubsystem,
2) we use some wrapper class with an instance of SftpSubsystem (a la
composition over inheritance), or
3) avoid it altogether in favor of some other mechanism?

Thanks for the great project all!

Al

Reply via email to