MIME-Version: 1.0
In-Reply-To: <rt-3.8.6-2430-1412785522-1379.37410-0-0@isc.org>
X-Mailer: MIME-tools 5.428 (Entity 5.428)
Content-Disposition: inline
References: <543560E8.5070902@redhat.com>
 <rt-3.8.6-2430-1412785522-1379.37410-0-0@isc.org>
Content-Type: text/plain; charset="UTF-8"
Message-ID: <rt-3.8.6-2438-1412786465-756.37410-0-0@isc.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
RT-Send-CC:
Content-Length: 495

> In fact the PIN maximum length is a property of the HSM
> so I'll dig in the new PKCS#11 v2.40 specs I copied from OASIS
> some hours ago to see if there is useful about it in them...
 
=> ulMinPinLen and ulMaxPinLen are members
of the CK_TOKEN_INFO structure, so one can check
for the range used by its HSM(s).
Of course, the PKCS#11 specs give nothing about the
reasonable values... SoftHSMv2 uses the 4..255 range
(so 32 could be too small).

BTW, what is the HSM where you need long PINs?