Password sent over UDP, TCP/IP or HTTP to GpsGate.com, GpsGate Server or your own custom server are encrypted with the following algorithm. Running the algorithm on an encrypted password will decrypt it to clear text again.
The intention of the algorithm is only to avoid having passwords in cleartext displayed in logs, etc.
The above would print "GpsGate" on a web page, hope this helps!
Can anyone seeing my traffic decrypt the password? Can anyone see my username/latitude/longitude by looking at http traffic, not even needing to decrypt?
Wouldn't it be better to simply encrypt all traffic (des is fast, maybe aes) with the gpsgate.com password?
The purpose of the "encryption" is not to make it impossible to read the password, it is just that to avoid it being written in plain text in logs etc.
If you want to encrypt all http traffic you can configure your web to use https. You can do this on your own Gpsgate Server installation. GpsGate.com does currently not support https.
This algorithm drops all non-alphanum characters, is that intentional?
It makes the algorithm non-reversible.
example: "test#!#!#password" will be encrypted as "WILDHHZKGHVG" and decrypted into "testpassword"