Well, if I remember it was 60bits, not 32, but what I was suggesting is not that mIRC add sha1.cpp into mIRC, Windows already has an SHA1 function. All I'm saying is mIRC should just use Microsoft's CryptoAPI to add support for SHA1, then there are no export restrictions to worry about because it is then MS's job to worry about that, not mIRC. Also the US does allow exporting of strong crypto, you just have to go through a bunch of stuff to get your program approved by the government. Thats mainly to make sure, for example, that someone doesn't make a program that uses strong crypto for a detonator for a bomb or something else that would potentially cause more problems than good.
