Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/dropbear: security bump version to 2026.92
Date: Fri, 10 Jul 2026 18:28:47 +0200	[thread overview]
Message-ID: <92970db0171d49a50a0a85052f18e884@free.fr> (raw)
In-Reply-To: <20260707185207.2387124-1-bernd@kuhls.net>

On 07/07/2026 20:52, Bernd Kuhls wrote:
> https://matt.ucc.asn.au/dropbear/CHANGES
> 
> - Security: server: Don't allow -B (accept blank password) with
>   -t (two factor auth). If run with -t and -B a user configured with a
>   blank password would be allowed to log in without pubkey auth.
>   
> https://github.com/mkj/dropbear/commit/23ec78285639edf068d86bb96f91cba755039740
>   Reported by nvidia
> 
> - Security: server: Fix parsing of long authorized_keys lines.
>   The remainder of a long line would be handled as the start of a new 
> line.
>   In the case where external programs add semi-trusted public keys to
>   authorized_keys, a crafted key might bypass restrictions such as 
> "command=".
>   
> https://github.com/mkj/dropbear/commit/8d8e1930b866eb44135ae393a793cbeb03b6b9d6
>   Reported by nvidia
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>

Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-07-10 16:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07 18:52 [Buildroot] [PATCH 1/1] package/dropbear: security bump version to 2026.92 Bernd Kuhls
2026-07-10 16:28 ` Julien Olivain via buildroot [this message]
2026-07-17 15:47 ` Thomas Perale via buildroot

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=92970db0171d49a50a0a85052f18e884@free.fr \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=ju.o@free.fr \
    /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