Date: Tue, 29 Jan 2013 18:13:36 -0600 From: "jfoug" <jfoug@....net> To: <john-dev@...ts.openwall.com> Subject: RE: dmg2john The C99 stdint.h is fine in JtR. BUT (and that is a big BUT), use: #include "stdint.h" and NOT #include <stdint.h> There are JtR specific stdint.h and stdbool.h file in JtR's source. The detect version of STDC, and if applicable, load <stdint.h> If the version is not applicable, then they simply define things the way stdint.h would do so. NOTE, there are several files at this time, which are using the <stdint.h> (and break some compilers). The blake stuff is some, and there are some others. Jim. From: Milen Rangelov [mailto:gat3way@...il.com] Sent: Tuesday, January 29, 2013 17:46 To: john-dev@...ts.openwall.com Subject: Re: [john-dev] dmg2john uint64_t I meant. I don't know if C99 stdint.h stuff is acceptable for jtr though, but it really helps in situations like that. But definitely long is 32-bit int on both x86 and x86_64. Also the compiler likes to do some implicit casts, I would never trust it to do that even if unsigned long long was used. Better thing is assign that to a variable that is definitely 64-bit int, then use it. Content of type "text/html" skipped
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.