No, I meant the tokens which would be used if authentication is done with
https and
data transmission without. Somehow these two parts have to be connected, a
token transfered
with the authentication would be one solution.
This token could be intercepted and used to send unauthenticated map
If HTTPS is ever offered we have two options (as we do now):
A third option with a non-standard auth token being generated was discussed
in this thread, and that's probably what Stefan was referring to.
I must have overlooked that. In that case I'm sorry Stefan, seems as
if _I_ was the one
- signing and checking a signature is essentally encrypting and
decrypting (CPU?), but with less data
Indeed. But as far as I know HMAC-SHA1 is reasonably quick and
shouldn't be a performance hit. Even more so because it needs to be
done only once for each 'consumer' (JOSM in this case).
-
But honestly, what would you say from a user interface perspective;
should we try and keep changesets open? What JOSM currently does is open
changeset - upload - close, for each upoad action. Some people have a
habit of uploading once every five minutes and they are perhaps annoyed
to have to
Hi,
I'm using this command line to force JOSM to use my c\OSM\JOSM\data
directory instead of the one in Documents and Settings:
java -Djosm.home=c:\OSM\JOSM\data -jar josm-latest.jar
And so far it seems to work perfectly.
Lars
___
josm-dev mailing
