1. Forum
  2. FSXNet
  3. FSX CRY

  • TLS

    From Avon@21:1/101 to All on Mon Dec 23 15:56:57 2019
    I've been reading and watching some presentations about TLS and the
    differences between v1.2 and v1.3 and how the handshakes occur between client and server etc.

    The differences are really interesting in terms of perfect forward secrecy
    and which cipher suites are in and which are not etc.

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Argos@21:1/203 to Avon on Mon Dec 23 13:01:32 2019

    I've been reading and watching some presentations about TLS and the differences between v1.2 and v1.3 and how the handshakes occur between client and server etc.

    The differences are really interesting in terms of perfect forward
    secrecy and which cipher suites are in and which are not etc.


    to Chime on to this .. Microsoft and most industry mail transport has abandon TLS v1.0 and 1.2. Currently Office Exchange 365 is running TLS 2.0

    ---

    Rocket Town BBS - Telnet: rtbbs.ddns.net
    fsxNET: 21:1/203 FidoNET:1:135/383 - Titusville, FL. NASA SPACE Coast

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Rocket Town BBS (21:1/203)
  • From Avon@21:1/101 to Argos on Tue Dec 24 16:08:20 2019
    On 23 Dec 2019 at 01:01p, Argos pondered and said...

    to Chime on to this .. Microsoft and most industry mail transport has abandon TLS v1.0 and 1.2. Currently Office Exchange 365 is running TLS
    2.0

    Interesting thanks for sharing ... yeah, I've only just started to read up on it etc. but it seemed like around the start on this year TLS v1.2 was the
    main version being used but the impression I got was that v1.3 was now
    adopted by by IETF in RFC 8446 and was being rolled out ...

    2.0 I have not even come across yet... but I am n00b at all of this :)

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Al@21:4/106 to Avon on Tue Dec 24 01:03:28 2019
    to Chime on to this .. Microsoft and most industry mail
    transport has abandon TLS v1.0 and 1.2. Currently Office
    Exchange 365 is running TLS 2.0

    Interesting thanks for sharing ... yeah, I've only just started to
    read up on it etc. but it seemed like around the start on this year
    TLS v1.2 was the main version being used but the impression I got
    was that v1.3 was now adopted by by IETF in RFC 8446 and was being
    rolled out ...

    TLS 1.3 is the current version of TLS everyone is working with these days
    They were hoping folks would have 1.3 implemented Jan 1, 2020. I'm not
    sure if that'll happen though.

    This Microsoft TLS 2.0 must be Microsoft's in house TLS, hopefully it
    supports TLS 1.3. I know their web browsers IE and Edge don't seem to
    support it yet, but then Microsoft has always had a way of just doing
    their own thing.

    Ttyl :-),
    Al

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From Avon@21:1/101 to Al on Thu Dec 26 10:04:32 2019
    On 24 Dec 2019 at 01:03a, Al pondered and said...

    TLS 1.3 is the current version of TLS everyone is working with these days They were hoping folks would have 1.3 implemented Jan 1, 2020. I'm not sure if that'll happen though.

    I'm not sure 'everyone' is... isn't half the battle trying to get people to shift to the latest standard? :)

    This Microsoft TLS 2.0 must be Microsoft's in house TLS, hopefully it supports TLS 1.3. I know their web browsers IE and Edge don't seem to support it yet, but then Microsoft has always had a way of just doing their own thing.

    I don't know, like Sgt Schultz says .. I know noothingg.... nooothhinggg...

    :)

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Al@21:4/106 to Avon on Wed Dec 25 16:18:44 2019
    I'm not sure 'everyone' is... isn't half the battle trying to get
    people to shift to the latest standard? :)

    Yes, different organizations have different reasons for doing what they
    do. TLS 1.3 is only a year old but it's the target today. AFAIK.

    This Microsoft TLS 2.0 must be Microsoft's in house TLS,
    hopefully it supports TLS 1.3. I know their web browsers IE
    and Edge don't seem to support it yet, but then Microsoft has
    always had a way of just doing their own thing.

    I don't know, like Sgt Schultz says .. I know noothingg.... nooothhinggg...

    Neither do I actually, I just find TLS 2.0 interesting, that's the first
    I have heard of it. It's likely closed source so we in the internet
    community may never know what it is, or need to know if it's used in
    house.

    Ttyl :-),
    Al

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)