thinkfinger in hardy definitely includes the patch to fix this
** Changed in: thinkfinger (Ubuntu)
Status: Incomplete => Fix Released
--
sshd core dumps while trying to connect with a password
https://bugs.launchpad.net/bugs/208668
You received this bug notification because you are a memb
This is a known bug upstream, with a patch to fix it. upstream was going
to put up a final release to include these patches, but it hasn't
happened yet. Thinkfinger in hardy is provided from upstream SVN + some
extra patches not in SVN, but occasionally puts hald-input-addon (I
think) into an infi
Deinstalled the fingerprint packages
[EMAIL PROTECTED]:~$ dpkg -l | grep finger
ii finger 0.17-11
user information lookup program
ii libpam-thinkfinger 0.3~ppa9
PAM module for t
** Attachment added: "common-auth"
http://launchpadlibrarian.net/13154265/common-auth
--
sshd core dumps while trying to connect with a password
https://bugs.launchpad.net/bugs/208668
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
** Attachment added: "ssh"
http://launchpadlibrarian.net/13154252/ssh
--
sshd core dumps while trying to connect with a password
https://bugs.launchpad.net/bugs/208668
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
Ah, thinkfinger doesn't ship in gutsy. I do provide it in a PPA, but
this should be fixed in hardy and in the long run thinkfinger will
migrate to fprint. Unfortunately, Launchpad PPAs have no bug reporting
facilities.
So on the one hand, this bug does exist, but on the other hand, Ubuntu
does
I just installed thinkfinger on a ~month old hardy install, configured it to
accept my fingerprint, and installed sshd.
I can authenticate with sudo with my finger, so I believe tf is working. I can
also ssh to localhost without sshd dying.
ie, I cannot reproduce this bug.
--
sshd core dumps w
This looks like a thinkfinger bug; "Error: Bad address." is (I think)
being emitted by _libthinkfinger_store_fingerprint, and indicates some
kind of memory corruption within that library. Perhaps allocating a 10KB
array on the stack is too much for it? It's hard to be sure from here,
though.
Perha
>>Can't reproduce in hardy.
And now? Do I have to wait for hardy or do you need more information?
regards
Bernd
Nicolas Valcárcel (nxvl) wrote:
> Can't reproduce in hardy.
>
> [EMAIL PROTECTED]:~$ sudo /usr/sbin/sshd -p 1234 -d
> debug1: sshd version OpenSSH_4.7p1 Debian-5ubuntu1
> debug1: re
Can't reproduce in hardy.
[EMAIL PROTECTED]:~$ sudo /usr/sbin/sshd -p 1234 -d
debug1: sshd version OpenSSH_4.7p1 Debian-5ubuntu1
debug1: read PEM private key done: type RSA
debug1: private host key: #0 type 1 RSA
debug1: read PEM private key done: type DSA
debug1: private host key: #1 type 2 DSA
10 matches
Mail list logo
