openssh bugs - Nov 2019 - [Bug 3086] New: Ssh, scp (6.2p2 or 7.4p1) can't support the way to enter the private key password in a non-interactive way.

https://bugzilla.mindrot.org/show_bug.cgi?id=3086

            Bug ID: 3086
           Summary: Ssh, scp (6.2p2 or 7.4p1) can't support the way to
                    enter the private key password in a non-interactive
                    way.
           Product: Portable OpenSSH
           Version: 7.4p1
          Hardware: ix86
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: ssh
          Assignee: unassigned-bugs at mindrot.org
          Reporter: wuzhao1024 at sina.com

Ssh and scp (6.2p2 or 7.4p1) can't support the way to input the private
key password in a non-interactive manner. As a result, the program
automatically executes ssh/scp, which is difficult to use. Generally,
the private key of the null password can only be used, which poses a
security risk. At the same time, private key encryption is an optional
method. If you use errors, there is also a security risk. It is
recommended that the software support automatic encryption of private
keys, which is safe by default.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=3086

Damien Miller <djm at mindrot.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED
             Blocks|                            |3162
                 CC|                            |djm at mindrot.org
         Depends on|                            |69

--- Comment #1 from Damien Miller <djm at mindrot.org> ---
Generally your best option in this case it to use ssh-agent. It is
possible to ssh-add passworded keys to an agent by passing the password
on stdin.

In OpenSSH 8.4, it will also be possible to force the use of
$SSH_ASKPASS via the $SSH_ASKPASS_REQUIRE environment (see bug #69),
which might offer another approach for you.


Referenced Bugs:

https://bugzilla.mindrot.org/show_bug.cgi?id=69
[Bug 69] Generalize SSH_ASKPASS
https://bugzilla.mindrot.org/show_bug.cgi?id=3162
[Bug 3162] Tracking bug for 8.4 release
-- 
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=3086

Darren Tucker <dtucker at dtucker.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #2 from Darren Tucker <dtucker at dtucker.net> ---
Mass close of all bugs fixed in 8.4 release.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.