phc-discussions - Re: [PHC] Specification of a modular crypt format

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: <CA+hr98FrNyvLEDS9bsUuAb3k8NeWoEMx17fSeR=03NYFhsnvhg@mail.gmail.com>
Date: Thu, 17 Sep 2015 15:17:53 +0200
From: Krisztián Pintér <pinterkr@...il.com>
To: "discussions@...sword-hashing.net" <discussions@...sword-hashing.net>
Subject: Re: [PHC] Specification of a modular crypt format

On Thu, Sep 17, 2015 at 2:15 PM, Thomas Pornin <pornin@...et.org> wrote:
> In an object-oriented implementation, the generic parser would be given
> not a lost of parameters, but an associative map of parameter names to
> instances that parse the specific parameter values.

i would assume any language supporting associative maps also supports
a list/array of tuples. am i wrong in that assumption? i must admit,
i'm a little lagged behind on modern languages.it certainly does not
seem to be a problem in c#, python and rust. have no clue about perl.