-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Encryption does not work on certain PCs (older HP Z400) #8
Comments
Unfortunately, I don't have access to that exact machine. Please update to latest main branch code (also tagged v2.1.2) and try:
Try the above on the HPZ400 that fails. Is it possible that the HP Z400 has faulty RAM? eg you can run memtest86 on that box to verify that hypothesis. At this point, from the logs above - I can't find an obvious fault in the program.. |
Good morning,
thx for looking into this. I do have 4 of these HP-Z400 machines.
I've observed the misbehavior on two of them, for the other two, I
didn't check so far.
I doubt that the bug is caused by faulty ram.
Executing the tests on the HP-Z400 machines is a bit tricky, since I
don't have
devtools and go available on them.
What I've done:
- Checking out version 2.1.2
- Building it on my local machine
- Copying it to the 3rd HP-Z400 (including the compiled binaries)
- Modifying `tests.sh` a little bit
- Execute `tests.sh` on the machine
It leads to this output:
```
***@***.***:~/sigtool$ ./tests.sh
./bin/linux-amd64/sigtool: decrypt: can't decrypt chunk 0: cipher:
message authentication failed
tests.sh: can't decrypt with /tmp/sigtool17078/ssk2
tests.sh: Test output in /tmp/sigtool17078 ..
```
So same error as on the other two HP-Z400.
Here the DIFF for tests.sh: #9
```diff
diff --git a/tests.sh b/tests.sh
index 4184a46..3d180cc 100755
--- a/tests.sh
+++ b/tests.sh
@@ -2,9 +2,11 @@
# simple round-trip tests to verify the tool
-
-arch=`./build --print-arch`
-bin=./bin/$arch/sigtool
+bin="`for sigtool in ./bin/*/sigtool; do test -x "${sigtool}" && {
"${sigtool}" -h >/dev/null 2>&1 && { echo "${sigtool}"; exit 0; }; };
done`"
+test -z "${bin}" && {
+ arch=`./build --print-arch`
+ bin=./bin/$arch/sigtool
+}
Z=`basename $0`
# workdir
```
Am 2022-06-05 22:51, schrieb Sudhi Herle:
Unfortunately, I don't have access to that exact machine.
Please update to latest main branch code (also tagged v2.1.2) and try:
* make test
* ./tests.sh
Try the above on the HPZ400 that fails. Is it possible that the HP Z400
has faulty RAM? eg you can run memtest86 on that box to verify that
hypothesis.
At this point, from the logs above - I can't find an obvious fault in
the program..
--
Reply to this email directly, view it on GitHub [1], or unsubscribe
[2].
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I have created a new branch - "debug-hpz400"; the code here has a global debug option: sigtool --debug encrypt .... This debug flag prints several key derivation data to stderr. please checkout the head of that branch: git clone -b debug-hpz400 https://github.com/opencoff/sigtool sigtool-debug Build it as before and re-run your tests but with one change: Add "--debug" to the global sigtool flags. We should expect to see the same set of keys derived on the encryptor and decryptor machines. If they don't match - that is one reason why decrypt on hpz400 fails.. Thanks, |
I am on vacation at the moment, so it will take me two weeks or three to do this. Thx for your help
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
Am 17. Juni 2022 17:24:49 MESZ schrieb Sudhi Herle ***@***.***>:
…I have created a new branch - "debug-hpz400"; the code here has a global debug option:
sigtool --debug encrypt ....
sigtool --debug decrypt ...
This debug flag prints several key derivation data to *stderr*.
please checkout the head of that branch:
git clone -b debug-hpz400 https://github.com/opencoff/sigtool sigtool-debug
Build it as before and re-run your tests but with one change:
Add "--debug" to the global sigtool flags.
We should expect to see the same set of keys derived on the encryptor and decryptor machines. If they don't match - that is one reason why decrypt on hpz400 fails..
Thanks,
--
Reply to this email directly or view it on GitHub:
#8 (comment)
You are receiving this because you commented.
Message ID: ***@***.***>
|
I'm back. The output looks OK to me:
|
Very strange indeed. Could you try running the test binary compiled on other machine and run it on the HPZ400 like so:
|
(Removed due to bad formatting)
|
Here you are:
|
I'm using "sigtool" on various ubuntu 20.04 PCs. I'm using the same binary on all of them. Typically, it works OK.
However, on a certain type of PC, encryption produces a file that cannot be decrypted. Decryption produces an error
message like this:
Any idea?
I've added a test script below. I've made "mixed tests" as well, meaning encrypt a file on
PC#A and decrypt it on PC#B. Outcome: Encryption doesn't work on the HP Z400 PCs.
Test Script
OK Output
KO Output
Observed on two older HP Z 400 PCs.
The text was updated successfully, but these errors were encountered: