<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div><br></div><div><br></div><div><br></div><div>6 paź 2023, 13:57 od traut@gmx.de:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>On 23-10-06 13:41, Tom Hughes wrote:<br></div><blockquote><div>On 06/10/2023 12:12, Martin Trautmann wrote:<br></div><blockquote><div>On 23-10-06 12:55, Tom Hughes via talk wrote:<br></div><blockquote><div>No it was released in June 2020. October 2021 was the last<br></div><div>security patches.<br></div><div><br></div><div>To answer the original question there have been any deliberate<br></div><div>changes that I know but given the error it's entirely possible<br></div><div>that FF has fixed something in what CSP rules it checks for what<br></div><div>requests.<br></div></blockquote><div><br></div><div>I doubt that since FF did not see any changes here for some time,<br></div><div>unfortunately. So it appears to be from an OSM editor's change.<br></div></blockquote><div><br></div><div>I think you misunderstood what I was saying.<br></div><div><br></div><div>My hypothesis is that something in iD has started using a data URL<br></div><div>where it didn't before and that is triggering a latent bug in your<br></div><div>version of firefox (in that it is checking that URL against the<br></div><div>media-src rule in our security policy) while newer versions of<br></div><div>firefox are checking it against some other rule.<br></div></blockquote><div><br></div><div>Thanks - that does clarify the issue. But as you say, "something in iD<br></div><div>has started" - so it's a change within OSM's editor, which does break<br></div><div>old systems.<br></div><div><br></div><div>Maybe it's a reasonable and necessary change for ID - but maybe it isn't!<br></div><div><br></div><blockquote><div>Without knowing more about which load is being blocked it's not<br></div><div>really possible to say more and I might be totally wrong as I'm<br></div><div>just guessing from the limited information available.<br></div></blockquote><div><br></div><div><br></div><div>I agree - but I don't know where else to report this malfunction. It's<br></div><div>obvious that one part of this bug is an outdated FF version. But that<br></div><div>does not mean that those have to be excluded.<br></div><div><br></div></blockquote><div dir="auto">If you track down which exact change <br></div><div dir="auto">changed things then maybe it would make sense to report it<br></div><div dir="auto">(You can try older iD versions and revisions)<br></div><div dir="auto"><br></div><div dir="auto">In general I would strongly recommend<br></div><div dir="auto">not using such ancient and insecure browser.<br></div><div dir="auto"><br></div><div dir="auto">You can setup dual booting, get new see<br></div><div dir="auto">computer, move that setup to VM, replace that software...</div> </body>
</html>