code without sources distributed in 7b130

[Valerie (Yu-Ching) Peng]

The binaries under test/sun/security/pkcs11/nss/lib is used for running 
PKCS11 regression tests.
They have been there since the start.

As for the hardcoded path in test/sun/security/pkcs11/Provider/csp.cfg, 
it's only for testing the configuration parsing code, i.e. it doesn't 
error out when encountering "~".
Valerie

On 05/03/11 14:34, Dr Andrew John Hughes wrote:
>>
>> in jdk:
>> test/sun/security/pkcs11/nss/lib/ various precompiled shared libraries. Is it 
>> necessary to distribute these with the jdk sources? Checked that these files are 
>> available on Debian and Ubuntu distributions
>>
>> libsoftokn3.so: in /usr/lib, package libnss3-1d/libnss3
>> libnss3.so: same
>> libnssckbi.so: in /usr/lib/nss
>>
>> libnspr4.so: in /usr/lib, package libnspr4-0d/libnspr4
>> libplds4.so: same
>> libplc4.so: same
>>
>> thanks, Matthias
>>     
>
> I agree these binaries shouldn't be in the repositories.  Seems things are slipping again.
> Thanks for spotting.  Either hg is lying or these have been there since the start.
>
> $ hg log -R jdk jdk/test/sun/security/pkcs11/nss/lib/linux-i586/libnssckbi.so 
>
> Worst case, we can hg rm these from the IcedTea forest.  I've now made this accessible to
> all IcedTea committers on http://icedtea.classpath.org/hg/icedtea7-forest
>
> Could someone also explain
> 6581254: pkcs11 provider fails to parse configuration file contains windows short path
> which introduces a file with hardcoded Windows paths
> test/sun/security/pkcs11/Provider/csp.cfg ?
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/security-dev/attachments/20110503/ecce357e/attachment.htm>