Thursday, 4 July 2019

TLS Security NS 3.8

Little more than a week ago I posted about the Security Certs for NS 3.8. I was not aware at that time that NS 3.9 was already available (I was using a link provided for D/L of 3.8). Since there has been other bugs/problems, I thought to provide the actual results. The location of this Qualys Client Test is

https://www.ssllabs.com/ssltest/viewMyClient.html

Presuming the Certs are within NS 3.8, it would appear that the "weak" certs be removed for added security. I did not receive an answer to the question if the certs are tapped from the Distribution or the Browser. So, here are the results...


Protocols
TLS 1.3 No
TLS 1.2 Yes*
TLS 1.1 Yes*
TLS 1.0 Yes*
SSL 3 Yes*
SSL 2 No

Cipher Suites (in order of preference)
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030) Forward Secrecy 256
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c) Forward Secrecy 256
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028) WEAK 256
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (0xc024) WEAK 256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f) Forward Secrecy 128
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b) Forward Secrecy 128
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027) WEAK 128
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (0xc023) WEAK 128
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x9f) Forward Secrecy 256
TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 (0x6b) WEAK 256
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x9e) Forward Secrecy 128
TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 (0x67) WEAK 128
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) WEAK 256
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a) WEAK 256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) WEAK 128
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009) WEAK 128
TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x39) WEAK 256
TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x33) WEAK 128
TLS_RSA_WITH_AES_128_CBC_SHA (0x2f) WEAK 128
TLS_EMPTY_RENEGOTIATION_INFO_SCSV (0xff) -
(1) When a browser supports SSL 2, its SSL 2-only suites are shown only on the very first connection to this site. To see the suites, close all browser windows, then open this exact page directly. Don't refresh.

Protocol Details
Server Name Indication (SNI) Yes
Secure Renegotiation Yes
TLS compression No
Session tickets Yes
OCSP stapling No
Signature algorithms SHA512/RSA, SHA512/DSA, SHA512/ECDSA, SHA384/RSA, SHA384/DSA, SHA384/ECDSA, SHA256/RSA, SHA256/DSA, SHA256/ECDSA, SHA224/RSA, SHA224/DSA, SHA224/ECDSA, SHA1/RSA, SHA1/DSA, SHA1/ECDSA
Named Groups secp256r1, secp521r1, brainpoolP512r1, brainpoolP384r1, secp384r1, brainpoolP256r1, secp256k1, sect571r1, sect571k1, sect409k1, sect409r1, sect283k1, sect283r1
Next Protocol Negotiation Yes
Application Layer Protocol Negotiation No
SSL 2 handshake compatibility No


Regards
Paul S. in CT

Tuesday, 2 July 2019

Re: 3.9 Release

On 2 Jul 2019 Geoffrey Baxendale <thebears@onetel.com> wrote:

> In message <20190702150402.GN14758@kyllikki.org>
> Vincent Sanders <vince@netsurf-browser.org> wrote:

>>> I had intended to release before now but testing kept revealing
>>> issues, however I now believe that we are ready for a 3.9 release
>>> candidate on Sunday June 16th with the actual release on Saturday June
>>> 22nd unless critical bugs are discovered.
>>>
>>
>> Well it seems a lot of bugs decided to make themselves known right at
>> the last moment and despite some hard work from John-Mark, Daniel,
>> Michael and myself we have simply not managed to get the browser as
>> stable as I wanted for a release.
>>
>> I will try again to release sometime this week but again I ask for
>> some *feedback* . I have had literally two replies (one should have
>> been a bug report but at least it was activity) and I hope there are
>> more than two people other than the developers using the CI builds!
>>
> I keep pretty much upto date with the builds and haven't seen any
> problems recently. Usually it's JavaScript issues, such as buttons
> not working, which send me to the dark side.

> Many thanks for all the effort.

+1

Best wishes,

Peter.

--
Peter Young (zfc Au) and family
Prestbury, Cheltenham, Glos. GL52, England
http://pnyoung.orpheusweb.co.uk
pnyoung@ormail.co.uk

Re: 3.9 Release

In message <20190702150402.GN14758@kyllikki.org>
Vincent Sanders <vince@netsurf-browser.org> wrote:

> > I had intended to release before now but testing kept revealing
> > issues, however I now believe that we are ready for a 3.9 release
> > candidate on Sunday June 16th with the actual release on Saturday June
> > 22nd unless critical bugs are discovered.
> >
>
> Well it seems a lot of bugs decided to make themselves known right at
> the last moment and despite some hard work from John-Mark, Daniel,
> Michael and myself we have simply not managed to get the browser as
> stable as I wanted for a release.
>
> I will try again to release sometime this week but again I ask for
> some *feedback* . I have had literally two replies (one should have
> been a bug report but at least it was activity) and I hope there are
> more than two people other than the developers using the CI builds!
>
I keep pretty much upto date with the builds and haven't seen any
problems recently. Usually it's JavaScript issues, such as buttons
not working, which send me to the dark side.

Many thanks for all the effort.

TTFN
--
Geoff. Baxendale, Darwen, Lancashire.
Using Elesar Titanium.
Oxymoron of the day: "Microsoft Works"

Re: 3.9 Release

In message <20190702150402.GN14758@kyllikki.org>
Vincent Sanders <vince@netsurf-browser.org> wrote:


>I will try again to release sometime this week but again I ask for
>some *feedback* . I have had literally two replies (one should have
>been a bug report but at least it was activity) and I hope there are
>more than two people other than the developers using the CI builds!

I use the CI builds. I update NetSurf to the latest build as part
of a regular routine when I fire up RISC OS (RO 5.24 on rpi3b).
I use Chrome under Rasbpian for reaching parts of the internet
that NetSurf cannot cope with. But the more that NetSurf can do
the better.

I am not clear what feedback would be useful to you. Every now and
then I see a message saying that some piece of layout does not
work on some site, and sometimes out of curiosity I browse the
site with NetSurf to see if my version does the same.

How often are the Development Progress pages updated? It is particularly
useful to know what CSS works and what does not. But I am aware that
you must be having a difficult time with lack of manpower, and I
am reluctant to pester you with trivia that might take precious time
to respond to.

--
Gavin Wraith (gavin@wra1th.plus.com)
Home page: http://www.wra1th.plus.com/

Re: Atari CI builds

> I can report that the Atari CI builds are working nicely again.> A big thanks to the guys on atari-forum.org and all the Netsurf>
developers and contributors.>>> Peter I second that. Big thanks from my
side to all people involved. Netsurfis the only browser I am using
regularly with my falcon and I am gladthat the ATARI versions are still
supported. Good work!
patjomki

Re: Atari CI builds

> I can report that the Atari CI builds are working nicely again.
>
> A big thanks to the guys on atari-forum.org and all the Netsurf
> developers and contributors.
>
>
> Peter

I second that. Big thanks from my side to all people involved. Netsurf
is the only browser I am using regularly with my falcon and I am glad
that the ATARI versions are still supported. Good work!

patjomki

Re: 3.9 Release

> I had intended to release before now but testing kept revealing
> issues, however I now believe that we are ready for a 3.9 release
> candidate on Sunday June 16th with the actual release on Saturday June
> 22nd unless critical bugs are discovered.
>

Well it seems a lot of bugs decided to make themselves known right at
the last moment and despite some hard work from John-Mark, Daniel,
Michael and myself we have simply not managed to get the browser as
stable as I wanted for a release.

I will try again to release sometime this week but again I ask for
some *feedback* . I have had literally two replies (one should have
been a bug report but at least it was activity) and I hope there are
more than two people other than the developers using the CI builds!

--
Regards Vincent