11:26 a.m.
All the NetSurf web services [1] are now securely accessible. This has
been made possible by the lets encrypt service [2] providing no cost
certificates and pepperfish proving the infrastructure to manage them.
We are making this change to ensure our users privacy is protected.
The NetSurf project collects no personally identifying data
about users of our web services except that required to provide the
service [3] and we do not believe third parties should be able to
intercept such information either.
Daniel Silverstone and myself have now updated all the NetSurf
infrastructure to make https available. It is intended that after a
short stabilisation period that web server and wiki will have HSTS [4]
enabled. Once this occurs only encrypted connections will be
available to NetSurf services.
Please ensure there are no issues with the secure sites (let us know
if there are!) and update any links you may have in external
documents.
[1] https://www.netsurf-browser.org/
https://wiki.netsurf-browser.org/
https://bugs.netsurf-browser.org/
https://ci.netsurf-browser.org/
[2] https://letsencrypt.org/
[3] The bugs interface requires a user identifier and email address
which are required to use the service and we do not use
that data for any other purpose than tracking bugs.
[4] https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security
--
Regards Vincent
http://www.kyllikki.org/
9:03 p.m.
In message <20180718092657.GC8426(a)kyllikki.org>
Vincent Sanders <vince(a)netsurf-browser.org> wrote:
All the NetSurf web services [1] are now securely accessible. This
has
been made possible by the lets encrypt service [2] providing no cost
certificates and pepperfish proving the infrastructure to manage them.
We are making this change to ensure our users privacy is protected.
The NetSurf project collects no personally identifying data
about users of our web services except that required to provide the
service [3] and we do not believe third parties should be able to
intercept such information either.
Daniel Silverstone and myself have now updated all the NetSurf
infrastructure to make https available. It is intended that after a
short stabilisation period that web server and wiki will have HSTS [4]
enabled. Once this occurs only encrypted connections will be
available to NetSurf services.
Please ensure there are no issues with the secure sites (let us know
if there are!) and update any links you may have in external
documents.
[1] https://www.netsurf-browser.org/
https://wiki.netsurf-browser.org/
https://bugs.netsurf-browser.org/
https://ci.netsurf-browser.org/
[2] https://letsencrypt.org/
[3] The bugs interface requires a user identifier and email address
which are required to use the service and we do not use
that data for any other purpose than tracking bugs.
[4] https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security
Left-click on the NS icon opens file:///NetSurf:/Resources/en/welcome.html
whose links are entirely http rather then https, AFAICS. Is this what
you intend?
Also I notice that the !Fetch_NS app no longer works, complaining of
an incorrectly formatted filename at line 24. Probably not your
problem, but I struggle to see how it works and thus how the error
occurs. Help would be appreciated!
Dave
9:32 p.m.
In article <921e311a57.DaveMeUK(a)my.inbox.com>,
David Higton <dave(a)davehigton.me.uk> wrote:
Also I notice that the !Fetch_NS app no longer works, complaining of
an incorrectly formatted filename at line 24. Probably not your
problem, but I struggle to see how it works and thus how the error
occurs. Help would be appreciated!
There's a thread and solution on the c.s.apps newsgroup. Fetch_NS.
Chris Johnson suggested and Frank put it in a form that even idiots like
me could eventually understand, with a tweak to the Fetch_NS settings file.
You need to view the thread to get the whole picture.
Dave
--
Dave Triffid
9:38 p.m.
In article <921e311a57.DaveMeUK(a)my.inbox.com>,
David Higton <dave(a)davehigton.me.uk> wrote:
Also I notice that the !Fetch_NS app no longer works, complaining of
an incorrectly formatted filename at line 24. Probably not your
problem, but I struggle to see how it works and thus how the error
occurs. Help would be appreciated!
You have to have a recent version of wget that understands https and
change the command options when using wget. There was a recent thread
in comp.sys.acorn.apps where this arose. I suggested using the option
--no-check-certificate
which works around the certificate check.
I think Frank has now suggested the changes to be made to !Fetch_NS
to make it function again.
--
Chris Johnson
Edinburgh
11:35 a.m.
On Thu, Jul 19, 2018 at 08:38:52PM +0100, cj wrote:
In article <921e311a57.DaveMeUK(a)my.inbox.com>,
David Higton <dave(a)davehigton.me.uk> wrote:
> Also I notice that the !Fetch_NS app no longer works, complaining of
> an incorrectly formatted filename at line 24. Probably not your
> problem, but I struggle to see how it works and thus how the error
> occurs. Help would be appreciated!
You have to have a recent version of wget that understands https and
change the command options when using wget. There was a recent thread
in comp.sys.acorn.apps where this arose. I suggested using the option
--no-check-certificate
which works around the certificate check.
Please note that this defeats the whole point of us switching to HTTPS
in the first place. A better solution would be to provide wget and
whatnot with the certificates to check. NetSurf itself ships a set of
certificates, but I'm not sure if the format is compatible. Check with
who ported wget.
B.
9:54 p.m.
In article <921e311a57.DaveMeUK(a)my.inbox.com>,
David Higton <dave(a)davehigton.me.uk> wrote:
Also I notice that the !Fetch_NS app no longer works, complaining of
an incorrectly formatted filename at line 24. Probably not your
problem, but I struggle to see how it works and thus how the error
occurs. Help would be appreciated!
See thread 'Fetch_NS' on c.s.a.apps.
Evan.
8:34 p.m.
In message <571a35c50aevan(a)ejclark.force9.co.uk>
Evan Clark <evan(a)ejclark.force9.co.uk> wrote:
In article <921e311a57.DaveMeUK(a)my.inbox.com>,
David Higton <dave(a)davehigton.me.uk> wrote:
> Also I notice that the !Fetch_NS app no longer works, complaining of
> an incorrectly formatted filename at line 24. Probably not your
> problem, but I struggle to see how it works and thus how the error
> occurs. Help would be appreciated!
See thread 'Fetch_NS' on c.s.a.apps.
My thanks to all who answered. I responded here before I saw the csa
thread.
The problem is solved for me.
Dave
1959
days inactive
1961
days old
netsurf-users@netsurf-browser.org
6 comments
6 participants
participants (6)
-
cj -
Dave Symes -
David Higton -
Evan Clark -
Rob Kendrick -
Vincent Sanders