#165 OpenSSI fails the glibc sha512c-test [ Not a bug ]

closed-works-for-me
nobody
None
5
2008-07-04
2008-07-03
John Hughes
No

This one is strange. If the glibc test "sha512c-test" is run on a non-initnode it fails. On the initnode it works.

$ gcc -DTIMEOUNT=10 sha512c-test.c -lcrypt
$ onnode 1 ./a.out
$ echo $?
0
$ onnode 2 ./a.out
Timed out: killed the child process
$ echo $?
1

Discussion

  • John Hughes

    John Hughes - 2008-07-03

    test from glibc test suite

     
  • Roger Tsang

    Roger Tsang - 2008-07-04

    Logged In: YES
    user_id=1246761
    Originator: NO

    Problem with your glibc? Can't reproduce this with glibc-2.3.6-0.fc3.1 on OpenSSI FC3.

    1. FC3 glibc doesn't support M_PERTURB.
    2. Test fails on any node, but does not timeout.

    # ./a.out
    test 0: expected "$6$saltstring$svn8UoSVapNtMuq1ukKS4tPQd8iKwSMHWjl/O817G3uBnIFNjnQJuesI68u4OTLiBFdcbYEdFCoEOfaS35inz1", got "$6x9WpaOdMM3g"
    test 1: expected "$6$rounds=10000$saltstringsaltst$OW1/O6BYHV6BcXZu8QVeXbDWra3Oeqh0sbHbbMCVNSnCM/UrjmM0Dp8vOuZeHBy/YTBmSK6H9qs/y3RnOaw5v.", got "$6x9WpaOdMM3g"
    test 2: expected "$6$rounds=5000$toolongsaltstrin$lQ8jolhgVRVhY4b5pZKaysCLi0QBxGoNeKQzQ3glMhwllF7oGDZxUhx1yxdYcz/e1JSbq3y6JMxxl8audkUEm0", got "$6x9tL3FIELQY"
    test 3: expected "$6$rounds=1400$anotherlongsalts$POfYwTEok97VWcjxIiSOjiykti.o/pQs.wPvMxQ6Fm7I6IoYN3CmLs66x9t0oSwbtEW7o7UmJEiDwGqd8p4ur1", got "$6MOs1CNBbb.6"
    test 4: expected "$6$rounds=77777$short$WuQyW2YR.hBNpjjRhpYD/ifIw05xdfeEyQoMxIXbkvr0gge1a1x3yRULJ5CCaUeOxFmtlcGZelFl5CxtgfiAc0", got "$65OJsZ2gre4c"
    test 5: expected "$6$rounds=123456$asaltof16chars..$BtCwjqMJGx5hrJhZywWvt0RLE8uZ4oPwcelCjmw2kSYu.Ec6ycULevoBK25fs2xXgMNrCzIMVcgEJAstJeonj1", got "$6lfLcCIGbasI"
    test 6: expected "$6$rounds=1000$roundstoolow$kUMsbe306n21p9R.FRkW3IGn.S9NPN0x50YhH1xhLsPuWGsUSklZt58jaTfF4ZEQpyUNGc0dqbpBYYBaHHrsX.", got "$69X7GLn2NAcI"

     
  • Roger Tsang

    Roger Tsang - 2008-07-04
    • status: open --> open-works-for-me
     
  • Nobody/Anonymous

    Logged In: NO

    Yeah, I get the same behaviour with glibc-2.3.6

    I'll keep investigating

     
  • John Hughes

    John Hughes - 2008-07-04
    • summary: OpenSSI fails the glibc sha512c-test --> OpenSSI fails the glibc sha512c-test [ Not a bug ]
    • status: open-works-for-me --> closed-works-for-me
     
  • John Hughes

    John Hughes - 2008-07-04

    Logged In: YES
    user_id=166336
    Originator: YES

    Nothing to do with OpenSSI - problem is that my 2nd node, a 2.0GHZ PIV is too slow to run this test in the 2 seconds allowed!

    $ TIMEOUTFACTOR=100 time ./a.out
    2.16user 0.00system 0:02.16elapsed 100%CPU (0avgtext+0avgdata 0maxresident)k
    0inputs+0outputs (0major+155minor)pagefaults 0swaps

    $ TIMEOUTFACTOR=100 onnode 1 time ./a.out
    1.50user 0.00system 0:01.54elapsed 97%CPU (0avgtext+0avgdata 0maxresident)k
    0inputs+0outputs (0major+154minor)pagefaults 0swaps

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks