Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 8 Sep 2012 14:55:22 +0200
From: magnum <>
Subject: Re: New formats: KRB5-18 and KRB5-23

On 8 Sep, 2012, at 14:51 , Dhiru Kholia <> wrote:

> On Sat, Sep 8, 2012 at 6:17 PM, magnum <> wrote:
>> I tried this on OSX and now got this:
>> Benchmarking: KRB5 aes256-cts-hmac-sha1-96 [32/64]...
>> Program received signal EXC_BAD_ACCESS, Could not access memory.
>> Reason: 13 at address: 0x0000000000000000
>> 0x00000001000408ac in crypt_all (count=98745856) at krb5-18_fmt.c:198
>> 198                   crypt_out[index][i] = (key.contents[4 * i]) |
>> (gdb) bt
>> #0  0x00000001000408ac in crypt_all (count=98745856) at krb5-18_fmt.c:198
>> #1  0x0000000100099b46 in fmt_self_test (format=0x1002dff20) at formats.c:104
>> Previous frame inner to this frame (gdb could not unwind past this frame)
>> This is a non-OMP build. Note the count=98745856... I'm puzzled this only happens on OSX.
> Did you have to install anything "extra" on OSX to build these
> formats? I can test and debug the format on my OSX VM.

No, it just worked right out of the box. On the other hand, that *may* be the problem. Maybe I end up using an incompatible Kerberos lib?


Powered by blists - more mailing lists

Your e-mail address:

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.