WTware - using chip card reader terminal with Raspberry v3

Post a reply

Smilies
:D :) :( :o :shock: :? 8) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :!: :?: :idea: :arrow: :| :mrgreen:

BBCode is OFF
Smilies are ON

Topic review
   

Expand view Topic review: WTware - using chip card reader terminal with Raspberry v3

Re: WTware - using chip card reader terminal with Raspberry v3

by aka » Thu Feb 08, 2018 8:05 pm

jktz90 wrote: Thu Feb 08, 2018 1:48 pm Is it safe for me to update to the current version of WTware
Yes.

Re: WTware - using chip card reader terminal with Raspberry v3

by jktz90 » Thu Feb 08, 2018 1:48 pm

Is it safe for me to update to the current version of WTware or is the protocol not implemented?

Thanks

Re: WTware - using chip card reader terminal with Raspberry v3

by jktz90 » Mon Nov 13, 2017 2:20 am

Works perfectly.
Much appreciated.
Attachments
logworking.txt
(238.08 KiB) Downloaded 461 times

Re: WTware - using chip card reader terminal with Raspberry v3

by aka » Mon Nov 13, 2017 12:26 am

Please, try this: http://pxe.ru/files/testing/201711130123.zip
And show me the log.

Re: WTware - using chip card reader terminal with Raspberry v3

by jktz90 » Sat Nov 11, 2017 9:30 pm

Here the rdesktop log.
Clean Ubuntu MATE installation - nothing added besides rdesktop and permission for ttyUSB0.
Attachments
rdesktoplog.txt
(132.75 KiB) Downloaded 433 times

Re: WTware - using chip card reader terminal with Raspberry v3

by aka » Sat Nov 11, 2017 4:26 pm

Try this on Ubuntu:

http://pxe.ru/files/testing/201711111721.zip

./rdesktop ...options..it..need.. > /tmp/log.txt

Re: WTware - using chip card reader terminal with Raspberry v3

by jktz90 » Fri Nov 10, 2017 4:47 pm

I reinstalled Ubuntu MATE and wasn't able to redirect my smartcard reader. Then I realized i had to give the ttyUSB device permissions-
sudo chmod go+rw /dev/ttyUSB0
After that, it worked without problems.

Any chance this is related to the problem WTware has?


Readme:

The installation requires root access rights.

If medCompact terminal devices will be connected via RS232 to the system, the
administrator shall enable write access to the corresponding devices (e.g.
/dev/ttyS0 for COM1). Regarding COM1 this can be done using the command:

sudo chmod go+rw /dev/ttyS0

This command asks for the root password.


Supported distributions
This tool has been tested successfully on SuSE 10.3 and Ubuntu 8.4 ("hardy heron").

Re: WTware - using chip card reader terminal with Raspberry v3

by jktz90 » Tue Nov 07, 2017 7:49 pm

I set up an old Widows XP machine with RS232 port to monitor both the original (RS232) and RS232 to USB connection. I add them as attachment. I had to shorten the log due to personal informations.
Thanks.
Serial0 SUCCESS Rate: 115200
13 0.00001006 medView.exe IOCTL_SERIAL_CLR_RTS Serial0 SUCCESS
14 0.00001062 medView.exe IOCTL_SERIAL_CLR_DTR Serial0 SUCCESS
15 0.00001620 medView.exe IOCTL_SERIAL_SET_LINE_CONTROL Serial0 SUCCESS StopBits: 1 Parity: EVEN WordLength: 8
16 0.00000726 medView.exe IOCTL_SERIAL_SET_CHAR Serial0 SUCCESS EOF:0 ERR:0 BRK:0 EVT:0 XON:11 XOFF:13
17 0.00000922 medView.exe IOCTL_SERIAL_SET_HANDFLOW Serial0 SUCCESS Shake:0 Replace:0 XonLimit:2048 XoffLimit:512

Re: WTware - using chip card reader terminal with Raspberry v3

by akatik » Tue Nov 07, 2017 9:55 am

strace is a tool to log everyting in linux. But it's linux... In theory, simply run:

Code: Select all

 strace rdesktop options-to-rdesktop
and it should produce tons of log.

Can you attach device to old 32-bit windows? There is easy to use microsoft tool: https://docs.microsoft.com/en-us/sysint ... ds/portmon It sniffs all serial traffic. As I remember, it also sniffs virtual COM.

Re: WTware - using chip card reader terminal with Raspberry v3

by jktz90 » Mon Nov 06, 2017 1:26 pm

Hello,

I did the exact same operation on the server but the two devices are different. On the USB version I have to enter a pin on the device when the server application tries to communicate with the device. Thats not necessary on the R232 version. Other than that, I did the same read operation.

Is there anything I can do to give you a log out of Ubuntu mate/rdesktop? I always thought both use the same rdp protocol - so it's confusing to me why it works with Ubuntu and not with WTware.

Would it make any difference the specify the device path to /dev/ttyUSB0 ? Thats how I successfully redirect the r232 version using rdesktop.

Re: WTware - using chip card reader terminal with Raspberry v3

by akatik » Mon Nov 06, 2017 8:59 am

This log is completely different. Please, make me the same log with working reader. Perform the same task (test?).

Re: WTware - using chip card reader terminal with Raspberry v3

by jktz90 » Fri Nov 03, 2017 10:59 pm

Any news? I would really appreciate your help.

Re: WTware - using chip card reader terminal with Raspberry v3

by jktz90 » Sun Oct 29, 2017 7:08 pm

Hi,

I added the USB version debug log as an attachment.
I did not find any rdesktop command to debug the working R232 version using Ubuntu MATE.



USB version:
Image



R232 version:
Image

Re: WTware - using chip card reader terminal with Raspberry v3

by aka » Sat Oct 28, 2017 11:23 pm

jktz90 wrote:I have the smartcard reader in two different versions: one mobile version with direct USB connection (works totally fine with serial = comx(USB))
Show me same log with working reader.

Re: WTware - using chip card reader terminal with Raspberry v3

by jktz90 » Sat Oct 28, 2017 2:01 pm

Thanks for your reply.

Yes the standard configuration of the device is:
– 115200 Baud
– 8 databits
– even parity
– 1 stopbit

When I try to communicate with the smart card reader the reader turns on but crashes and requires a restart.

Some more info:
I have the smartcard reader in two different versions: one mobile version with direct USB connection (works totally fine with serial = comx(USB)) and one version with RS232 to USB converter (does work with Ubunutu MATE but not with WTware).
Any idea why it works with Ubuntu/rdesktop but not with WTware?

The manufacturer also released the whole source code for its device:
https://www.medline-online.com/fileadmi ... 080814.zip
* The communication between the DLL and the card terminal
* uses T=1 protocol on a serial line without handshake control:
* 9600...115200 baud, 8 databits, EVEN parity, 1 stopbit.

Top