Re: [openssl-users] FIPSLD 2.0.5 (HP-UX AI64 11.23) fails to link with pthread error

2015-03-02 Thread Mrunal Nerpawar
of the security policy, you’re free to modify it. Just don’t modify it such that the security policy is no longer followed. Generally speaking, adding more options to the compile and link steps will be safe. TOM On Feb 23, 2015, at 4:36 AM, Mrunal Nerpawar p.mru...@gmail.com wrote: Details

[openssl-users] FIPSLD 2.0.5 (HP-UX AI64 11.23) fails to link with pthread error

2015-02-23 Thread Mrunal Nerpawar
Details == Fips 2.0.5 configured with no-asm and threads. Openssl 1.0.1H configured with shared, fips, threads no-asm (many alogos omitted) compiler - using aCC 6.25 on HPUX-IA64 11.23. bash-2.05$ aCC --version aCC: HP C/aC++ B3910B A.06.25.02 [Nov 25 2010] bash-2.05$ product linking with

Re: Linking error on Soalris x86 and sparc using fips capable openssl 1.0.1h

2014-09-17 Thread Mrunal Nerpawar
Thanks all for the help. I could resolve both the errors: Sun-Intel : using -Wl, -Bsymbolic and resolving few other linking errors. Sun-sparc : Re-building libstdc++ all the errors gone away. Thanks again Andy for pointing it out. Regards, Mrunal On Mon, Sep 15, 2014 at 12:40 AM, Andy

Linking error on Soalris x86 and sparc using fips capable openssl 1.0.1h

2014-09-12 Thread Mrunal Nerpawar
Hi All, While fips build on soalris, I am getting variour errors: Sun-Intel: FIPSLD_CC=gcc FIPSLD_LINK=g++ /unixhome/upg/Unix/SunOS/i386/OpenSource/ssl-1.0.1h/bin/fipsld -fPIC -shared -g -O2 -o libImpl.so.10.0.0 -lcrypto Text relocation remains referenced against

How to use Blowfish

2011-09-13 Thread Mrunal Nerpawar
Hi, I have a use case for one of the product that I work on. I need to know if the passwords on the unix machines are weak. The passwords are hashed using blowfish algorithm. I shall be doing dictionary encryption using blowfish API to find the weak passwords. I am using openssl/blowfish for