Re : Different host_fingerprint on the same system.

April 15, 2020, 6:29 am

≫ Next: Re : Different host_fingerprint on the same system.

≪ Previous: Different host_fingerprint on the same system.

Hi Vasile,

Thanks for raising the concern.

How was it determined that the fingerprint recieved were different ?
If you have decoded the fingerprint C2Vs then please share it with us as well to check.

Looking forward to hearing from you.

Best regards,

Parth

↧

Re : Different host_fingerprint on the same system.

April 15, 2020, 8:43 am

≫ Next: Re : Different host_fingerprint on the same system.

≪ Previous: Re : Different host_fingerprint on the same system.

Test 1.
I used the Hasp.getInfo method (KEY_SCOPE, KEY_FORMAT, VENDOR_CODE) from the "Licensing API" with the following parameters:
KEY_SCOPE: <? Xml version = "1.0" encoding = "UTF-8"?> <haspscope> <license_manager hostname = "localhost" /> </haspscope>
KEY_FORMAT: <haspformat format = "host_fingerprint" />
VENDOR_CODE: Specific.
Each time I restarted the system and called this method, the answer was different.

Test 2.
I used the web service provided by EMS. This resource is https://docs.sentinel.gemalto.com/ldk/LDKdocs/WebHelpWS/getFingerprintPC.htm. I used 2 activations done on the same system. The values returned for host_fingerprint differed and only the value for secure_storage_uid differed from the criteria list.

Why is secure_storage_uid different if I use the same system each time?

Thanks again.

↧

Re : Different host_fingerprint on the same system.

April 20, 2020, 11:23 pm

≫ Next: Aksfridge.sys causing bluescreen on Windows10 20H1 after KB4556803 (may update)

≪ Previous: Re : Different host_fingerprint on the same system.

Hi Vasile,

Thanks for the response.

However, the behaviour appearing is not as expected. Thus, we may need to get the same tested for this platform.

Could you please share it with our support staff using our customer support portal at https://supportportal.gemalto.com/csm ?

It would be helpful to analyze the behvaiour in detail.

Best Regards,

Parth

↧

Aksfridge.sys causing bluescreen on Windows10 20H1 after KB4556803 (may update)

May 15, 2020, 6:52 am

≫ Next: Re : Aksfridge.sys causing bluescreen on Windows10 20H1 after KB4556803 (may update)

≪ Previous: Re : Different host_fingerprint on the same system.

Hi, i just wanted to inform you that on latest Windows 19041, when KB4556803 get downloaded it causes system to crash. I didn't understand why, it happend also after a clean install. Then i've seen it was aksfridge.sys. I don't know why the file was on my pc. I suppose installed by ZEISS Zen 3.0 (lite), i don't even use a dongle with it but the driver is there anyway. I had to revert the install of the update and then Changing HKLM\System\CurrentControlSet\Services\aksfridge start value to 4 the problem does not occur anymore.

The Aksfridge.sys version i have is 1.78.12384.

↧

Re : Aksfridge.sys causing bluescreen on Windows10 20H1 after KB4556803 (may update)

May 18, 2020, 8:25 am

≫ Next: Re : Aksfridge.sys causing bluescreen on Windows10 20H1 after KB4556803 (may update)

≪ Previous: Aksfridge.sys causing bluescreen on Windows10 20H1 after KB4556803 (may update)

Dear User,

Thanks for raising the concern.

Could you please check if the issue reproduces with our latest Sentinel runtime as well ?

Please download it from our knowledge-base at KB0018320.

If the problem is still observed then please be suggested to raise it with out technical support using our support portal.

Kindly share the crash dump for Windows OS to investigate.

Thanks & regards,

Parth

↧

Re : Aksfridge.sys causing bluescreen on Windows10 20H1 after KB4556803 (may update)

May 18, 2020, 8:49 am

≫ Next: Re : Aksfridge.sys causing bluescreen on Windows10 20H1 after KB4556803 (may update)

≪ Previous: Re : Aksfridge.sys causing bluescreen on Windows10 20H1 after KB4556803 (may update)

I downloaded the version you provided with -install

Driver got installed and start value in register reverted to 2.

System works perfectly fine.

ZEISS should add a newer version of the driver bundled with their software. Or microsoft? or somebody?

otherwise i think we'll see more of those problem in the next weeks with 20h1 release

i'm adding memory.dmp as soon it's done uploading

↧

Re : Aksfridge.sys causing bluescreen on Windows10 20H1 after KB4556803 (may update)

May 18, 2020, 9:01 am

≫ Next: Re : Aksfridge.sys causing bluescreen on Windows10 20H1 after KB4556803 (may update)

≪ Previous: Re : Aksfridge.sys causing bluescreen on Windows10 20H1 after KB4556803 (may update)

Here MEMORY.DMP https://drive.google.com/file/d/1FT8yHjQU_BNsWqgO9fk1jmdfQGYXyKPp/view?usp=sharing

and my debug output

-------------------------------------------------------------------------------------------------------------------------------------------

Microsoft (R) Windows Debugger Version 10.0.19041.1 AMD64

Loading Dump File [C:\Users\staim\Desktop\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

************* Path validation summary **************

Response Time (ms) Location

Deferred srv*c:\cache*https://msdl.microsoft.com/download/symbols

Symbol search path is: srv*c:\cache*https://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 10 Kernel Version 19041 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff806`05600000 PsLoadedModuleList = 0xfffff806`0622a250

Debug session time: Wed May 13 20:00:51.572 2020 (UTC + 2:00)

System Uptime: 0 days 0:00:11.284

Loading Kernel Symbols

...............................................................

....Page 103f3a not present in the dump file. Type ".hh dbgerr004" for details

............................................................

.....................................

Loading User Symbols

Loading unloaded module list

......

For analysis of this file, run !analyze -v

7: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)

Invalid system memory was referenced. This cannot be protected by try-except.

Typically the address is just plain bad or it is pointing at freed memory.

Arguments:

Arg1: fffff806ee1a6800, memory referenced.

Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.

Arg3: fffff806059bc451, If non-zero, the instruction address which referenced the bad memory

address.

Arg4: 0000000000000002, (reserved)

Debugging Details:

------------------

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec

Value: 4

Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on DESKTOP-4MKPM3M

Key : Analysis.DebugData

Value: CreateObject

Key : Analysis.DebugModel

Value: CreateObject

Key : Analysis.Elapsed.Sec

Value: 5

Key : Analysis.Memory.CommitPeak.Mb

Value: 69

Key : Analysis.System

Value: CreateObject

BUGCHECK_CODE: 50

BUGCHECK_P1: fffff806ee1a6800

BUGCHECK_P2: 0

BUGCHECK_P3: fffff806059bc451

BUGCHECK_P4: 2

READ_ADDRESS: fffff806ee1a6800

MM_INTERNAL_CODE: 2

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

PROCESS_NAME: System

TRAP_FRAME: ffffe406b7a92480 -- (.trap 0xffffe406b7a92480)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=fffff806ee1a6800 rbx=0000000000000000 rcx=000007f911e59800

rdx=00000000bd48675b rsi=0000000000000000 rdi=0000000000000000

rip=fffff806059bc451 rsp=ffffe406b7a92618 rbp=ffffe406b7a92650

r8=7efefefefefefeff r9=0000000000000000 r10=000000009e3779b9

r11=8101010101010100 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl zr na po nc

nt!strlen+0x31:

fffff806`059bc451 488b10 mov rdx,qword ptr [rax] ds:fffff806`ee1a6800=????????????????

Resetting default scope

STACK_TEXT:

ffffe406`b7a921d8 fffff806`05a35c1d : 00000000`00000050 fffff806`ee1a6800 00000000`00000000 ffffe406`b7a92480 : nt!KeBugCheckEx

ffffe406`b7a921e0 fffff806`05812ce0 : 00000000`00000000 00000000`00000000 ffffe406`b7a92500 00000000`00000000 : nt!MiSystemFault+0x1ad4ed

ffffe406`b7a922e0 fffff806`059ebb1e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x400

ffffe406`b7a92480 fffff806`059bc451 : fffff806`0d15b558 00000014`db520f40 00000000`00000000 ffffcf7c`0302bfc0 : nt!KiPageFault+0x35e

ffffe406`b7a92618 fffff806`0d15b558 : 00000014`db520f40 00000000`00000000 ffffcf7c`0302bfc0 ffffcf67`be018158 : nt!strlen+0x31

ffffe406`b7a92620 fffff806`0d10ff7e : 00000000`00000000 4e932dcf`4e932dcf 00000000`00000001 ffffe406`b7a92898 : aksfridge+0x5b558

ffffe406`b7a926a0 fffff806`0d1100c3 : ffffffff`8000233c ffffd30b`00000000 00000000`06b88057 fffff806`05d4315c : aksfridge+0xff7e

ffffe406`b7a926e0 fffff806`0d11f055 : ffffd30b`0b2a3460 00000000`000000df fffff806`0d17b000 00000000`00000002 : aksfridge+0x100c3

ffffe406`b7a92740 fffff806`05d5f164 : ffff8186`b19ad000 00000000`00000000 ffff8186`00000002 ffffe406`b7a92928 : aksfridge+0x1f055

ffffe406`b7a92900 fffff806`05d2a6c9 : 00000000`00000014 00000000`00000000 00000000`00000000 00000000`00001000 : nt!PnpCallDriverEntry+0x4c

ffffe406`b7a92960 fffff806`05d6fd67 : 00000000`00000000 00000000`00000000 fffff806`06324440 ffff8186`a9cc0b00 : nt!IopLoadDriver+0x4e5

ffffe406`b7a92b30 fffff806`05833f25 : ffff8186`00000000 ffffffff`8000233c ffff8186`a9ccd140 ffff8186`00000000 : nt!IopLoadUnloadDriver+0x57

ffffe406`b7a92b70 fffff806`05946715 : ffff8186`a9ccd140 00000000`00000080 ffff8186`a9c93040 8993c9a6`c6d01f33 : nt!ExpWorkerThread+0x105

ffffe406`b7a92c10 fffff806`059e5078 : fffff806`00566180 ffff8186`a9ccd140 fffff806`059466c0 91cd2f70`4fb6536d : nt!PspSystemThreadStartup+0x55

ffffe406`b7a92c60 00000000`00000000 : ffffe406`b7a93000 ffffe406`b7a8d000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME: aksfridge+5b558

MODULE_NAME: aksfridge

IMAGE_NAME: aksfridge.sys

IMAGE_VERSION: 1.77.3441.0

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 5b558

FAILURE_BUCKET_ID: AV_R_INVALID_aksfridge!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7970908d-bb77-adf6-e29e-9053eb9e30e3}

Followup: MachineOwner

---------

↧

Re : Aksfridge.sys causing bluescreen on Windows10 20H1 after KB4556803 (may update)

May 19, 2020, 7:12 am

≫ Next: HASP SL Cloned Storage immediatelly after driver installation

≪ Previous: Re : Aksfridge.sys causing bluescreen on Windows10 20H1 after KB4556803 (may update)

Dear User,

We are glad to know if the machine is working fine with the latest drivers. It seems that the earlier driver was facing some conflict with the OS update. It may not be officially tested for the same.

Hence, we suggest you continue using the latest drivers for now. You may like to inform the application vendor to re-bundle new drivers with setup.

If needed, the application vendor can reach our support team for more details or help on your behalf.

Best regards,

Parth Kaushik

↧

HASP SL Cloned Storage immediatelly after driver installation

June 29, 2020, 10:38 am

≫ Next: Re : HASP SL Cloned Storage immediatelly after driver installation

≪ Previous: Re : Aksfridge.sys causing bluescreen on Windows10 20H1 after KB4556803 (may update)

We've a customer who is running 2 virtual machines (Windows Server), probably originating from the same image. We received a fingerprint c2v from each, and they are different. We successfully generated HASP SL Admin Mode keys for both and succeeded installing the one, but for the other we cannot install the V2C because RUS tells us "Update failed: Cloned Sentinel SL secure storage detected".

The other machine's key is visible through localhost:1947.

We tried removing the driver, including "haspdinst -fr -kp -purge" and deleting the contents of "C:\Program Files (x86)\Common Files\Aladding Shared" (where it kept hasplm.ini), but to no avail.

Repeated installs/uninstalls of the runtime does not seem to have any impact (notably the fingerprint remains the same).

So it seems that there is no way for us to install the HASP SL key onto the 2nd server.

Any advice would be appreciated!

↧

Re : HASP SL Cloned Storage immediatelly after driver installation

July 1, 2020, 3:13 am

≫ Next: Sentinel HL - fritzbox vpn

≪ Previous: HASP SL Cloned Storage immediatelly after driver installation

Hi Filip,

Thanks for raising the concern.

However, the raised problem might require a detailed investigation as it is related to 'SL secure storage'.

Please be advised to contact our support team by reporting the issue on Thales Support Portal .

Kindly share the mentioned files and details in your discussion.

regards,

Parth

↧

Sentinel HL - fritzbox vpn

August 2, 2020, 7:46 am

≫ Next: Re : Sentinel HL - fritzbox vpn

≪ Previous: Re : HASP SL Cloned Storage immediatelly after driver installation

Beste leden,

Ik heb een sentinel HL-dongle in mijn Fritzbox.

Van daaruit een VPN-beurt, maar ik kan de dongle alleen lokaal zien.

Is het mogelijk dat ik de dongle in mijn server op afstand kan bereiken?

↧

Re : Sentinel HL - fritzbox vpn

August 5, 2020, 1:43 pm

≫ Next: Difference between RDP admin session and RDP Gateway admin session

≪ Previous: Sentinel HL - fritzbox vpn

Hallo Kevin,

applologieën, ik heb hier geen native speakers. Dit forum is alleen in het Engels beschikbaar.

Try to access the remote computer (where the Sentinel HL HASP key is connected) via Remote Desktop while connected to the VPN.

Then check via a web browser, if you can access "http://localhost:1947/_int_/features.html" then look at the column "Access" . Verify if each "feature" row have an access "Local, Display".

In such case, the protected application should be allowed to consume the required license "feature" via "Remote Desktop" access.

Else, contact the software Editor to get the remote access added to your license.

Best Regards,
Olivier

↧

Difference between RDP admin session and RDP Gateway admin session

September 1, 2020, 5:04 am

≫ Next: Detect feature expired in remote desktop

≪ Previous: Re : Sentinel HL - fritzbox vpn

Hi,

We have a Sentinel HAPS license manager for our product Priva Engineering.

The license runs on a Hyper-V servers (dongle connected with Anywhere USB). The license works fine.

I can connect with this server through a remote desktop gateway (provided by our IT supplier) and i can connect through local network (both RDP admin sessions).

This should be the same, but when the license manager is started via the console session on RDP gateway, and I connect via local network (also admin session) the license manager looses the connection with the dongle(?) or license manager.

Does anyone recognizes this issue?

↧

Detect feature expired in remote desktop

January 12, 2021, 12:50 pm

≫ Next: Re : Detect feature expired in remote desktop

≪ Previous: Difference between RDP admin session and RDP Gateway admin session

Hi, our software is autorized to run on a machine connected via remote desktop.

We have a feature with an expiration date, but if we test that feature, we obtain HASP_TS_DETECTED status instead of HASP_FEATURE_EXPIRED. I copy the code that we use.

How can we solve this problem?

ChaspFeature feature = ChaspFeature::fromFeature(featureid);
Chasp hasp(feature);
haspStatus status = hasp.login(VENDOR_CODE);
bool succeeded = HASP_SUCCEEDED(status);
bool expired = status == HASP_FEATURE_EXPIRED; --> this is false because status is HASP_TS_DETECTED

Thanks Matteo

↧

Re : Detect feature expired in remote desktop

January 13, 2021, 6:20 am

≫ Next: Re : Detect feature expired in remote desktop

≪ Previous: Detect feature expired in remote desktop

Hi Matteo,

Thanks for raising the concern.

The message HASP_TS_DETECTED appears if a non-RDP enabled feature is accessed through sentinel API over RDP. Please check the license feature under ACC page at http://localhost:1947/_int_/features.htm.

f the particular feature doesn't have "display" tag under the access row then the same is not an RDP enabled license. It will require to modify such license to 'RDP enabled' though product modification and license key update process.

Looking forward to hearing from you.

Thanks & regards,

Parth Kaushik

↧

Re : Detect feature expired in remote desktop

January 13, 2021, 7:25 am

≫ Next: Re : Detect feature expired in remote desktop

≪ Previous: Re : Detect feature expired in remote desktop

Perfect, thank you very much!

↧

Re : Detect feature expired in remote desktop

January 14, 2021, 1:25 am

≫ Next: Admin API and password

≪ Previous: Re : Detect feature expired in remote desktop

Hi Matteo,

Thanks for the response.

We are glad to know if the discussion was helpful.

Best regards,

Parth

↧

Admin API and password

June 2, 2021, 12:27 pm

≫ Next: Getting HASP_OLD_LM error after successfully encrypted files

≪ Previous: Re : Detect feature expired in remote desktop

Hello

I can't find how to use Admin API with ACC password protected.

I have a server with a Sentinel Licence Manager (8.21) on a Debian with a software key.

This server is exposed on Internet for some stuff.

With this ACC, I must use HTTPS, so I must have a password protection.

So all work fine except Admin API

I use this sample code for exemple :

status = sntl_admin_context_new_scope( &context, scopeNew);

status = sntl_admin_get( context, scopeGet, format, &info);

- scopeNew with host, port, password and certificat

- scopeGet with just <haspscope/>

It work fine only if I configure Password protection to "Configuration Pages" (because password is just ignored)

It I configure Password protection to "All ACC Pages", sntl_admin_get return 6008 error : SNTL_ADMIN_PASSWORD_REQUIRED, but I have already fill the passord in scopeNew

Same thing with sntl_admin_context_new()

I don't know how and where to give password ?

Any help

↧

Getting HASP_OLD_LM error after successfully encrypted files

June 2, 2021, 11:33 pm

≫ Next: Re : Getting HASP_OLD_LM error after successfully encrypted files

≪ Previous: Admin API and password

Hi,

I realised this is a common problem that Sentinel user came across. However, most posts are too old and the most of the links are dead.

The error message I got is:

Sentinel LDK Protection System: Sentinel License Manager version too old (H0042)

From http://localhost:1947/_int_/diag.html I can see the Run-time Installer and Run-time Package version are 8.13. Please let me know what other information I can provide to debug this problem.

↧