Safenet Etoken Pro 72k Driver Download

Note: Microsoft will support SHA1 Code Signing Certificates until Jan 1, 2020. Microsoft recommends using SHA-256 certificate/digest algorithm/timestamp for all applications. Microsoft has not yet released a SHA1 deprecation policy for drivers. For more information, refer to the Windows Enforcement of Authenticode Code Signing and Timestamping page.

Before you can access the Document Signing Certificate on your token and use it to sign documents, you need to activate the token, download and install the SafeNet driver for your token, and obtain and change your token password.

DOWNLOAD 🔥 https://tiurll.com/2y7NPY 🔥

Having the SafeNet drivers on your computer lets you enable document signer authentication. Once enabled, SafeNet pops up before you sign a document and requires you to enter your password to verify that you are the actual signer.

I use eToken 64k pro every day. I have read last news about end of initscripts support and desided to migrate all my desktops and servers to systemd. I started migration from my netbook ASUS X101CH and found that after successful migration my etoken began to work very unstable.

I have get systemd openct init file from openct rpm for RedHat linux,

and /usr/lib/pcsc/drivers/openct-ifd.bundle/ folder frokm debian (ubuntu) openct deb package (but replaced openct-ifd.so with /usr/lib/openct-ifd.so already installed with AUR).

Everything works now except one thing - after removing and inserting back the USB key - I always need to restart openct and pcscd (in this order) to get it working.

Btw, I am using OpenSC PKCS15, not the proprietary Aladdin/Safenet eToken PKCS11 driver.

However, the token does not work with original opensc package, which is built with pcsc.

I have created opensc-openct AUR package.

I used to access my A3 token certificate without problems on ubuntu 20.04 using safenet authorization client 10.7 (.deb instalation file). I remember that I just had to install this debian package before in order to make it work.

last week I made a clean install of ubuntu 22.04 and, after installing that debian package of libssl 1.1, the driver seemed to work ok... but when I insert the token, nothing shows up on the driver. runnning SACTools on terminal doesn't show any output besides a lot of gtk errors (like it used to do before). when I insert the token the LED turns on then goes off after a few seconds. lsusb shows that my token is indeed connected. the command "pkcs11-tool --modul /usr/lib/libeTPkcs11.so --show-info -v" shows that no token is connected.

Recently purchased an Alladin(now owned by SafeNet) eToken which isn't being recognized by PGP WDE v10.2. However, Windows Vista does recognize the Alladin eToken, but I think I need to install the eToken specific usb drivers for my token dongle to be recognized by PGP. The site where I purchased the eToken didn't mention anything about additional software drivers. Help...

I believe this was over a year ago when I found some reference suggesting the use of this, and I just don't recall where that came from. I could also not find the file at the site; as I recall, I searched the Internet and found it available from where ever that was. I just did a Google search and found the following. It looks familiar, but I'm not able to vouch for it: -rd.ru/support/faq/etoken/category3/faq1000512/

I have administrator privileges, and I've tried creating various email/passwords combos on the eToken. Perhaps it's a hardware driver incompatibility, or the same user can't have more than one boot verification type. When I tried to delete the original single password verification key, pgp responded with a message stating that the original verification key can't be deleted. I could create another user account and try it from that process.

The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.

My EV code signing cert expired about a week ago. It used a Digicert hardware token (USB SafeNet device) that I had used for many years without issue. In a Visual Studio driver project you could select "Production Sign" and then in the Production Certificate field you could pick "Select from Store..." and it would show my cert as an option.

Next I tried to copy the cert subject and thumbprint data from the test certificate field to the production certificate field and changed the type to Production Sign. I figured even if it wouldn't let me select it, if I described it then it should be able to find it. (Signtool.exe at the command line was able to find it with just the thumbprint). But now VS complains that it needs a cross-signing cert. That's bogus, those stopped being used for driver signing a couple years ago.

Thanks for the reply, Tim. I know the attestation (or HLK) signing is a requirement for running on end user machines, but you don't sign the .sys with your cert as well? I've always signed the .sys, generated the .cat, then signed the .cat, then created the .cab, then signed the .cab, then ran it through portal. This results in getting a driver back from MSFT which has both my cert and their cert on the .sys.

Very interesting. I just confirmed that it works as you said, the cab contents don't need any signatures. This contradicts my understanding of what attestation signing was all about in the first place. I always interpreted the dual signatures to effectively say "the first sig says I wrote this and the second sig says Microsoft confirms it." It seems odd for a 3rd party to be able to ship out a driver which could have no identifying publisher info other than a Microsoft signature. I would assert this makes it look like Microsoft is the publisher.

For the record: We did not sing any driver files, only the .cab file. The driver files included were the .inf, .sys and .pdb files. In the dashboard it is still scanning the .cab file after 12 hours. Tried it again, also still scanning.

You can't timestamp in VS when building a release driver because you can't select the new EV certificate from the production store any more (that was the initial post here). Hence you can use for a release build in VS only Test-Sign with the new EV certificate where timestamping is not supported by VS.

After about 36 hours, both attempts of our unsigned drivers have finally been signed by MS. There might have been a glitch in their system (or it might be that our new certificate had never been used before, who knows).

It arrived yesterday. GlobalSign gave me a "blank" USB security token device - a SafeNet eToken 5100. Unfortunately the user-experience is terrible. It requires its own special driver instead of using Microsoft's own standard USB security token driver or emulating a smart-card device. The UI is horribly designed and covered in logos. It's also impossible to get drivers directly from SafeNet / Gemalto, they're distributed by the CA (in this case, GlobalSign). I had issues with the driver's background service refusing to start and my Windows logon-screen now has 6 extra buttons for duplicate token devices even when the USB token isn't plugged in.

I would like to extract my information from the token and move it to a better-implemented device, such as another USB token that doesn't require special drivers, similar to the experience I had with my old employer's smartcard-based PKI).

Well, I need to use the Etoken to digitally sign invoices in my country for my company. I have installed Safenet 8.1 software, and I am currently running Ubuntu 12.04. The PKI client (from Safenet) can't find the etoken.

I may be wrong, however it's worthy a shot. In my understanding it's just the opposite. I work here with ikey2032 and etoken pro 72k. You only disable libhal and enable libusb to work with ikey. I do use ubuntu 12.04 too, 32bit and 64bit. I just do a clean instalation via dpkg, resolve all dependencies (pcsc and libhal) and it works fine for etoken. I could never make it work with ikey.

I Have the same problem and i was solved that.

I was remove every packages was i used to fing my eToken (ex p11-kit, pcscd,opensc openct etc) after that i was install SafNet pki driver for eToken and required packages (pcscd).

In file

/etc/gnutls/pkcs11.conf

i was add line

as far as I understand, the OpenSC driver is not shown in the combobox of GlobalSign. I would have thought, that OpenSC should be shown anyway, no matter if a device is already plugged in. So it looks to me as if this connection between the website and the CSP does not work yet, no matter which OpenSC-compatible device you would plug in. 006ab0faaa