gmane.comp.lib.muscle archive
410 archived articles, newest first (page 1 of 5). Latest articles →
Mailing list migration to lists.infradead.org
Sun, 5 Nov 2017 14:17:33 +0100Re: Mailing list migration to lists.infradead.org
Fri, 17 Nov 2017 18:31:53 +0100Omnikey 5022 CL and authentication Ultralight C
Fri, 27 Oct 2017 13:58:17 +0200Re: ScardControl under Linux?
Fri, 27 Oct 2017 12:59:58 +0200ScardControl under Linux?
Fri, 27 Oct 2017 12:03:32 +0200Re: acsccid 1.1.5 Released
Fri, 27 Oct 2017 15:00:27 +0800acsccid 1.1.5 Released
Fri, 27 Oct 2017 14:54:33 +0800Re: How to find out which process is accessing the card?
Tue, 24 Oct 2017 13:32:34 +0200Re: How to find out which process is accessing the card?
Tue, 24 Oct 2017 10:28:35 +0200Re: new AK910 reader spotted
Fri, 20 Oct 2017 12:58:48 -0200new AK910 reader spotted
Fri, 20 Oct 2017 15:37:46 +0200Re: How to replace/move the MUSCLE mailing list?
Fri, 13 Oct 2017 15:28:33 +0200New version of libccid: 1.4.28
Wed, 11 Oct 2017 14:29:22 +0200Re: How to replace/move the MUSCLE mailing list?
Fri, 06 Oct 2017 08:24:23 +0000Re: How to replace/move the MUSCLE mailing list?
Thu, 5 Oct 2017 14:21:22 +0200Re: How to replace/move the MUSCLE mailing list?
Thu, 5 Oct 2017 12:45:09 +0200Re: How to replace/move the MUSCLE mailing list?
Thu, 05 Oct 2017 11:23:06 +0100Re: How to replace/move the MUSCLE mailing list?
Thu, 5 Oct 2017 12:08:06 +0200Re: How to replace/move the MUSCLE mailing list?
Thu, 5 Oct 2017 09:13:40 +0200Re: How to replace/move the MUSCLE mailing list?
Wed, 4 Oct 2017 20:49:17 +0200Re: How to replace/move the MUSCLE mailing list?
Wed, 4 Oct 2017 14:40:29 +0200Re: How to replace/move the MUSCLE mailing list?
Tue, 03 Oct 2017 18:43:32 +0100Re: [Non-DoD Source] How to replace/move the MUSCLE mailing list?
Tue, 3 Oct 2017 17:31:24 +0000How to replace/move the MUSCLE mailing list?
Sun, 1 Oct 2017 19:11:32 +0200Re: How to find out which process is accessing the card?
Thu, 28 Sep 2017 14:45:42 +0200How to find out which process is accessing the card?
Wed, 27 Sep 2017 21:58:25 +0200Re: CCID_Receive Card absent or mute
Thu, 14 Sep 2017 10:13:15 +0200Re: CCID_Receive Card absent or mute
Wed, 13 Sep 2017 10:52:13 -0700Re: CCID_Receive Card absent or mute
Wed, 13 Sep 2017 10:06:14 +0200Re: CCID_Receive Card absent or mute
Tue, 12 Sep 2017 14:17:29 -0700Re: EZ100PU/PR Linux 64 bit
Sun, 10 Sep 2017 09:42:08 +0200Re: EZ100PU/PR Linux 64 bit
Sat, 9 Sep 2017 13:18:21 +0200EZ100PU/PR Linux 64 bit
Sat, 9 Sep 2017 12:43:12 +0200Re: Fwd: Broadcom 5880
Sat, 2 Sep 2017 10:12:10 -0400Re: Fwd: Broadcom 5880
Sat, 2 Sep 2017 09:57:38 +0200Fwd: Broadcom 5880
Fri, 1 Sep 2017 12:13:42 -0400Re: CCID_Receive Card absent or mute
Tue, 29 Aug 2017 09:57:54 +0200CCID_Receive Card absent or mute
Mon, 28 Aug 2017 14:13:55 -0700Re: RFC - one old and one new bluetooth device driver.
Thu, 17 Aug 2017 22:31:49 +0200Re: RFC - one old and one new bluetooth device driver.
Thu, 17 Aug 2017 11:01:44 +0200Re: RFC - one old and one new bluetooth device driver.
Wed, 16 Aug 2017 09:01:02 +0100Re: RFC - one old and one new bluetooth device driver.
Wed, 16 Aug 2017 06:50:37 +0000Re: Using pcsclite with multiple cards through one reader
Wed, 16 Aug 2017 06:36:20 +0000Using pcsclite with multiple cards through one reader
Tue, 15 Aug 2017 19:04:06 +0000Re: RFC - one old and one new bluetooth device driver.
Tue, 15 Aug 2017 12:25:28 +0100Re: RFC - one old and one new bluetooth device driver.
Tue, 15 Aug 2017 15:31:09 +0800RFC - one old and one new bluetooth device driver.
Mon, 14 Aug 2017 13:53:37 +0100Re: Valgrind error in SCardEstablishContext(): socketcall.connect points to uninitialized bytes
Mon, 31 Jul 2017 10:03:27 +0200Re: Fail to detect smartcard from reconnected reader
Fri, 21 Jul 2017 14:20:08 +0200Fail to detect smartcard from reconnected reader
Fri, 21 Jul 2017 13:46:33 +0200libgen_ifd.so
Wed, 19 Jul 2017 17:43:30 +0000Valgrind error in SCardEstablishContext(): socketcall.connect points to uninitialized bytes
Wed, 19 Jul 2017 15:14:17 +0200Re: Cyberjack e-com on openSuse 42.2 fails
Thu, 13 Jul 2017 21:27:19 +0200Re: Cyberjack e-com on openSuse 42.2 fails
Thu, 13 Jul 2017 18:58:14 +0200Re: Cyberjack e-com on openSuse 42.2 fails
Thu, 13 Jul 2017 18:54:15 +0200Re: Cyberjack e-com on openSuse 42.2 fails
Thu, 13 Jul 2017 17:39:30 +0200Re: Cyberjack e-com on openSuse 42.2 fails
Thu, 13 Jul 2017 14:21:50 +0200Re: Cyberjack e-com on openSuse 42.2 fails
Thu, 13 Jul 2017 13:57:02 +0200Re: Cyberjack e-com on openSuse 42.2 fails
Thu, 13 Jul 2017 13:50:43 +0200Re: Cyberjack e-com on openSuse 42.2 fails
Thu, 13 Jul 2017 13:21:26 +0200Re: Cyberjack e-com on openSuse 42.2 fails
Thu, 13 Jul 2017 10:35:33 +0200Re: Cyberjack e-com on openSuse 42.2 fails
Thu, 13 Jul 2017 10:33:53 +0200Re: Cyberjack e-com on openSuse 42.2 fails
Thu, 13 Jul 2017 10:15:38 +0200Re: Cyberjack e-com on openSuse 42.2 fails
Thu, 13 Jul 2017 10:08:54 +0200Re: Cyberjack e-com on openSuse 42.2 fails
Thu, 13 Jul 2017 09:55:36 +0200Re: Cyberjack e-com on openSuse 42.2 fails
Thu, 13 Jul 2017 09:47:45 +0200Cyberjack e-com on openSuse 42.2 fails
Thu, 13 Jul 2017 09:25:40 +0200Re: Real time issue for register / unregister to READER_STATE_CHANGE event.
Fri, 7 Jul 2017 16:54:04 +0200Re: Real time issue for register / unregister to READER_STATE_CHANGE event.
Fri, 7 Jul 2017 14:45:51 +0000Re: Real time issue for register / unregister to READER_STATE_CHANGE event.
Fri, 7 Jul 2017 15:40:09 +0200Re: Real time issue for register / unregister to READER_STATE_CHANGE event.
Wed, 5 Jul 2017 08:11:31 +0000Re: Real time issue for register / unregister to READER_STATE_CHANGE event.
Tue, 4 Jul 2017 19:09:27 +0200Re: Real time issue for register / unregister to READER_STATE_CHANGE event.
Tue, 4 Jul 2017 13:09:20 +0000Re: Real time issue for register / unregister to READER_STATE_CHANGE event.
Tue, 4 Jul 2017 15:03:11 +0200Real time issue for register / unregister to READER_STATE_CHANGE event.
Tue, 4 Jul 2017 12:20:00 +0000New pcsc-lite 1.8.22
Sat, 17 Jun 2017 10:23:08 +0200Re: A recent change causes SCardCancel() to block?
Thu, 15 Jun 2017 15:00:41 +0200Re: A recent change causes SCardCancel() to block?
Wed, 14 Jun 2017 16:05:51 +0200Re: Jinmuyu MR800 card reader problem
Wed, 14 Jun 2017 15:37:12 +0200A recent change causes SCardCancel() to block?
Wed, 14 Jun 2017 12:43:46 +0300Re: Jinmuyu MR800 card reader problem
Wed, 14 Jun 2017 05:22:27 +0200Re: Jinmuyu MR800 card reader problem
Mon, 12 Jun 2017 18:50:55 +0200Re: Jinmuyu MR800 card reader problem
Mon, 12 Jun 2017 09:15:36 +0200Re: Jinmuyu MR800 card reader problem
Mon, 12 Jun 2017 06:33:55 +0200Re: Jinmuyu MR800 card reader problem
Sun, 11 Jun 2017 15:58:18 +0200Re: Jinmuyu MR800 card reader problem
Sun, 11 Jun 2017 11:58:36 +0200Re: Jinmuyu MR800 card reader problem
Sun, 11 Jun 2017 11:14:51 +0200Jinmuyu MR800 card reader problem
Sun, 11 Jun 2017 09:45:28 +0200Re: pcscd can not be startet with log level "info"
Tue, 6 Jun 2017 18:03:13 +0200pcscd can not be startet with log level "info"
Tue, 6 Jun 2017 17:09:37 +0200Re: Gemalto (was Gemplus) GemPC Key SmartCard Reader not working in debian stretch
Tue, 30 May 2017 16:31:21 +0200Re: Gemalto (was Gemplus) GemPC Key SmartCard Reader not working in debian stretch
Tue, 30 May 2017 13:57:57 +0000Re: Gemalto (was Gemplus) GemPC Key SmartCard Reader not working in debian stretch
Mon, 29 May 2017 11:08:50 +0200Re: Gemalto (was Gemplus) GemPC Key SmartCard Reader not working in debian stretch
Mon, 29 May 2017 09:18:43 +0200Re: Gemalto (was Gemplus) GemPC Key SmartCard Reader not working in debian stretch
Sun, 28 May 2017 21:28:28 +0000Re: Gemalto (was Gemplus) GemPC Key SmartCard Reader not working in debian stretch
Sun, 28 May 2017 23:23:22 +0200New version of pcsc-tools: 1.5.0, 1.5.1, 1.5.2
Sun, 28 May 2017 23:22:37 +0200Re: Gemalto (was Gemplus) GemPC Key SmartCard Reader not working in debian stretch
Sun, 28 May 2017 21:00:27 +0000Re: Gemalto (was Gemplus) GemPC Key SmartCard Reader not working in debian stretch
Sun, 28 May 2017 16:27:39 +0200Re: Gemalto (was Gemplus) GemPC Key SmartCard Reader not working in debian stretch
Thu, 25 May 2017 19:09:49 +0000
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.