This is the mail archive of the
mailing list for the GCC project.
Re: Compiler support for erasure of sensitive data
- From: Marcos Diaz <marcos dot diaz at tallertechnologies dot com>
- To: zackw at panix dot com, andres dot tiraboschi at tallertechnologies dot com, gcc at gcc dot gnu dot org, daniel dot gutson at tallertechnologies dot com
- Date: Mon, 29 Feb 2016 18:14:22 -0300
- Subject: Re: Compiler support for erasure of sensitive data
- Authentication-results: sourceware.org; auth=none
- References: <55F0653C dot 9010903 at panix dot com>
Hi, we are facing the same issue. This bugzilla was opened:
We were thinking on making a function attribute that ensures that non necessary registers, or stack frames used by the function will be correctly cleared before returning.
We think in implementing for x86_64 as a first work.
For this we are trying to modify the epilogue generation. Here we should have the information of which registers this function used, and the size of the stack frame to clean. The downside of this is that will be architecture dependent.
Do you think this is a good idea? Do you suggest something else?