Changes between Initial Version and Version 1 of Ticket #1782, comment 3


Ignore:
Timestamp:
Dec 12, 2023, 7:07:04 PM (5 months ago)
Author:
Adam Piggott

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1782, comment 3

    initial v1  
    1 -NoVerify works. I get the same failure when gpg.exe is in the same directory as the updater script.
     1`-NoVerify` works. I get the same failure when gpg.exe is in the same directory as the updater script.
    22
    33Is the fact that the script appears to try to launch "gpg.exe gpg.exe" relevant? Looking through a Sysinternals Process Monitor trace, powershell.exe searches the directories in PATH for "gpg.*" and get a success result in gpg.exe's parent directory, for "gpg.exe". Afterwards it then issues searches for "gpg.exe gpg.exe.*" in the same directories and gets no results.
    … …  
    66From the same Powershell prompt:
    77
     8{{{
    89> gpg --version
    910gpg (GnuPG) 2.4.3
    1011libgcrypt 1.10.2
     12}}}
    1113
    1214Powershell version table shows mine is somewhat more recent. I haven't manually installed or changed my Powershell install (other than to allow execution of 'untrusted' scripts).
    1315
     16{{{
    1417PSVersion                      5.1.19041.3758
    1518PSEdition                      Desktop
    … …  
    2023PSRemotingProtocolVersion      2.3
    2124SerializationVersion           1.1.0.1
     25}}}