similar to: [Bug 1843] ssh should mention ssh-keygen in remote host fingerprint warning

https://bugzilla.mindrot.org/show_bug.cgi?id=1843 Darren Tucker <dtucker at zip.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #7 from Darren Tucker <dtucker

https://bugzilla.mindrot.org/show_bug.cgi?id=1843 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #8 from Damien Miller <djm at mindrot.org> --- Close all resolved bugs after 7.3p1 release

https://bugzilla.mindrot.org/show_bug.cgi?id=1843 Summary: ssh should mention ssh-keyscan in remote host fingerprint warning Product: Portable OpenSSH Version: 5.6p1 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P2 Component: ssh AssignedTo: unassigned-bugs

https://bugzilla.mindrot.org/show_bug.cgi?id=86 Christoph Anton Mitterer <calestyo at scientia.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |calestyo at scientia.net --- Comment #7 from Christoph Anton Mitterer <calestyo at

https://bugzilla.mindrot.org/show_bug.cgi?id=958 Christoph Anton Mitterer <calestyo at scientia.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |calestyo at scientia.net --- Comment #3 from Christoph Anton Mitterer <calestyo at

https://bugzilla.mindrot.org/show_bug.cgi?id=1953 Christoph Anton Mitterer <calestyo at scientia.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |calestyo at scientia.net --- Comment #2 from Christoph Anton Mitterer <calestyo at

https://bugzilla.mindrot.org/show_bug.cgi?id=1993 Christoph Anton Mitterer <calestyo at scientia.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|6.2p1 |6.7p1 --- Comment #4 from Christoph Anton Mitterer <calestyo at scientia.net> --- Hi guys.

https://bugzilla.mindrot.org/show_bug.cgi?id=2000 Christoph Anton Mitterer <calestyo at scientia.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |--- Status|CLOSED |REOPENED --- Comment #6 from Christoph Anton

https://bugzilla.mindrot.org/show_bug.cgi?id=1994 Christoph Anton Mitterer <calestyo at scientia.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #2637| |ok- Flags| | --- Comment #2 from Christoph Anton Mitterer

There were a few notes in this thread that may indicate open areas for development. I forward merely as FYI. http://www.metzdowd.com/pipermail/cryptography/2015-January/024231.html ---------- Forwarded message ---------- From: Peter Gutmann <pgut001 at cs.auckland.ac.nz> Date: Sun, Jan 4, 2015 at 9:29 PM Subject: Re: [Cryptography] Why aren?t we using SSH for everything? To: calestyo at

Damien, What is the best document to use for documentation on SFTP? In other words, if I want to build an SFTP client library based on libssh.a, is there documentation about the series of messages I need to send over the wire? Thanks, ScottN -----Original Message----- From: openssh-unix-dev [mailto:openssh-unix-dev-bounces+scott_n=xypro.com at mindrot.org] On Behalf Of Damien Miller Sent:

Josh Coalson wrote: > --- Christoph Anton Mitterer <calestyo@scientia.net> wrote: > >> There is one thing I forgot to ask last time.... when using that cue >> feature from flag,.. is it possible to store different tags (title, >> composer, etc) for each range? And if so how do I specify this on the >> command line? >> > unfortunately, no. >

Hi, below is a patch to simply mention 'ssh-keygen' when a fingerprint does not match between the known_hosts file and the remote. I find that many people are unaware that ssh-keygen can do this for them. adding a copy-and-pasteable message in the warning will make users more aware. Description: Mention ssh-keygen in ssh fingerprint changed warning Author: Scott Moser <smoser at

https://bugzilla.mindrot.org/show_bug.cgi?id=1861 Summary: strange wording in ssh-keygen manpage Product: Portable OpenSSH Version: 5.8p1 Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P2 Component: Documentation AssignedTo: unassigned-bugs at mindrot.org ReportedBy:

https://bugzilla.mindrot.org/show_bug.cgi?id=1862 Summary: document ECDSA within the "-b" option of the ssh-keygen manpage Product: Portable OpenSSH Version: 5.8p1 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Documentation

https://bugzilla.mindrot.org/show_bug.cgi?id=86 --- Comment #8 from Christoph Anton Mitterer <calestyo at scientia.net> --- taking the 2nd paragraph back... I forgot that one can give the port to ListenAddress ;-) -- 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.

https://bugzilla.mindrot.org/show_bug.cgi?id=1993 --- Comment #10 from Christoph Anton Mitterer <calestyo at scientia.net> --- Created attachment 2638 --> https://bugzilla.mindrot.org/attachment.cgi?id=2638&action=edit ssh -vvv output what happens when a key is auto added for the IP address of an already trusted host -- You are receiving this mail because: You are watching

https://bugzilla.mindrot.org/show_bug.cgi?id=2000 --- Comment #8 from Christoph Anton Mitterer <calestyo at scientia.net> --- Uhm? Well I thought that was obvious... using SSH to remotely execute checks seems desirable because it's a) the protocol meant for doing this b) secure (unlike e.g. NRPE). But without control channel muxing, it's much slower than e.g. NRPE, as all the

https://bugzilla.mindrot.org/show_bug.cgi?id=2000 --- Comment #10 from Christoph Anton Mitterer <calestyo at scientia.net> --- Hmm AFAIU, when not using ControlPersist, that would simply mean that if the last session is closed, the mux closes either, right? This is however undesirable as well for the above use-case: First, considers hosts where only one check runs (i.e. executed via

https://bugzilla.mindrot.org/show_bug.cgi?id=1993 --- Comment #9 from Christoph Anton Mitterer <calestyo at scientia.net> --- (replies to all your comments in one) Hey. Sorry for the delay. (In reply to Darren Tucker from comment #5) > > $ ssh -o StrictHostKeyChecking=no someHost > > Warning: Permanently added the ECDSA host key for IP address > >