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

Will <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|enhancement                 |normal
                 CC|                            |[email protected]
            Version|-current                    |6.6p1
                 OS|All                         |Mac OS X

--- Comment #6 from Will <[email protected]> ---
This is still broken on Mac OS X, preventing me from writing portable
scripts. Installed latest 6.6p1 and it's still broken, even though this
bug seems very old. Works fine on my Linux systems:

will@x ~$ which ssh
/usr/local/bin/ssh
will@x ~$ ssh -V
OpenSSH_6.6p1, OpenSSL 1.0.1h 5 Jun 2014
will@x ~$ ssh-keyscan -t rsa login.itd.umich.edu | ssh-keygen -l -f
/dev/stdin
# login.itd.umich.edu SSH-1.99-OpenSSH_5.2p1-hpn13v6
/dev/stdin is not a public key file.
will@x ~$ ssh-keygen -l -f <(ssh-keyscan -t rsa login.itd.umich.edu)
# login.itd.umich.edu SSH-1.99-OpenSSH_5.2p1-hpn13v6
/dev/fd/63 is not a public key file.
will@x ~$ uname -a
Darwin x.local 13.3.0 Darwin Kernel Version 13.3.0: Tue Jun  3 21:27:35
PDT 2014; root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64
will@x ~$ sw_vers -productVersion
10.9.4
will@x ~$ system_profiler SPSoftwareDataType
Software:

    System Software Overview:

      System Version: OS X 10.9.4 (13E28)
      Kernel Version: Darwin 13.3.0
      Boot Volume: Macintosh HD
      Boot Mode: Normal
      Computer Name: x
      User Name: Will X (will)
      Secure Virtual Memory: Enabled
      Time since boot: 8 days 4:23

will@x ~$ which ssh-keygen
/usr/local/bin/ssh-keygen
will@x ~$

Temporary files are the only way on Mac.

-- 
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.
_______________________________________________
openssh-bugs mailing list
[email protected]
https://lists.mindrot.org/mailman/listinfo/openssh-bugs

Reply via email to