lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 15 Sep 2021 17:35:40 +0200
From:   David Hildenbrand <>
To:     "Kirill A. Shutemov" <>
Cc:     Chao Peng <>,
        "Kirill A. Shutemov" <>,
        Andy Lutomirski <>,
        Sean Christopherson <>,
        Paolo Bonzini <>,
        Vitaly Kuznetsov <>,
        Wanpeng Li <>,
        Jim Mattson <>,
        Joerg Roedel <>,,, Borislav Petkov <>,
        Andrew Morton <>,
        Joerg Roedel <>,
        Andi Kleen <>,
        David Rientjes <>,
        Vlastimil Babka <>,
        Tom Lendacky <>,
        Thomas Gleixner <>,
        Peter Zijlstra <>,
        Ingo Molnar <>,
        Varad Gautam <>,
        Dario Faggioli <>,,,,
        Kuppuswamy Sathyanarayanan 
        Dave Hansen <>,
        Yu Zhang <>
Subject: Re: [RFC] KVM: mm: fd-based approach for supporting KVM guest private

>>> who will actually do some kind of gfn-epfn etc. mapping, how we'll
>>> forbid access to this memory e.g., via /proc/kcore or when dumping memory
>> It's not aimed to prevent root to shoot into his leg. Root do root.
> IMHO being root is not an excuse to read some random file (actually used
> in production environments) to result in the machine crashing. Not
> acceptable for distributions.
I just realized that reading encrypted memory should be ok and only 
writing is an issue, right?


David / dhildenb

Powered by blists - more mailing lists