[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#763118: marked as done (sshd(8): options field in authorized_keys is no longer detected by numbers)

Your message dated Mon, 1 Dec 2025 10:41:16 +0000
with message-id <aS1wzLkb3kWTS8RH@riva.ucam.org>
and subject line Re: Bug#763118: sshd(8): options field in authorized_keys is no longer detected by numbers
has caused the Debian Bug report #763118,
regarding sshd(8): options field in authorized_keys is no longer detected by numbers
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
763118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763118
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: openssh-server
Version: 1:6.6p1-7
Severity: minor

>From sshd(8), under the AUTHORIZED_KEYS FILE FORMAT section:

  The options field is optional; its presence is determined by whether
  the line starts with a number or not (the options field never starts
  with a number).  

This is indeed the case for Protocol 1 public keys, but Protocol 2 keys
don't start with a number either; the presence of the options field is
instead determined by whether or not the first field matches any of the
known keytypes.


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 3.16-2-amd64 (SMP w/3 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages openssh-server depends on:
ii  adduser                3.113+nmu3
ii  debconf [debconf-2.0]  1.5.53
ii  dpkg                   1.17.13
ii  init-system-helpers    1.21
ii  libc6                  2.19-11
ii  libcomerr2             1.42.12-1
ii  libgssapi-krb5-2       1.12.1+dfsg-10
ii  libkrb5-3              1.12.1+dfsg-10
ii  libpam-modules         1.1.8-3.1
ii  libpam-runtime         1.1.8-3.1
ii  libpam0g               1.1.8-3.1
ii  libselinux1            2.3-2
ii  libssl1.0.0            1.0.1i-2
ii  libwrap0               7.6.q-25
ii  lsb-base               4.1+Debian13
ii  openssh-client         1:6.6p1-7
ii  openssh-sftp-server    1:6.6p1-7
ii  procps                 1:3.3.10-1
ii  zlib1g                 1:1.2.8.dfsg-2

Versions of packages openssh-server recommends:
ii  ncurses-term  5.9+20140913-1
ii  xauth         1:1.0.9-1

Versions of packages openssh-server suggests:
pn  molly-guard                      <none>
pn  monkeysphere                     <none>
pn  rssh                             <none>
ii  ssh-askpass-gnome [ssh-askpass]  1:6.6p1-7
pn  ufw                              <none>

-- debconf information excluded

--- End Message ---
--- Begin Message --- 
Source: openssh
Source-Version: 1:7.4p1-1

On Sat, Sep 27, 2014 at 07:14:48PM -0400, Frédéric Brière wrote:

From sshd(8), under the AUTHORIZED_KEYS FILE FORMAT section:


 The options field is optional; its presence is determined by whether
 the line starts with a number or not (the options field never starts
 with a number).

This is indeed the case for Protocol 1 public keys, but Protocol 2 keys
don't start with a number either; the presence of the options field is
instead determined by whether or not the first field matches any of the
known keytypes.


Fixed in OpenSSH 7.4:

  https://anongit.mindrot.org/openssh.git/commit/?id=ffe6549c2f7a999cc5264b873a60322e91862581

Thanks,

--
Colin Watson (he/him)                              [cjwatson@debian.org]

--- End Message ---
Reply to: