usb4java | USB library for Java based on libusb | Change Data Capture library

openssl pkeyutl -sign with an RSA private key and -pkeyopt digest:$alg does steps 2-5 of EMSA-PKCS1-v1_5 plus the private modexp (i.e. 8.2.1 step 2 using RSASP1 from 5.2.1); without that -pkeyopt it does not do step 2, which encodes the hash value in a simple ASN.1 structure.

The Java Signature algorithms that include a hash like SHA1withRSA do all steps of EMSA-PKCS1-v1_5 plus modexp, while the scheme NONEwithRSA does only steps 3-5 plus modexp, and neither of these matches what you want. If you can't supply the data to let Signature do the hashing, you'll need to do step 2 yourself and then NONEwithRSA. Although ASN.1 encoding in general can be complicated (and decoding even more so), this case can be done simply by concatenating a prefix determined entirely by the hash algorithm to the hash value; see note 1 on page 47.

Meta: there have been lots of Qs about the differences in RSA v1_5 signatures between openssl rsautl, pkeyutl with and without -pkeyopt digest, or dgst -sign and other systems like Java, all to do with the issue of including or not including the ASN.1 encoding step (and many of them older than rfc8017!) but I can't find any that is a good dupe for this Q.

You can try to configure the Gradle build environment, gradle.properties in project root directory.

There are basically two ways around your issue:

1. don't use the PC/SC interface used by java.smartcardio but use native, proprietary libraries from the card reader manufacturer, for instance using a wrapper (JNI based, but there are better / higher level alternatives out there);

2. keep using APDU's, but use CLA byte set to FF hex, opening a connection to the reader. FF is reserved, but it is generally reserved for this kind of card reader access, e.g. to access memory cards without ISO/IEC 7816-4 layer that are supported by the reader manufacturer.

3. out of two (for completeness only): many card readers have been created using a USB to serial interface chip, which means that you can directly connect to the (virtual) serial interface; needless to say, you will have to know what commands to send and program everything yourself, if this interface is present at all (Omnikey 3121 is relatively new, so I would be surprised).

Both options rely on card reader specific functions, so you will have find the information for the reader to see what is possible. To my knowledge there is no way to request what functionality is provided. Don't expect too much from standardization for this kind of functionality.

Did you check your card reader specific documentation?

Most probably you are receiving a C-String as a response. So the String is terminated by a NUL ('\0') character. Try getting the value using:

Included the file lib/libusb-1.0-windows-x86_64.jar in the classpath.

It's solved, i used Java Serial Connection instead for it, and it works just fine!

sometimes it is -9 when I disconnect

Should always be -9, as a disconnect clears the USB handle inside the kernel.

For Sending, I got a response of 0 but in receiving, I got -7.

That is the regular ERROR_TIMEOUT, which may or may not be an error at all.

The basic meaning is just: The USB device did not send any data on the endpoint during the timeout period.

In the (example) case of an USB2UART chip, the ERROR_TIMEOUT would just mean that there were no bytes received on the UART RX line.

Fun fact: LibUsb.bulkTransfer() can receive zero bytes from a USB device, and would not return an error code in this case. USB bulk endpoints actually allow that (and it is different from the "no data at all" case).

The issue seems to be that I did not trigger LibUsb.freeDeviceList(devs, unref_devices); , I figured it out when I disconnected the USB device manually and successfully connected it when it is freshly connected.

For reading files (part 2),

1 - First read the interface and endpoint details which you are already doing