[Marble-devel] What to do with api keys

[Utku Aydın]

Hello,

Storing in clear text is how I deal with Foursquare plugin's own API key
actually. I asked the same question too, on IRC channel a while ago.

Regards,
Utku Aydın
26 Kas 2012 17:25 tarihinde "Anders Lund" <anders at alweb.dk> yazdı:

> Hi,
>
> I have written a plugin for displaying geocaches from opencaching.com,
> mainly
> to get my feet wet with a web service and QJson without having to deal with
> oauth, that is used by opencaching.pl (and others using their API).
>
> To access opencaching.com, I got an API key from the site, and now the
> question is how to deal with that in the opensource context.
>
> The key is just a text string, and it is used as part of the URL sent to
> get
> data from the service, like
> http://www.opencaching.com/api/geocache/?Authorization=<key>&<rest of
> query>
>
> As you can see, it is not very secret, but I'm not sure how to deal with
> the
> key - how can I include it in a wasy so it is not put in clear text in the
> code, but without making it difficult to use the plugin?
>
> I could write a plugin for the opencaching network as well, but they also
> use
> api keys.
>
>
> For a screenshot of the plugin in action, look here in case anyone is
> interrested:
>
> http://owncloud.alweb.dk/public.php?service=files&file=/anders/files/Public/marble-
> opencaching.png
>
> http://owncloud.alweb.dk/public.php?service=files&file=/anders/files/Public/marble-
> opencaching1.png
>
> --
> Anders
> _______________________________________________
> Marble-devel mailing list
> Marble-devel at kde.org
> https://mail.kde.org/mailman/listinfo/marble-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/marble-devel/attachments/20121126/337ea5ea/attachment.html>