[gem5-users] Re: Initialization for memory encription in se mode

2021-12-17 Thread Portero, Antonio via gem5-users
Sehr geehrte Herren/Frauen,
ich bin nicht im Büro und habe keine Internetverbindung. Erwarten Sie, dass 
sich meine Antwort bis zum 3. Januar verzögert.
Mit freundlichen Grüßen,
Antonio


Dear Sir/Madam,
I am out of office with low connection to internet. Expect delays in my answer 
till 3 January.
Best regards,
Antonio

On Dec 8, 2021, at 06:22, hiromichi.haneda--- via gem5-users 
 wrote:

I thought about encrypting the memory area where the binary was loaded once.
How is the area where the binaries are loaded chosen?
Is there a way to encrypt a specific memory area only once?
Or any other good initialization ideas?

Thank you.
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s




Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Volker Rieke
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr. Astrid Lambrecht,
Prof. Dr. Frauke Melchior



___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

[gem5-users] Re: Initialization for memory encription in se mode

2021-12-07 Thread hiromichi.haneda--- via gem5-users
I thought about encrypting the memory area where the binary was loaded once.
How is the area where the binaries are loaded chosen?
Is there a way to encrypt a specific memory area only once?
Or any other good initialization ideas?

Thank you.
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s


[gem5-users] Re: Initialization for memory encription in se mode

2021-12-06 Thread hiromichi.haneda--- via gem5-users
Here is an example of the code.
The cache is placed between the CPU and Enc/Dec Engine, and the data size is 
adjusted by setting the cacheline to 128 bits.
if(pkt->isWrite()){
unsigned char dec1[16];
for (int i = 0; i < 16; ++i){
dec1[i] = *(pkt->getConstPtr() + i);
}
unsigned char key[16] = {
0x2b, 0x7e, 0x15, 0x16, 0x28, 0xae, 0xd2, 0xa6, 0xab, 0xf7, 0x15, 
0x88, 0x09, 0xcf, 0x4f, 0x3c};
unsigned char enc1[16] = {};
AES128_ECB_Encrypt(key, dec1, enc1);
for (int i = 0; i < 16; ++i){
*(pkt->getPtr() + i) = enc1[i];
}
}
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s