If they are in the hmac code that's probably my fault when I put it
back in the repo.
I don't think it will be causing any problems, as we do not run in any
16 bit platform guint is either equal to guint32 or larger (64) and
the way the code is written is protected from both endianity and word
lenght (as far as it is at least 32 bits).
However, go ahead and change it.
On 3/16/07, Sebastien Tandel <sebastien@xxxxxxxxx> wrote:
Hi,
just for curiosity purposes :
I'm looking at crypt-sha1.c, and seeing variables defined as guint and
not as guint32. On the other hand, we can also read in the header file
that Anders changed uint to uint32_t in 2004.
Are there some conflicts? Are there some reasons to keep the guint
instead of guint32?
Regards,
Sebastien Tandel
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev
--
This information is top security. When you have read it, destroy yourself.
-- Marshall McLuhan
