phc-discussions - Re: [PHC] further limitation: not writing secret to memory

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3953344.XD8cbxztZE@darkstar>
Date: Thu, 19 Sep 2013 21:04:07 +0400
From: "Sergey V." <sftp.mtuci@...il.com>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] further limitation: not writing secret to memory

On 2013-09-18 at 20:48:41, Krisztián Pintér <pinterkr@...il.com> wrote:
> Steve Thomas (at Wednesday, September 18, 2013, 7:58:25 PM):
> > I'm pretty sure page locked memory [...] never gets written to swap.
> 
> on a windows box, there are multiple ways of telling the OS not to swap 
> a memory block. but neither of those guarantees anything. i'm not a 
> linux guy, but as i'm informed, you can't do that ony linux either.

I suppose mlock(2) should works on linux.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)