| 2019-07-29 19:34:28 |
Sylvain |
bug |
|
|
added bug |
| 2019-07-29 19:34:28 |
Sylvain |
attachment added |
|
example file https://bugs.launchpad.net/bugs/1838334/+attachment/5279859/+files/aeskeyschedule |
|
| 2019-07-29 19:39:59 |
Sylvain |
description |
I found that aeskeyfind returns strange results on constraints. From the package or after compiling the git version of aeskeyfind (https://salsa.debian.org/pkg-security-team/aeskeyfind commit b62137e81487b397023fe94ccdd62fc239b57eac), when I run it on the example joined the report I have the following results:
aeskeyfind aeskeyschedule -v
FOUND POSSIBLE 128-BIT KEY AT BYTE 0
KEY: 2b7e151628aed2a6abf7158809cf4f3c
EXTENDED KEY:
2b7e151628aed2a6abf7158809cf4f3c
a0fafe1788542cb123a339392a6c7605
f2c295f27a96b9435935807a7359f67f
3d80477d4716fe3e1e237e446d7a883b
ef44a541a8525b7fb671253bdb0bad00
d4d1c6f87c839d87caf2b8bc11f915bc
6d88a37a110b3efddbf98641ca0093fd
4e54f70e5f5fc9f384a64fb24ea6dc4f
ead27321b58dbad2312bf5607f8d292f
ac7766f319fadc2128d12941575c006e
d014f9a8c9ee2589e13f0cc8b6630ca6
CONSTRAINTS ON ROWS:
00000001000000000000000000000000
000000e5000000000000000000000000
0000008f000000000000000000000000
0000003c000000000000000000000000
000000b9000000000000000000000000
00000082000000000000000000000000
00000074000000000000000000000000
0000002f000000000000000000000000
000000d2000000000000000000000000
0000005b000000000000000000000000
Keyfind progress: 100%
The key is correct, however, I should have constraints on rows equal zero this the key schedule is correct as well. I recompile aeskeyfind with only the optimization change to -O2 and then I obtained the resutl I expect with all constraints to zero.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: aeskeyfind 1:1.0-4
ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
Uname: Linux 4.15.0-55-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 29 21:29:16 2019
Dependencies:
gcc-8-base 8.3.0-6ubuntu1~18.04.1
libc6 2.27-3ubuntu1
libgcc1 1:8.3.0-6ubuntu1~18.04.1
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-05-02 (453 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: aeskeyfind
UpgradeStatus: No upgrade log present (probably fresh install) |
I found that aeskeyfind returns strange results on constraints. From the package or after compiling the git version of aeskeyfind (https://salsa.debian.org/pkg-security-team/aeskeyfind commit b62137e81487b397023fe94ccdd62fc239b57eac), when I run it on the example joined in the report I have the following results:
aeskeyfind aeskeyschedule -v
FOUND POSSIBLE 128-BIT KEY AT BYTE 0
KEY: 2b7e151628aed2a6abf7158809cf4f3c
EXTENDED KEY:
2b7e151628aed2a6abf7158809cf4f3c
a0fafe1788542cb123a339392a6c7605
f2c295f27a96b9435935807a7359f67f
3d80477d4716fe3e1e237e446d7a883b
ef44a541a8525b7fb671253bdb0bad00
d4d1c6f87c839d87caf2b8bc11f915bc
6d88a37a110b3efddbf98641ca0093fd
4e54f70e5f5fc9f384a64fb24ea6dc4f
ead27321b58dbad2312bf5607f8d292f
ac7766f319fadc2128d12941575c006e
d014f9a8c9ee2589e13f0cc8b6630ca6
CONSTRAINTS ON ROWS:
00000001000000000000000000000000
000000e5000000000000000000000000
0000008f000000000000000000000000
0000003c000000000000000000000000
000000b9000000000000000000000000
00000082000000000000000000000000
00000074000000000000000000000000
0000002f000000000000000000000000
000000d2000000000000000000000000
0000005b000000000000000000000000
Keyfind progress: 100%
The key is correct, however, I should have constraints on rows equal zero this the key schedule is correct as well. I recompile aeskeyfind with only the optimization change to -O2 and then I obtained the resutl I expect with all constraints to zero.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: aeskeyfind 1:1.0-4
ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
Uname: Linux 4.15.0-55-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 29 21:29:16 2019
Dependencies:
gcc-8-base 8.3.0-6ubuntu1~18.04.1
libc6 2.27-3ubuntu1
libgcc1 1:8.3.0-6ubuntu1~18.04.1
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-05-02 (453 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: aeskeyfind
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2019-07-29 19:40:56 |
Sylvain |
description |
I found that aeskeyfind returns strange results on constraints. From the package or after compiling the git version of aeskeyfind (https://salsa.debian.org/pkg-security-team/aeskeyfind commit b62137e81487b397023fe94ccdd62fc239b57eac), when I run it on the example joined in the report I have the following results:
aeskeyfind aeskeyschedule -v
FOUND POSSIBLE 128-BIT KEY AT BYTE 0
KEY: 2b7e151628aed2a6abf7158809cf4f3c
EXTENDED KEY:
2b7e151628aed2a6abf7158809cf4f3c
a0fafe1788542cb123a339392a6c7605
f2c295f27a96b9435935807a7359f67f
3d80477d4716fe3e1e237e446d7a883b
ef44a541a8525b7fb671253bdb0bad00
d4d1c6f87c839d87caf2b8bc11f915bc
6d88a37a110b3efddbf98641ca0093fd
4e54f70e5f5fc9f384a64fb24ea6dc4f
ead27321b58dbad2312bf5607f8d292f
ac7766f319fadc2128d12941575c006e
d014f9a8c9ee2589e13f0cc8b6630ca6
CONSTRAINTS ON ROWS:
00000001000000000000000000000000
000000e5000000000000000000000000
0000008f000000000000000000000000
0000003c000000000000000000000000
000000b9000000000000000000000000
00000082000000000000000000000000
00000074000000000000000000000000
0000002f000000000000000000000000
000000d2000000000000000000000000
0000005b000000000000000000000000
Keyfind progress: 100%
The key is correct, however, I should have constraints on rows equal zero this the key schedule is correct as well. I recompile aeskeyfind with only the optimization change to -O2 and then I obtained the resutl I expect with all constraints to zero.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: aeskeyfind 1:1.0-4
ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
Uname: Linux 4.15.0-55-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 29 21:29:16 2019
Dependencies:
gcc-8-base 8.3.0-6ubuntu1~18.04.1
libc6 2.27-3ubuntu1
libgcc1 1:8.3.0-6ubuntu1~18.04.1
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-05-02 (453 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: aeskeyfind
UpgradeStatus: No upgrade log present (probably fresh install) |
I found that aeskeyfind returns strange results on constraints. From the package or after compiling the git version of aeskeyfind (https://salsa.debian.org/pkg-security-team/aeskeyfind commit b62137e81487b397023fe94ccdd62fc239b57eac), when I run it on the example joined in the report I have the following results:
aeskeyfind aeskeyschedule -v
FOUND POSSIBLE 128-BIT KEY AT BYTE 0
KEY: 2b7e151628aed2a6abf7158809cf4f3c
EXTENDED KEY:
2b7e151628aed2a6abf7158809cf4f3c
a0fafe1788542cb123a339392a6c7605
f2c295f27a96b9435935807a7359f67f
3d80477d4716fe3e1e237e446d7a883b
ef44a541a8525b7fb671253bdb0bad00
d4d1c6f87c839d87caf2b8bc11f915bc
6d88a37a110b3efddbf98641ca0093fd
4e54f70e5f5fc9f384a64fb24ea6dc4f
ead27321b58dbad2312bf5607f8d292f
ac7766f319fadc2128d12941575c006e
d014f9a8c9ee2589e13f0cc8b6630ca6
CONSTRAINTS ON ROWS:
00000001000000000000000000000000
000000e5000000000000000000000000
0000008f000000000000000000000000
0000003c000000000000000000000000
000000b9000000000000000000000000
00000082000000000000000000000000
00000074000000000000000000000000
0000002f000000000000000000000000
000000d2000000000000000000000000
0000005b000000000000000000000000
Keyfind progress: 100%
The key is correct, however, I should have constraints on rows equal zero since the key schedule is correct as well. I recompiled aeskeyfind with only the optimization option changed to -O2 and then I obtained the result I expected with all constraints to zero.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: aeskeyfind 1:1.0-4
ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
Uname: Linux 4.15.0-55-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 29 21:29:16 2019
Dependencies:
gcc-8-base 8.3.0-6ubuntu1~18.04.1
libc6 2.27-3ubuntu1
libgcc1 1:8.3.0-6ubuntu1~18.04.1
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-05-02 (453 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: aeskeyfind
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2019-07-29 19:42:57 |
Sylvain |
summary |
aeskeyfind constraints results |
aeskeyfind problem with constraints results |
|
| 2021-06-09 22:44:02 |
Samuel Henrique |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989179 |
|
| 2021-06-09 22:44:02 |
Samuel Henrique |
bug task added |
|
aeskeyfind (Debian) |
|
| 2021-06-10 00:12:00 |
Bug Watch Updater |
aeskeyfind (Debian): status |
Unknown |
Confirmed |
|
| 2021-06-10 16:23:40 |
Launchpad Janitor |
aeskeyfind (Ubuntu): status |
New |
Fix Released |
|
| 2021-06-11 01:33:31 |
Bug Watch Updater |
aeskeyfind (Debian): status |
Confirmed |
Fix Released |
|
