Your message dated Fri, 3 May 2024 22:36:59 +0200
with message-id <e9dfe636-1e83-4b59-9f4e-2517bb80e...@debian.org>
and subject line Issue was fixed long ago
has caused the Debian Bug report #772810,
regarding libpam-yubico: dpkg-reconfigure -plow libpam-yubico fails due to 
parameter escaping
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 ow...@bugs.debian.org
immediately.)


-- 
772810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772810
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpam-yubico
Version: 2.12-1
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
   
   + I need libpam-yubico-based authentication with my own auth-servers

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   
   + running dpkg-reconfigure -plow libpam-yubico and entering parameters
     (mode=client try_first_pass id=myid key=mykey 
url=http://server:port/wsapi/2.0/verify?id=%d&otp=%s) 
     as per documentation
   
   
   * What was the outcome of this action?

   + for stable:
    # dpkg-reconfigure -plow libpam-yubico
    sed: -e expression #1, char 75: unknown option to `s'

   + for testing: (libpam-yubico 2.17-2)
    # grep yubico /etc/pam.d/common-auth
    auth        required        pam_yubico.so mode=client try_first_pass 
id=myid key=mykey 
url=http://server:port/wsapi/2.0/verify?id=%d#DEBCONF_REPLACEotp=%s

   * What outcome did you expect instead?

   + I expected the parameters to be set exactly the way I specified them

I reported this bug against stable, please note that this applies to testing
as well.



-- System Information:
Debian Release: 7.7
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages libpam-yubico depends on:
ii  debconf [debconf-2.0]  1.5.49
ii  libc6                  2.13-38+deb7u6
ii  libldap-2.4-2          2.4.31-1+nmu2
ii  libpam-runtime         1.1.3-7.1
ii  libpam0g               1.1.3-7.1
ii  libykclient3           2.6-1
ii  libykpers-1-1          1.7.0-1
ii  libyubikey0            1.8-1

libpam-yubico recommends no packages.

libpam-yubico suggests no packages.

-- debconf information:
* libpam-yubico/module_args: mode=client try_first_pass id=N key=K

--- End Message ---
--- Begin Message ---
Hey,

thanks for your report - the issue was fixed within debian long ago, just the report was open all the time.

With best regards
Patrick
--
 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  win...@debian.org/patr...@winnertz.eu
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: 8D208172388840811B85DA1CC6D50A4188C70E43
 ⠈⠳⣄

The people who refer to the pandemic in the past tense and climate change in the future tense are the reason everything is going to shit.
--- End Message ---

Reply via email to