Quantcast
Channel: Gemalto Sentinel Customer Discussions
Viewing all 1619 articles
Browse latest View live

Re : Stop Error (BSOD) when install Sentinel Run-time Environment version 7.51 on Asus Q500A with Intel RAID drivers 11.5.2.1001

$
0
0
Dear Customer,

Hope you are doing well!
 
To understand the issue better and troubleshoot further, please e-mail us at support@safenet-inc.com.
 
Regards,
Anubhav

HASP 4 - Run Time API

$
0
0
Hi,
more than 10 year ago,
I developed a protection for some applications of a my customer that use HASP4 Keys, using c++ and the CHasp class, linking my code with some modules included with the hasp software kit.
Now I need to develop the same protection to .Net applications.
My question is:

Are there API to protect an application using HASP4 key in the .Net Framework environment?

Thanks

Domenico

Re : HASP 4 - Run Time API

$
0
0
Hello Domenico,

Hope you are keeping well.

Please be informed that there are APIs available for .NET environment on HASP4.

However, it could only be shared via support request.

Kindly forward your query to our support portal support@safenet-inc.com for assistance in this regard.

with regards,
Parth Kaushik

Re : Haspdinst.exe BSOD for 7.50 and 7.51

$
0
0
Hello,

I just wanted to confirm whether the fix in 7.52 for "SM-504
When using RTE 7.51, a Stop error (BSoD) would occur when the protected application attempted to retrieve the serial number of the disk drive that uses Intel RAID drivers." 

.. is in fact fixing this issue? I just didn't know the ticket number, or that it was specific to retrieving the drive's serial number, but it sounds pretty likely that this is the same issue.

Thanks!

Re : Haspdinst.exe BSOD for 7.50 and 7.51

$
0
0
Hello Tim,

Thanks for getting back to us.

Yes, the fix has been provided in RTE 7.52 release for this issue.

with regards,
Parth Kaushik

haspdinst.exe 7.52 signing of vendor library for Windows 10 Enterprise Anniversary Update

$
0
0
Hi,

The release notes of haspdinst.exe RTE 7.52 contains three workarounds for handling unsigned vendor libraries in DeviceGuard on Windows 10 Enterprise systems. The first two workarounds involve the end user performing specific tasks to get vlib working. The third workaround is for the software vendor to provide the end user with an out-of-the-box experience. Therefore my focus is on this third workaround because it makes life easy for the end user, we all want that.

I contacted Gemalto support and they provided me with instructions on how to do this. We need to sign the vlib and then manually package the vlib in haspdinst.exe. What I would like to discuss is the following:

I did not create this Vendor Library (VLIB). Gemalto created the vendor library. If I would receive a file from company A that is signed by Company B I would not trust the file. A clear indication that something is not right. So in my opinion Gemalto should sign the vlib before they distribute them. If they would have signed the file then it would automatically end up in the custom haspdinst.exe generated by EMS and the end user would have the out-of-the-box experience that I think we all want. Am I missing something here? Why do we have to sign a file we did not create?

Regards,
Arno


Sentinel LDK on high DPI display

$
0
0
I have just installed Sentinel LDK 7.5 for Windows and find that some sections of the tools (dialogs, etc) are unusable on my 4K display (3840 x 216) with scaling set to 200%.

I see that Qt 4.8 is being used for the vendor tools, but high DPI support in Qt was first introduced in version 5.6.

With the number of 4K displays in use set to grow, it is time the LDK was updated to support such displays.

Regards.
Brett


Re : Sentinel LDK on high DPI display

$
0
0
Hi Brett,

Hope you are keeping well.

We need to investigate on this request. For that, please send one email to "Support@safenet-inc.com" with your query.

Regards,
Anubhav

Re : haspdinst.exe 7.52 signing of vendor library for Windows 10 Enterprise Anniversary Update

$
0
0
Hello Arno,

Thank you for raising the concern.

We have found similar requests from other customers on this issue and which are under consideration.

Hence, we would request you to kindly forward this concern to our support team at support@safenet-inc.com so that we may keep you inform about the resolution.  

with regards,

Parth Kaushik

Convert from 32 bit to 64 bit application

$
0
0

Apologies if this is not the correct forum.

I have used hasp dongles for many years now and was hoping to migrate my application from a 32 to 64 bit application.  Unfortunately having made the change within a Windows Visual Studio 2010 project, I now have several "unresolved external symbols" as a result i.e. hasp_login.

I looked for a suitable download but unfortunately cannot locate 64 bit libraries (.lib/.dll).  If someone could direct me to where I may download these, it would be much appreciated.

My current implementation utilises the following:

include "hasp_hl.h",

Lib: libhasp_windows.lib

Runtime: hasp_windows.dll (Aladdin HASP HL Windows Dll Version 1.12)

thanks

Re : Convert from 32 bit to 64 bit application

$
0
0

Hello Lee,

 

Thanks for sharing the concern.

 

However, unfortunately the HASP version you are using has been deprecated and would not be helpful in 64-bit environment.


Hence, kindly be advised to upgrade the latest Sentinel LDK SDK and for that forward your request to our support team at support@safenet-inc.com.


You may require to keep the sales rep informed about that as well.


Have a nice day ahead.

 

With regards,


Parth Kaushik

SRM Legacy Api access + Hasp SRM network key = LM Server death

$
0
0
Hello

I use an Apps in 32 bits with Hasp 4 API (no Envelope)
The same Apps in 64 bits use SLDK API with Envelope
It work with 2 Hasp SRM Network key (Hasp mode with Hasp4 part) on 2 servers (lmsetup Hasp 4 licenses server + NetHasp.ini on computers to disable broadcast et change reponse time)

The 32 and 64 bits Apps use the same acces to the Network Key

If I launch 32 bits Apps on ~100 computers : it works well
If I launch 64 bits Apps on same ~100 computers : all apps crash after few seconds : the 2 Hasp LM can't negociate all the query off ~100 apps

I think the 64 bits Hasp 4 emulation generate more traffic with LM Setup than the 32 bits Hasp 4 API.

Anyone can confirm this ?
Is there any solution ? 

I have already change the nethasp.ini to :
 - disable broadcast
 - change the responds timeout to :   
 NH_SESSION = 6
 NH_SEND_RCV = 3
 
I have also reduce the number off call off Hasp API but It doesn't work
Gemalto support can't help me because lmsetup is not supported anymore.
 
Please Help
Regards
David

Re : SRM Legacy Api access + Hasp SRM network key = LM Server death

$
0
0
Hi David,

Hope you are doing good.

For the above mentioned issue, kindly confirm the following:

1. Sentinel LDK version used.
2. Run time version used at your end.
3. As we have understood the 32 bit apps make use of Program No. and the 64 bit apps use Feature Id's. Please confirm.
4. If yes, please explain what do you mean by this "I think the 64 bits Hasp 4 emulation generate more traffic with LM Setup than the 32 bits Hasp 4 API".
5. As you said that
"If I launch 32 bits Apps on ~100 computers : it works well
If I launch 64 bits Apps on same ~100 computers : all apps crash after few seconds : the 2 Hasp LM can't negotiate all the query off ~100 apps" does this mean that we stop 32 bits apps first and then execute 64 bit app or the 32 bit apps are still running while executing the 64 bit apps.

Thanks,
Heena

Re : Linux hasp_update with my vendor key

$
0
0
Hi Ashish,

To resurrect this old thread: we're recently started to implement a more complex licensing mechanism utilizing key memory.  We plan to not just use the envelope for the feature-based licensing (which we have been using for many years now) but also we'll use sub-feature/parameters utilizing key memory.  For that we are using the C APIs hasp_login, hasp_read and hasp_logout in our protected application.  To successfully log into the key, we need to pass the vendor code to hasp_login (so, the vendor code must be present in our resulting app binary).  But after logging in, we are also able to call hasp_write, modifying the key memory.  This contradicts your statement that passing around binaries with the vendor code, especially in non-enveloped form, is not a protection risk, as a potential attacker would use the vendor code for hasp_login and hasp_write, overwriting the key memory.

Is there any way that would allow us to prevent modification of the key memory?  Perhaps leaving the authentication to envelope, and calling hasp_login+hasp_read to only read the key memory without the vendor code?

Thanks for your comments.

Re : SRM Legacy Api access + Hasp SRM network key = LM Server death

$
0
0
Hello Heena

Sentinel LDK : Latest 7.5
Runtime on server : Hasp 7.41 + LMSetup 8.32.5.40 (latest)
The 32 bits Apps use hasp() commande with Prog number
The 64 bits Apps use LDK specific API hasp_login() + another hasp_login() with Program Nbr and HASP_PROGNUM_OPT_CLASSIC to access on Hasp 4 memory part

Customers can choose between 32 or 64 bits versions, I need to take a license on Hasp 4 LM on 64 bits version.

I launch 32 bits Apps (~on 100 computers) : it work
I stop 32 bits Apps and launch 64 bits Apps (~on 100 computers) : After a few time, I have errors on hasp_read() with handle open with HASP_PROGNUM_OPT_CLASSIC
Error are : 0x07 (hasp not found), 0x1F : Feature not found
If i launch an 32 bits apps when I get errors, hasp(110) return error like "15 : No Hasp LM Found" or "137 : no Space H4 Net log)

I think the 64 bits hasp 4 emulation on network key push down the LM servers so LMs servers can response under the 3 seconds of NH_SEND_RCV = 3

Regards
David


Sentinel Driver v5.7.4 on macOS El Capitan (10.11) and Sierra (10.12)

$
0
0
I've installed, uninstalled, installed the Sentinel Drivers v5.7.4 on my Mac (El Capitan 10.11) and could not get it working.  Well, it could possibly be working but I don't know how to test it.  I've just been looking for entries in the /dev directory to show up.  Maybe that's wrong?

The driver is loaded and running.  "kextstat | grep -i sent" gives me a hit.

I do get messages in the console saying the service runs for 0 seconds and tries to respawn.

"Jan 26 21:21:40 Brendan-MBP-510 com.apple.xpc.launchd[1] (com.safenet.sentinel.kext): Service only ran for 0 seconds. Pushing respawn out by 10 seconds."

Is the driver working or not?

In desperation I upgraded to macOS Sierra (10.12) and I get the same result/symptoms.

How can I test if the Sentinel Drivers detect my USB Device and can communicate with it OK.

v5.7.4 doesn't explicitly state support for Sierra (as Sierra was released after v5.7.4).  Is there an updated version or beta version I can try?

Thanks, Brendan.

Data Location

$
0
0
Hello All,

I've a question about data location and the cloud. Do to data protection requirements we need to specify what location our customers' data is stored. For example we'd need our EU customers data at a european data center and our US customers at a US data center.

Will Sentinel Cloud allow us do to this?

Regards,
Phil Smith

Re : Data Location

$
0
0
Hi Phil,

Hope you are keeping well.

For better understanding on your concern, I would request you to share detailed query to "support@gemalto.com".

Regards,
Anubhav

Re : SRM Legacy Api access + Hasp SRM network key = LM Server death

$
0
0
Hi David,

This issue would require further investigation over the application , so it is requested to send an Email to support@safenet-inc.com with the details of the issue.

We would be happy to assist you.

Thanks,
Heena

Re : SRM Legacy Api access + Hasp SRM network key = LM Server death

$
0
0
Hi Heena

First solution :
I don't know if I will contact support because :
 - 2 issues with the same answers : Sorry, LM Setup is obsolete and will not be update anymore !
 - 1 issues with Envelope 6.4 : no solution except reduce protection quality option to 0
 - 1 issues with Envelope 7.4 (regression vs 6.4) : answer : We need to develope new thing so we need to planify this (Hey gays, this is a regression) !

Second solution is to change protection sheme (but with more than 100 000 keys solds, it's difficult to change for a new solution or for migrating all customers to the last version)

The last solution : bring me the source code of LM Setup (with confidentiality contract), I will find the problem !

I have investigate some network UDP packet on the server with wireshark :
To obtain simply the Hasp ID :
 - with Hasp 4 API : 2 packet (for send and reveive)
 - with Hasp SRM API : 6 packet 
LM Setup can't process more than 40 packets per second (to have an answer within 3 seconds)

So !

Viewing all 1619 articles
Browse latest View live