[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-hackers
Subject:    Re: AMD's memory encryption (aka SME)
From:       grarpamp <grarpamp () gmail ! com>
Date:       2021-01-25 8:55:45
Message-ID: CAD2Ti2_3q6k2g1twH4-R3W0gCbjUxYuFBYT0PMFR9NYVB3xyEg () mail ! gmail ! com
[Download RAW message or body]

> does anyone have an opinion on AMD's "Secure Memory Encryption"? This
> transparently encrypts all/most RAM pages.
> Looking at some tech docs, this seems fairly easy to implement.
> I was wondering if someone has attempted that already, or knows of
> reasons why not to.

Consider applications to rowhammer, cold boot attacks, shared
hosting, VM, poison, etc... there are papers on some use cases.
AMD SME has some different levels with EPYC being full
featured, TR and PRO differently, than even consumer cpu last.
FreeBSD should also implement sysctl that writes random
to all memory (even over kernel) just before halt / reboot call.
Similar for unallocated upon sleep, upon alloc release,
and as background scrub.
User can already choose random upon alloc with malloc.conf
but that is different than above.
Also: memtest86[+] integration.
_______________________________________________
freebsd-hackers@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic