On Thu, 3 Nov 2022, Mikolaj Kucharski wrote:
> On Thu, Nov 03, 2022 at 07:06:48AM +, Mikolaj Kucharski wrote:
> > Hi,
> >
> > I'm using below type of config for few years now. Today I've upgraded to:
> >
> >
> > OpenBSD 7.2-current (GENERIC.MP) #823: Wed Nov 2 11:56:37 MDT 2022
> >
On Mon, 27 Dec 2021, Damien Miller wrote:
> The specific problem was that I was relying on authmethod_lookup() in
> userauth_finish() to get the canonical authentication method name, but
> this lookup function implicitly checks whether the authentication method
> is enabled, and I di
On Mon, 27 Dec 2021, Damien Miller wrote:
> On Sun, 26 Dec 2021, Nam Nguyen wrote:
>
> > >Synopsis: ssh anoncvs regression: Connection closed
> > >Category: user
> > >Environment:
> > System : OpenBSD 7.0
> > Details : OpenBSD 7.
On Sun, 26 Dec 2021, Nam Nguyen wrote:
> >Synopsis:ssh anoncvs regression: Connection closed
> >Category:user
> >Environment:
> System : OpenBSD 7.0
> Details : OpenBSD 7.0-current (GENERIC) #198: Sat Dec 25 16:22:02
> MST 2021
>
>
Thanks - I just committed a fix. Will look at adding a regress test
to catch similar cases.
On Tue, 8 Jun 2021, Lucas wrote:
> Hi bugs@, Damien,
>
> I updated to a really recent snapshot
>
> oolong$ sysctl kern.version
>
>
On Sat, 5 Jun 2021, Daniel Jakots wrote:
> Hi,
>
> I updated some machines of mine to a newer snapshot and got some
> problems with sshd.
>
> Old snapshot is from 2021-05-19.
> New snapshot is from 2021-06-05 (today).
>
> I use the default config (only change is LogLevel VERBOSE) and at the
>
On Wed, 26 May 2021, James Cook wrote:
> On Wed, May 26, 2021 at 10:26:00AM +1000, Damien Miller wrote:
> >
> > On Sat, 22 May 2021, James Cook wrote:
> >
> > > >Synopsis:ssh segfault: hostkeys_check_old passes NULL to
> > > >
On Sat, 22 May 2021, James Cook wrote:
> >Synopsis:ssh segfault: hostkeys_check_old passes NULL to sshkey_ssh_name
> >Category:user
> >Environment:
> System : OpenBSD 6.9
> Details : OpenBSD 6.9-current (GENERIC.MP) #28: Wed May 19 16:59:40
> MDT 2021
>
ugh, that's embarassing
ok & thanks djm
On Mon, 21 Dec 2020, Theo Buehler wrote:
> On Mon, Dec 21, 2020 at 10:15:33AM +0100, Theo Buehler wrote:
> > On Mon, Dec 21, 2020 at 08:10:59PM +1100, Damien Miller wrote:
> > > Sorry, this snuck back in along with another com
Sorry, this snuck back in along with another commit.
Does this fix it?
diff --git a/readconf.c b/readconf.c
index cec6844..85e8c6f 100644
--- a/readconf.c
+++ b/readconf.c
@@ -2769,7 +2769,7 @@ parse_jump(const char *s, Options *o, int active)
{
char *orig, *sdup, *cp;
char
On Thu, 29 Oct 2020, Jeremie Courreges-Anglas wrote:
> On Thu, Oct 29 2020, Damien Miller wrote:
> > On Wed, 28 Oct 2020, Jeremie Courreges-Anglas wrote:
> >
> >> On Wed, Oct 28 2020, Damien Miller wrote:
> >> > On Mon, 26 Oct 2020, Jeremie Courreges-Anglas
On Wed, 28 Oct 2020, Jeremie Courreges-Anglas wrote:
> On Wed, Oct 28 2020, Damien Miller wrote:
> > On Mon, 26 Oct 2020, Jeremie Courreges-Anglas wrote:
> >
> >> On Fri, Oct 23 2020, Damien Miller wrote:
> >> > On Fri, 23 Oct 2020, Jeremie Courreges-Ang
On Mon, 26 Oct 2020, Jeremie Courreges-Anglas wrote:
> On Fri, Oct 23 2020, Damien Miller wrote:
> > On Fri, 23 Oct 2020, Jeremie Courreges-Anglas wrote:
> >
> >>
> >> I upgraded my ports builder from snaps yesterday and I hit this when
> >> r
On Mon, 26 Oct 2020, Jeremie Courreges-Anglas wrote:
> > I think these were the problems that I fixed around 2020/10/14. If
> > you remove line 12 from your known_hosts and reconnect with a ssh
> > built after that then you should be fine.
>
> Indeed I'm fine after removing line 12:
>
> --8<--
On Fri, 23 Oct 2020, Jeremie Courreges-Anglas wrote:
>
> I upgraded my ports builder from snaps yesterday and I hit this when
> running cvs up:
>
> --8<--
> russell ~$ ssh anon...@ftp.hostserver.de
> Warning: the ED25519 host key for 'ftp.hostserver.de' differs from the key
> for the IP
On Mon, 31 Aug 2020, Evan Tann wrote:
> Hi Damien,
>
> Sure thing. Please see the output of `ssh -vvv user@host` below.
Thanks for the quick reply.
> debug1: ssh-sk-helper: ready to sign with key ECDSA-SK, provider internal:
> msg len 245, compat 0x400
> debug1: sshsk_sign: provider
On Mon, 31 Aug 2020, open...@evantann.com wrote:
> >Synopsis:ecdsa-sk no longer works with latest snapshot
> >Category:
> >Environment:
> System : OpenBSD 6.7
> Details : OpenBSD 6.7-current (GENERIC.MP) #52: Sun Aug 30 17:55:06
> MDT 2020
>
>
On Mon, 21 Oct 2019, Ted Unangst wrote:
> Damien Miller wrote:
> > On Sun, 20 Oct 2019, Ted Unangst wrote:
> >
> > > Ah, so when this happens, it's on a machine that doesn't have
> > > id_ed25519.pub.
> > > Here's a before and after ssh -vvv fo
On Sun, 20 Oct 2019, Ted Unangst wrote:
> Ah, so when this happens, it's on a machine that doesn't have id_ed25519.pub.
> Here's a before and after ssh -vvv for reference.
ah, so you have just the private key id_ed25519 and no corresponding
pubkey on this machine?
So, what usually happens is
On Sun, 20 Oct 2019, Ted Unangst wrote:
> I have two OpenBSD machines, let's call them laptop and desktop. desktop is a
> bit older, and has a ecdsa-sha2-nistp256 key in .ssh/authorized_keys. laptop
> is configured with a ssh-ed25519 .ssh/id_ed25519 key file. The keyfile has a
> password and I
I've reverted it
On Wed, 7 Mar 2018, Stuart Henderson wrote:
> On 2018/03/03 04:52, Klemens Nanni wrote:
> > Just upgraded the latest snapshot
> >
> > OpenBSD 6.3-beta (GENERIC.MP) #25: Fri Mar 2 14:41:23 MST 2018
> >
> > The following ssh_config(5) snippet is now broken:
> >
> > Match
can you demonstrate this attack with small-modulus RSA key?
E.g. the attached
On Tue, 16 Jan 2018, Gabriel Withington wrote:
> There is a serious flaw in cryptography based on semiprimes. While attempts
> at breaking such cryptography typically focus on factoring semiprimes, the
> approach I
22 matches
Mail list logo
