hat jemand ein Verständnis dafür, wie der Prozess der Dateiverschlüsselung im System abläuft? Ich versuche, die Firmware des Systems zu analysieren und Programme/Skripte/Bibliotheken zu finden, die den Inhalt des Kathologen /Data/mnt-c/public entschlüsseln. Ich vermute, dass das CAAM-Modul verwendet wird. ich muss verstehen, wie man das Dekriptieren von Dateien in diesem Verzeichnis aufruft. Ich verstehe, dass es dieser Person gelungen ist, diese Frage zu klären, aber ich weiß nicht, wie ich sie erreichen soll.
Posts by pepelxl
-
-
GitHub - pepelxl/psa_coder: encoding of the Stellantis ECUencoding of the Stellantis ECU. Contribute to pepelxl/psa_coder development by creating an account on GitHub.github.com
Sie können mit diesem Programm Kodierungen ändern
-
-
i decompiled rcc firmware. you can decompile your device firmware with examples https://github.com/ludwig-v/ps…mware-reverse-engineering . and find similar values.
-
diese Datei befindet sich in RCC(bosch)
-
XML
<?xml version="1.0" encoding="UTF-8"?> <DisplayConfiguration> <Version> 4.0 </Version> <Display id="0" name="Bosch Developer Display" dp_device_name="sharp_psa_rcc_a2_7inch" width_pix="800" height_pix="480" width_mm="155" height_mm="82" capability_touch="single" ilm_env_file="layer-management-env-file-16bit.txt"/> <Display id="1" name="Continental Low Speed" dp_device_name="dg4tp_protob_7inch" width_pix="800" height_pix="480" width_mm="152.4" height_mm="91.44" capability_touch="single" ilm_env_file="layer-management-env-file-16bit.txt"/> <Display id="2" name="Magneti Marelli" dp_device_name="dgt8c_protob3_8inch" width_pix="800" height_pix="480" width_mm="174" height_mm="104.4" capability_touch="multi" ilm_env_file="layer-management-env-file-32bit.txt"/> <Display id="3" name="Valeo" dp_device_name="dgt7cff_7inch" width_pix="800" height_pix="480" width_mm="152.4" height_mm="91.44" capability_touch ="multi" ilm_env_file="layer-management-env-file-16bit.txt"/> <Display id="4" name="Continental High Speed" dp_device_name="dgt7c_protob3_7inch" width_pix="800" height_pix="480" width_mm="152.4" height_mm="91.44" capability_touch ="multi" ilm_env_file="layer-management-env-file-16bit.txt"/> </DisplayConfiguration> -
GitHub - pepelxl/psa_coder: encoding of the Stellantis ECUencoding of the Stellantis ECU. Contribute to pepelxl/psa_coder development by creating an account on GitHub.github.com
Это программное обеспечение может кодировать SMEG
Übersetzung - Diese Software kann kodieren
-
I realized that I was looking for too much. enc_key contains the encrypted key for the enc_data block.
enc_data->parameter is the IV data for the enc_data block.
enc_data - contains useful data.
Is there anyone who understands openssl? how do I properly extract the data and decompose it into readable data?
I can view the certificates using the commandCodeopenssl smime -pk7out -in license_UIN.key | openssl pkcs7 -text -noout -print_certsbut I would like to learn how to pull certificates into separate files.
I managed to get useful data using the command
Codeopenssl cms -in license_UIN.key -verify -noverify | openssl smime -decrypt -inkey RCC-privkey.pemBut this is not correct, something like:
Codeopenssl cms -in license_UIN.key -decript ...How do I assemble the right сommand?
-
I'm still searching for information that is encrypted in the enc_data block.
I found a way to decrypt the enc_key block. This block stores the AES key to decrypt the update firmware. The block is decrypted with a unique key located in the head unit. But the key is not suitable for decrypting the enc_data block. Does anyone have any ideas about decrypting this block for RCC? I've posted my best practices here.GitHub - pepelxl/psa-rcc-reverse: анализ прошивок магнитолы bosch RCC EUанализ прошивок магнитолы bosch RCC EU. Contribute to pepelxl/psa-rcc-reverse development by creating an account on GitHub.github.com -
how to view the contents of the license.key for updating the firmware?
example:Code
Display Moretype: pkcs7-envelopedData (1.2.840.113549.1.7.3) d.enveloped: version: 0 recipientinfo: version: 0 issuer_and_serial: issuer: C=FR, L=Paris, O=PSA Peugeot Citroen, OU=Certificate Authorities, OU=(c) PSA Peugeot Citroen - For authorized use only, OU=0002 319187308, CN=PSA - OVIP - Embedded component - G1 serial: 265785 key_enc_algor: algorithm: rsaEncryption (1.2.840.113549.1.1.1) parameter: NULL enc_key: 0000 - 29 e4 f5 3c e0 30 2d bb-e5 d0 8b 00 b8 55 f6 )..<.0-......U. 000f - 78 db 5a 69 fa f3 80 ec-fe 08 d5 f4 d7 3f c8 x.Zi.........?. 001e - 31 fa a7 62 bf 20 2a 2d-15 6e e1 68 26 88 6a 1..b. *-.n.h&.j 002d - 3a d7 c1 3d 8a d5 e6 cb-ee 8c 2b c5 91 45 30 :..=......+..E0 003c - 60 ad 24 97 45 40 57 ad-49 31 4f 5e 15 b0 ea `.$.E@W.I1O^... 004b - 4d 19 4e 30 f2 17 da 14-71 4f 0a 91 7f f1 0c M.N0....qO..... 005a - 87 40 be 5a 0f 6d 1c 69-43 d0 fc 1d dd 77 61 .@.Z.m.iC....wa 0069 - 03 45 42 eb d5 19 d9 a6-35 cb b0 41 df 69 a0 .EB.....5..A.i. 0078 - d7 f2 ba bf 25 d4 0e b8-55 20 21 95 6e 6f 0b ....%...U !.no. 0087 - fa dc 05 d7 f2 85 30 31-98 06 3a dd 4b 90 4a ......01..:.K.J 0096 - b3 72 0e 1f 8c 9d 4c 09-76 2e 5d e5 de 2f 4c .r....L.v.]../L 00a5 - 92 ab eb 4c 88 44 cd 68-c4 b0 03 e5 1e 8b 4b ...L.D.h......K 00b4 - 36 e7 35 a0 98 9a bf e9-8d 60 f3 e9 35 29 e3 6.5......`..5). 00c3 - 9b 7a 07 09 43 b8 49 9b-d1 fe 75 b4 9b fc 98 .z..C.I...u.... 00d2 - 8b 5b 58 79 ed 0f 6f 95-f7 e3 e4 b0 df 83 68 .[Xy..o.......h 00e1 - 56 e6 bf cf eb 2c f5 a2-48 fc 9b 33 e7 63 3b V....,..H..3.c; 00f0 - c0 a6 70 69 78 5d 76 0d-ad 8d 2c c4 7c 4e 74 ..pix]v...,.|Nt 00ff - 8b . enc_data: content_type: pkcs7-data (1.2.840.113549.1.7.1) algorithm: algorithm: aes-256-cbc (2.16.840.1.101.3.4.1.42) parameter: OCTET STRING: 0000 - 51 31 3b 20 79 cf f9 ca-da 56 7d 1b ae 7e 3e Q1; y....V}..~> 000f - 5b [ enc_data: 0000 - 2c 36 70 56 d1 67 e7 f7-0e bc 6b af 9b 56 08 ,6pV.g....k..V. 000f - 08 c2 c8 19 f3 02 be 93-c1 2d 70 46 e2 73 37 .........-pF.s7 001e - 3f 59 20 47 9c a8 1f 9d-1d dd 8d 8f 51 ca 48 ?Y G........Q.H 002d - a6 4a d6 63 f0 50 3f ea-56 6d 05 f3 18 48 56 .J.c.P?.Vm...HV 003c - 28 59 69 2c 9f 21 2c 39-8b 66 9f 8f 10 64 e4 (Yi,.!,9.f...d. 004b - 25 26 a6 d0 6b 38 b9 33-5c 52 89 51 c7 f7 79 %&..k8.3\R.Q..y 005a - fd 82 d0 3f a9 11 71 05-da 73 fd 0d 33 3e d2 ...?..q..s..3>. 0069 - d4 95 fb 86 36 6b 68 6d-a4 25 79 a1 8a ff 0e ....6khm.%y.... 0078 - 62 d9 10 97 d8 1d 37 12-f6 55 d5 36 04 88 de b.....7..U.6... 0087 - 10 be 3d 6a 85 c3 f9 ac-d9 04 08 ec 33 96 e5 ..=j........3.. 0096 - 69 c3 62 42 a4 62 76 c4-ef 4f ce 8d dc 52 b3 i.bB.bv..O...R. 00a5 - 27 72 6f bd 80 27 c7 ab-d5 a7 74 'ro..'....twhat kind of data is hidden behind these two fields?
In the first case, there is a PSA signature - VIP - Embedded component - G1, which is easily downloaded. http://pki.p3cs.com/PSA-OVIP-EC-G1.crt . But its length is 4096 and I do not know how it can be used.