On 9/24/14 9:39 AM, pulkomandy wrote:
My next question is on how to handle the key. I think we need to keep it
secret so people can't easily extract it from our web browser and start
using it elsewhere. This means we can't hardcode it in our sourcecode
like I did for the openbmap one currently:
http://cgit.haiku-os.org/haiku/tree/src/kits/network/libnetapi/Geolocation.cpp

Do you have hints on how to handle that? Do you know how Firefox is doing
it?

Firefox and MozStumbler have build configuration files that are stored in a private repository. The Firefox and MozStumbler build files in the public source code repository look for the build configuration files at a well-known path or environment variable, which have the custom build information like API keys or Mozilla private keys.


chris
_______________________________________________
dev-geolocation mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-geolocation

Reply via email to