<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2015-02-28 17:58, Jo wrote :<br>
</div>
<blockquote
cite="mid:CAJ6DwMC6Jo1ss6MGgEJ5SWPHBk8q-WCR8p2zvks-RzUqgTiprA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>It makes a connection to the website of openstreetmap and
sends your password over it. If you do that over http, all the
routers in the middle can simply see your password. Is that a
big deal? Not in itself, until somebody starts to
'impersonate' you. Making uploads that weren't yours in your
name.<br>
<br>
</div>
Jo<br>
</div>
<div class="gmail_extra"><br>
</div>
</blockquote>
I suppose you reply to me (1).<br>
The "HTTPS support in the Remote Control preferences" controls
Remote Control which, usually, happens only inside the local
computer, which is obvious if you use local ports
<a class="moz-txt-link-freetext" href="https://localhost:8112">https://localhost:8112</a> (or <a class="moz-txt-link-freetext" href="http://localhost:8111">http://localhost:8111</a>) as in Glen's or
Ruben's messages.<br>
I showed 8111 in a previous message and I show it again in more
detail, just after a control:<tt><br>
$ netstat -an | more<br>
Active Internet connections (servers and established)<br>
Proto Recv-Q Send-Q Local Address Foreign
Address State <br>
tcp6 0 0 127.0.0.1:8111
:::* LISTEN <br>
tcp6 0 0 127.0.0.1:8111
127.0.0.1:56769 TIME_WAIT </tt><br>
You see JOSM LISTENing for control connections and the TCP
connection between JOSM 8111 and Firefox 56769 ports that has just
been closed.<br>
Convinced now?<br>
<br>
Remote control could be to another computer as in wget
<a class="moz-txt-link-freetext" href="http://anotherhost:8111/">http://anotherhost:8111/</a>... but it's not what we are talking about
here and I don't think Firefox can be configured for that anyway.<br>
<br>
The "connection to the website of openstreetmap" you speak of is
controlled by Edit>Preferences>Connection...>OSM Server
URL:<br>
If you use <a class="moz-txt-link-freetext" href="https://">https://</a>... there, you get SSL encryption between JOSM
and OSM.org,<br>
if you use <a class="moz-txt-link-freetext" href="http://">http://</a>... you don't.<br>
<br>
Cheers
<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
(1) and not to Glen or Ruben like in other messages. If we replied
inline on this mailing list we would know to whom and about what
we're writing.<br>
<br>
<blockquote
cite="mid:CAJ6DwMC6Jo1ss6MGgEJ5SWPHBk8q-WCR8p2zvks-RzUqgTiprA@mail.gmail.com"
type="cite">
<div class="gmail_extra">
<div class="gmail_quote">2015-02-28 17:51 GMT+01:00 André Pirard
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:A.Pirard.Papou@gmail.com" target="_blank">A.Pirard.Papou@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>On 2015-02-28 16:57, Ruben Maes wrote :<br>
</div>
<span class="">
<blockquote type="cite">
<pre>Maybe you can circumvent the issue by doing this:
Open JOSM and make sure you have Remote Control enabled. In Firefox,
go to this address: <a moz-do-not-send="true" href="https://127.0.0.1:8112/" target="_blank">https://127.0.0.1:8112/</a>
You should get a warning screen saying "This Connection is Untrusted".
Click "I Understand the Risks" and press the "Add Exception..."
button.
A window pops up. (You can press "View" and inspect the certificate if
you like. Close the details window if you have done so.) Make sure
"Permanently store this exception" is checked and click "Confirm
Security Exception".
Now you should see a Bad Request error page because you haven't asked
JOSM to do anything ;)
This worked for me. The website still emits an alert that editing
failed, but JOSM loads the data.
Ruben</pre>
</blockquote>
</span> That's only if HTTPS support is enabled in the
Remote Control preferences.<br>
If it's not, my config, 8112 port -> unable to connect.<br>
And I conclude that the alert I receive too may be because
of trying to use<br>
closed port 8112 before using port 8111.<br>
<br>
And my question is: why enable HTTPS if it causes
problems?<br>
It encrypts information that's stays in your computer,
doesn't it?<br>
Fearing that NSA would learn the locations you load via
remote control?<br>
<br>
Cheers <br>
<span class="HOEnZb"><font color="#888888"> <br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
</font></span>
<div>
<div class="h5"> <br>
<blockquote type="cite">
<pre>2015-02-27 9:20 GMT+01:00 Glenn Plas <a moz-do-not-send="true" href="mailto:glenn@byte-consult.be" target="_blank"><glenn@byte-consult.be></a>:
</pre>
<blockquote type="cite">
<pre>StartSSL is a free certificate provider, and most probably firefox
doesn't have the intermediate certificate chain on board which means it
cannot verify.
That is probably the reason, although I do not see startSSL as the
certificate writer, I see rapidSSL instead. startSSL is not really a
great one to use actually for a site like this.
Apple products have the same problem with the latest GoDaddy certificates.
<a moz-do-not-send="true" href="https://www.sslshopper.com/cheapest-ssl-certificates.html" target="_blank">https://www.sslshopper.com/cheapest-ssl-certificates.html</a>
You might want to try this in firefox:<a moz-do-not-send="true" href="https://127.0.0.1:8112/" target="_blank">https://127.0.0.1:8112/</a>
<a moz-do-not-send="true" href="https://www.sslshopper.com/ssl-checker.html#hostname=https://www.openstreetmap.org" target="_blank">https://www.sslshopper.com/ssl-checker.html#hostname=https://www.openstreetmap.org</a>
And see if it gives you a chain error or not. It will work in chrome,
but it depends on the browser.
If you don't get the all-green in firefox, you just need to assemble a
chain file with the missing intermediate certificates so the browser can
validate.
Note, this heavily depends on firefox (/browser) version, I see in my FF
that it loads the intermediates fine:
Common name: RapidSSL CA
Organization: GeoTrust, Inc.
Location: US
Valid from February 19, 2010 to February 18, 2020
Serial Number: 145105 (0x236d1)
Signature Algorithm: sha1WithRSAEncryption
Issuer: GeoTrust Global CA
Common name: GeoTrust Global CA
Organization: GeoTrust Inc.
Location: US
Valid from May 20, 2002 to August 20, 2018
Serial Number: 1227750 (0x12bbe6)
Signature Algorithm: sha1WithRSAEncryption
Issuer: Equifax
Glenn
</pre>
</blockquote>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
</body>
</html>