[
https://issues.apache.org/jira/browse/SSHD-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16718870#comment-16718870
]
Thomas Wolf commented on SSHD-708:
----------------------------------
{quote}
The code is *generic* - i.e., if we ever replace the {{bcrypt}} with something
else, this is how the I would like the {{catch}} block to behave, so I don't
see the harm in writing the code in this manner now rather than later.
{quote}
I had already noticed that we have quite different philosophies about this. :-)
I'm nearer the opposite end of the spectrum: do what's needed and not more, and
generalize later when and if a need arises. Yes, with a general _library_ one
needs to plan and build in _some_ genericity and configurability from the
beginning, but even then I like to keep interfaces as narrow and simple as
possible and generalize further only when there's a real need for it. I don't
think OpenSSH will switch from bcrypt to something else soon...
Anyway, it's allright as it is.
> Add support for password encrypted OpenSSH private key files
> ------------------------------------------------------------
>
> Key: SSHD-708
> URL: https://issues.apache.org/jira/browse/SSHD-708
> Project: MINA SSHD
> Issue Type: Improvement
> Affects Versions: 1.4.0
> Reporter: Goldstein Lyor
> Assignee: Goldstein Lyor
> Priority: Minor
> Fix For: 2.1.1
>
>
> The current code supports only reading un-encrypted private key files
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
