New version: Thales.SafeNetAuthenticationClient version 10.9.3283.0

[Dragon1573]

Checklist for Pull Requests

• Have you signed the Contributor License Agreement?
• Resolve [Update Request]: Thales.SafeNetAuthenticationClient version 10.9.3283.0 (arm64 + x86 + x64) = CVE-2023-7016 patch #173741

Manifests

• Have you checked that there aren't other open pull requests for the same manifest update/change?
• This PR only modifies one (1) manifest
• Have you validated your manifest locally with winget validate --manifest <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
• Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[stephengillie]

Automatic Validation ended with:

No errors to post.

(Automated response - build 895.)

[R-Adrian]

question: does the slash direction matter for syntax validation in RelativeFilePath?
i see that this PR uses forward slashes while most other PRs i've seen use back slashes

e.g.
RelativeFilePath: Msi/x64/SafeNetAuthenticationClient-x64-10.9.msi
vs
RelativeFilePath: Msi\x64\SafeNetAuthenticationClient-x64-10.9.msi

update: looking at the ZIP format APPNOTE.TXT specification it looks like forward slashes is actually the correct format.
quote:

   4.4.17 file name: (Variable)

       4.4.17.1 The name of the file, with optional relative path.
       The path stored MUST NOT contain a drive or
       device letter, or a leading slash.  All slashes
       MUST be forward slashes '/' as opposed to
       backwards slashes '\' for compatibility with Amiga
       and UNIX file systems etc.  If input came from standard
       input, there is no file name field.  

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[stephengillie]

Automatic Validation ended with:

Installation failed with exit code -1978335141
2024-09-17 03:19:00.701 [CLI ] Unable to locate nested installer at: C:\Users\VALIDA1\AppData\Local\Temp\WinGet\Thales.SafeNetAuthenticationClient.10.9.3283.0\extracted\Msi/x64/SafeNetAuthenticationClient-x64-10.9.msi
2024-09-17 03:18:52.553 [CLI ] Unable to locate nested installer at: C:\Users\VALIDA1\AppData\Local\Temp\WinGet\Thales.SafeNetAuthenticationClient.10.9.3283.0\extracted\Msi/x32/SafeNetAuthenticationClient-x32-10.9.msi

Automated error analysis suggests -1978335141 may mean Unable to locate nested installer. Does the RelativeFilePath have the previous version number in it?

(Automated response - build 895.)

[stephengillie]

question: does the slash direction matter for syntax validation in RelativeFilePath? i see that this PR uses forward slashes while most other PRs i've seen use back slashes

e.g. RelativeFilePath: Msi/x64/SafeNetAuthenticationClient-x64-10.9.msi vs RelativeFilePath: Msi\x64\SafeNetAuthenticationClient-x64-10.9.msi

update: looking at the ZIP format APPNOTE.TXT specification it looks like forward slashes is actually the correct format. quote:

   4.4.17 file name: (Variable)

       4.4.17.1 The name of the file, with optional relative path.
       The path stored MUST NOT contain a drive or
       device letter, or a leading slash.  All slashes
       MUST be forward slashes '/' as opposed to
       backwards slashes '\' for compatibility with Amiga
       and UNIX file systems etc.  If input came from standard
       input, there is no file name field.  

This is something that we're not currently checking, but probably should be. We usually don't notice it, I believe, because the string is likely used on a Windows system after replacing the slashes for backslashes,

[stephengillie]

Hi @Dragon1573,

It appears that a folder is missing from the RelativeFilePath:

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[wingetbot]

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.