Tor built with mingw cannot handle large values for MaxAdvertisedBandwidth

Tor built with mingw on Windows cannot handle values larger than an unsigned int for MaxAdvertisedBandwidth, which causes a problem since the default value for MaxAdvertisedBandwidth is 128 TB.

getinfo version 250-version=0.1.2.8-beta 250 OK getconf maxadvertisedbandwidth 250 MaxAdvertisedBandwidth=0 setconf maxadvertisedbandwidth=4294967295 250 OK getconf maxadvertisedbandwidth 250 MaxAdvertisedBandwidth=4294967295 setconf maxadvertisedbandwidth=4294967296 250 OK getconf maxadvertisedbandwidth 250 MaxAdvertisedBandwidth=0

A side-effect of this problem is that Win32 users of Tor 0.1.2.8-beta are unable to start a Tor server with Vidalia, unless they manually set a value for MaxAdvertisedBandwidth to something greater than or equal to 10000 and less than 2!^32.

This problem has existed in previous Tor releases built with mingw (confirmed with the Tor 0.1.2.7-alpha Win32 binary), but most likely went unnoticed until nickm added a lower-bound on MaxAdvertisedBandwidth in r9652. The limitation does not occur if I build my own tor.exe using Microsoft's compiler.

[Automatically added by flyspray2trac: Operating System: All]

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information