> @MDF: > Before making even more effort on storing data objects, you should > definitely check if these objects are really private. My assumption is, > they are not. > Your assumption was wrong!
> $pkcs15-tool -C > ... > Path: 3f0050153303 (read 3f00/5015/3303) > ... > $opensc-explorer > OpenSC [3F00]> cd 5015 > OpenSC [3F00/5015]> cat 3303 > ... > File dump comes here, without pin verification !!!!! > ... > OpenSC [3F00/5015]> exit > [z...@test1 ~]$ pkcs15-tool -C Reading data object <0> applicationName: LUKS256 Label: applicationOID: NONE Path: 3f0050153404 Auth ID: 01 Reading data object <1> applicationName: LUKS1K Label: applicationOID: NONE Path: 3f0050153408 Auth ID: 02 Reading data object <2> applicationName: LUKS-Pub Label: applicationOID: NONE Path: 3f005015330b Auth ID: [z...@test1 ~]$ opensc-explorer OpenSC Explorer version 0.11.13 Using reader with a card: Aladdin eToken PRO 64 00 00 OpenSC [3F00]> cd 5015 OpenSC [3F00/5015]> cat 3404 [opensc-explorer] card-cardos.c:259:cardos_check_sw: required access right not granted [opensc-explorer] iso7816.c:129:iso7816_read_binary: returning with: Security status not satisfied [opensc-explorer] card.c:430:sc_read_binary: returning with: Security status not satisfied read failed: Security status not satisfied ACL for operation: CHV1 OpenSC [3F00/5015]> cat 3408 [opensc-explorer] card-cardos.c:259:cardos_check_sw: required access right not granted [opensc-explorer] iso7816.c:129:iso7816_read_binary: returning with: Security status not satisfied [opensc-explorer] card.c:430:sc_read_binary: returning with: Security status not satisfied read failed: Security status not satisfied ACL for operation: CHV3 OpenSC [3F00/5015]> cat 330b 00000000: 96 E3 25 3C 3E 28 10 8D 95 62 CE F0 6E A7 D6 8F ..%<>(...b..n... [...] _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
