Bug#919281: freerdp2-x11: fails for smartcard login with SCARD_E_INSUFFICIENT_BUFFER
Hi Bernhard, Am 14.01.19 um 18:00 schrieb Bernhard Miklautz: > On Mon, Jan 14, 2019 at 04:46:56PM +0100, Christoph Martin wrote: >> Am 14.01.19 um 15:51 schrieb Bernhard Miklautz: >> Gemalto USB Shell Token V2 (C5B57B07) 01 00 >> >> Possibly identified card (using /usr/share/pcsc/smartcard_list.txt): >> 3B F8 18 00 FF 81 31 FE 45 4A 43 4F 50 76 32 34 31 43 >> The log is attached. > thank you very much! > > The log shows the same problems as reported upstream. > Interestingly, but possible not relates because you don’t use it, the > upstream issues are all related to Yubikeys. Just to make sure, is there > any difference if the Yubikey isn't connected? I use my yubikey only for GPG and SSH. The Gemalto key is for Windows Logins. The other members of my group only use the Gemalto key. And they have the same issue. I just tried to only have the Gemalto key plugged, but the problem is the same. Christoph -- Christoph Martin, Leiter Unix-Systeme Zentrum für Datenverarbeitung, Uni-Mainz, Germany Anselm Franz von Bentzel-Weg 12, 55128 Mainz Telefon: +49(6131)3926337 Instant-Messaging: Jabber/XMPP: mar...@jabber.uni-mainz.de signature.asc Description: OpenPGP digital signature
Bug#919281: freerdp2-x11: fails for smartcard login with SCARD_E_INSUFFICIENT_BUFFER
Hi Christoph, On Mon, Jan 14, 2019 at 04:46:56PM +0100, Christoph Martin wrote: > Am 14.01.19 um 15:51 schrieb Bernhard Miklautz: > Gemalto USB Shell Token V2 (C5B57B07) 01 00 > > Possibly identified card (using /usr/share/pcsc/smartcard_list.txt): > 3B F8 18 00 FF 81 31 FE 45 4A 43 4F 50 76 32 34 31 43 > The log is attached. thank you very much! The log shows the same problems as reported upstream. Interestingly, but possible not relates because you don’t use it, the upstream issues are all related to Yubikeys. Just to make sure, is there any difference if the Yubikey isn't connected? Best regards, Bernhard
Bug#919281: freerdp2-x11: fails for smartcard login with SCARD_E_INSUFFICIENT_BUFFER
Hi, There are two open upstream issues reported with the same error. On Mon, Jan 14, 2019 at 02:40:10PM +0100, Christoph Martin wrote: > in contrast to freerdp-x11 1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2 > freerdp2-x11 fails while trying a smartcard-logon to our several > windows servers. The error messages is: > > [14:11:49:046] [14684:14732] > [WARN][com.freerdp.channels.smartcard.client] - IRP failure: > SCardStatusW (0x000900CC), status: SCARD_E_INSUFFICIENT_BUFFER > (0x8018) > > It might be depending on the size of the certificate we have on our > smartcards. what's your certificate size and the smartcard(s) and reader you use? Could you provide a trace when the error happens (either here or in upstream bug tracker)? Should be sufficient to set the following variables to your environment before you run the failing command export WLOG_PREFIX='%yr%mo%dyT%hr%mi%se.%ml:%fl:%ln:%lv %fn ' export WLOG_APPENDER=FILE export WLOG_FILEAPPENDER_OUTPUT_FILE_PATH=/tmp/ export WLOG_FILEAPPENDER_OUTPUT_FILE_NAME=freerdp.log export WLOG_LEVEL=DEBUG The log file is /tmp/freerdp.log. Best regards, Bernhard
Bug#919281: freerdp2-x11: fails for smartcard login with SCARD_E_INSUFFICIENT_BUFFER
Package: freerdp2-x11 Version: 2.0.0~git20181120.1.e21b72c95+dfsg1-1~bpo9+1 Severity: normal in contrast to freerdp-x11 1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2 freerdp2-x11 fails while trying a smartcard-logon to our several windows servers. The error messages is: [14:11:49:046] [14684:14732] [WARN][com.freerdp.channels.smartcard.client] - IRP failure: SCardStatusW (0x000900CC), status: SCARD_E_INSUFFICIENT_BUFFER (0x8018) It might be depending on the size of the certificate we have on our smartcards. Until about spring last year we could use remmina from stretch-backports, but then it suddenly stopped to work and we could not find a reason. The we switched to freerdp 1 which still works without problems. so freerdp2 is not working as a dropin replacement now. -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (700, 'stable-updates'), (700, 'stable'), (50, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages freerdp2-x11 depends on: ii libc6 2.24-11+deb9u3 ii libfreerdp-client2-2 2.0.0~git20181120.1.e21b72c95+dfsg1-1~bpo9+1 ii libfreerdp2-2 2.0.0~git20181120.1.e21b72c95+dfsg1-1~bpo9+1 ii libwinpr2-2 2.0.0~git20181120.1.e21b72c95+dfsg1-1~bpo9+1 ii libx11-6 2:1.6.4-3+deb9u1 ii libxcursor1 1:1.1.14-1+deb9u2 ii libxext6 2:1.3.3-1+b2 ii libxfixes31:5.0.3-1 ii libxi62:1.7.9-1 ii libxinerama1 2:1.1.3-1+b3 ii libxrandr22:1.5.1-1 ii libxrender1 1:0.9.10-1 ii libxv12:1.0.11-1 freerdp2-x11 recommends no packages. freerdp2-x11 suggests no packages. -- no debconf information < -- Christoph Martin, Leiter Unix-Systeme Zentrum für Datenverarbeitung, Uni-Mainz, Germany Anselm Franz von Bentzel-Weg 12, 55128 Mainz Telefon: +49(6131)3926337 Instant-Messaging: Jabber/XMPP: mar...@jabber.uni-mainz.de signature.asc Description: OpenPGP digital signature
