Use |mprotect()| to secure key data ? / was: Re: Proposal: always handle keys in separate process

[Gert Doering]

Hi,

On Wed, Jan 20, 2016 at 01:53:41AM +0100, Roland Mainz wrote:
> >> any performance impact if the code is switched to plain { |open()|,
> >> |read()|, ... } (with sufficient wrappers for |EINTR| handling) ?
> 
> Well, I am not happy with the solution because it adds *lots* of extra
> overhead (not noticeable on today's multi-GHz desktop machines but on
> small embedded machines this bites back).

Actually, "open(), read(full file size), close()" is *less* overhead than
mixing in an extra stdio layer.  Of course what you don't want to do is
single-byte-read()s then...

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert at greenie.muc.de
fax: +49-89-35655025                        gert at net.informatik.tu-muenchen.de