From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [SECURITY] p7zip: CVE-2015-1038
Date: Fri, 12 Feb 2016 19:05:00 -0000 [thread overview]
Message-ID: <87mvr5g36j.fsf@Rainer.invalid> (raw)
In-Reply-To: <BAY169-W8343B71FCE33C37B2C4219A7A80@phx.gbl> (Tony Kelman's message of "Wed, 10 Feb 2016 19:59:37 -0800")
Tony Kelman writes:
> I'm not very familiar with the intricacies of ssh auth options, as you
> can probably guess. I tried removing ~/.ssh/known_hosts (backing up to
> a different file name) but no change. Is there a cygport or sftp or ssh
> option via command line or environment variable that I can set for more
> verbose debugging output that might tell us what's going on here?
You probably need to connect to cygwin.com with ssh on the command line
once in order to accept the prompt about the changed (or unknown) host
key. You can then rely on cygport's canned use of ssh again.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2016-02-12 19:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 16:58 Yaakov Selkowitz
2016-01-29 20:11 ` Tony Kelman
[not found] ` <BAY169-W401D7F793D3E837DBF61F5A7DC0@phx.gbl>
2016-01-30 8:13 ` Tony Kelman
2016-02-08 13:54 ` Corinna Vinschen
2016-02-09 1:42 ` Tony Kelman
2016-02-09 10:40 ` Corinna Vinschen
2016-02-09 22:48 ` Tony Kelman
2016-02-10 10:40 ` Corinna Vinschen
2016-02-10 19:01 ` Achim Gratz
2016-02-11 3:59 ` Tony Kelman
2016-02-12 19:05 ` Achim Gratz [this message]
2016-02-13 6:53 ` Tony Kelman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mvr5g36j.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).