Addressing Visibility Challenges with TLS 1.3 - The NCCoE at NIST recognizes the challenges associated with compliance, operations, and security when enterprises employ encrypted protocols, in particular Transport Layer Security (TLS) 1.3, in their data centers. nccoe.nist.gov/projects/b…
πŸ‘︎ 3
πŸ“°︎ r/blueteamsec
πŸ’¬︎
πŸ‘€︎ u/digicat
πŸ“…︎ Feb 27
🚨︎ report
Transport Layer Security (TLS) - Computerphile youtube.com/watch?v=0TLDT…
πŸ‘︎ 6
πŸ“°︎ r/Computerphile
πŸ’¬︎
πŸ“…︎ Oct 23 2020
🚨︎ report
End-to-End Transport Layer Security on Hyperledger Besu 1.4 media.consensys.net/end-t…
πŸ‘︎ 20
πŸ“°︎ r/ethfinance
πŸ’¬︎
πŸ‘€︎ u/ethfinance
πŸ“…︎ Mar 26 2020
🚨︎ report
End-to-End Transport Layer Security on Hyperledger Besu 1.4 pegasys.tech/end-to-end-t…
πŸ‘︎ 16
πŸ“°︎ r/ethfinance
πŸ’¬︎
πŸ‘€︎ u/ethfinance
πŸ“…︎ Mar 13 2020
🚨︎ report
Transport Layer Security Matrix

My organization is doing a poor job at managing TLS. Some systems are using legacy protocols and no one is taking responsibility for the mess. I am trying to build a matrix that outlines all the different areas of responsibilities to ensure modern TLS (1.2+) protocols are used across all systems.

Does anyone know of a matrix or RACI chart that exists already for something like this? Is it as simple as:

  1. Make sure TLS 1.2 is available on the host system and configured as the OS system default
  2. Make sure secure cipher suites are available and configured in a secure order preference
  3. Make sure each system has trusted certificates deployed to the host
  4. Make sure application code is written to use OS system default wherever possible, and only hardcoding 1.2 or 1.3 when the default OS version could not be used
  5. Continue to renew certificates before they expire
  6. Update default TLS version as new protocols become available
πŸ‘︎ 2
πŸ“°︎ r/crypto
πŸ’¬︎
πŸ‘€︎ u/TechnologyAnimal
πŸ“…︎ Apr 08 2020
🚨︎ report
RFC 8446 - The Transport Layer Security (TLS) Protocol Version 1.3 tools.ietf.org/html/rfc84…
πŸ‘︎ 545
πŸ“°︎ r/programming
πŸ’¬︎
πŸ‘€︎ u/dochtman
πŸ“…︎ Aug 11 2018
🚨︎ report
RFC 8446 - The Transport Layer Security (TLS) Protocol Version 1.3 tools.ietf.org/html/rfc84…
πŸ‘︎ 47
πŸ“°︎ r/linux
πŸ’¬︎
πŸ‘€︎ u/Charwinger21
πŸ“…︎ Aug 13 2018
🚨︎ report
COTI’s exchange will be designed to be highly secure & fault-tolerant. It will implement multi-tiered security architecture that will limit attack vectors and ingresses. Traffic will be encrypted using Transport Layer Security and data-at-rest will be secured with AES-256 encryption.
πŸ‘︎ 4
πŸ“°︎ r/cotinetwork
πŸ’¬︎
πŸ‘€︎ u/CyberTemek
πŸ“…︎ Jan 21 2018
🚨︎ report
The Transport Layer Security (TLS) Extension to Support Code Execution: draft-tls-yolo-rce mailarchive.ietf.org/arch…
πŸ‘︎ 60
πŸ“°︎ r/crypto
πŸ’¬︎
πŸ‘€︎ u/bascule
πŸ“…︎ Apr 01 2017
🚨︎ report
Technology standards: Understanding Transport Layer Security hpe.com/us/en/insights/ar…
πŸ‘︎ 5
πŸ“°︎ r/webdev
πŸ’¬︎
πŸ‘€︎ u/yourbasicgeek
πŸ“…︎ Dec 18 2018
🚨︎ report
[ENG] RFC 8446 - The Transport Layer Security (TLS) Protocol Version 1.3 tools.ietf.org/html/rfc84…
πŸ‘︎ 4
πŸ“°︎ r/ItalyInformatica
πŸ’¬︎
πŸ‘€︎ u/michell9
πŸ“…︎ Aug 15 2018
🚨︎ report
The Transport Layer Security (TLS) Protocol Version 1.3 draft tools.ietf.org/html/draft…
πŸ‘︎ 99
πŸ“°︎ r/netsec
πŸ’¬︎
πŸ‘€︎ u/bobdudley
πŸ“…︎ Apr 19 2014
🚨︎ report
Protocol Action: 'The Transport Layer Security (TLS) Protocol Version 1.3' to Proposed Standard (draft-ietf-tls-tls13-28.txt) ietf.org/mail-archive/web…
πŸ‘︎ 23
πŸ“°︎ r/programming
πŸ’¬︎
πŸ‘€︎ u/cielpy
πŸ“…︎ Mar 24 2018
🚨︎ report
Google's Application Layer Transport Security cloud.google.com/security…
πŸ‘︎ 33
πŸ“°︎ r/crypto
πŸ’¬︎
πŸ‘€︎ u/dchestnykh
πŸ“…︎ Dec 29 2017
🚨︎ report
RFC 7905 - ChaCha20-Poly1305 Cipher Suites for Transport Layer Security (TLS) tools.ietf.org/html/rfc79…
πŸ‘︎ 30
πŸ“°︎ r/crypto
πŸ’¬︎
πŸ‘€︎ u/johnmountain
πŸ“…︎ Jun 23 2016
🚨︎ report
The Transport Layer Security (TLS) Protocol Version 1.3 tools.ietf.org/html/rfc84…
πŸ‘︎ 2
πŸ“°︎ r/hackernews
πŸ’¬︎
πŸ‘€︎ u/qznc_bot
πŸ“…︎ Aug 11 2018
🚨︎ report
KTLS: Linux Kernel Transport Layer Security netdevconf.org/1.2/papers…
πŸ‘︎ 18
πŸ“°︎ r/linux
πŸ’¬︎
πŸ‘€︎ u/agumonkey
πŸ“…︎ Sep 03 2017
🚨︎ report
50331715 security package error occurred in the transport layer

updated my windows 10 workstation to 1709 recently. I get this in mRenoteNG all the time now.


WarningMsg 50331715 Your computer can't connect to the remote computer because a security package error occurred in the transport layer. Retry the connection or contact your network administrator for assistance.

I have several different servers, all with Gateways defined and working up until now, and none of them work. If I put the exact same settings into RDC manually, they work fine. I cleared the credential cache in RDC as well, no change.

What am I missing here?

πŸ‘︎ 2
πŸ“°︎ r/mRemoteNG
πŸ’¬︎
πŸ‘€︎ u/lkeltner
πŸ“…︎ Mar 26 2018
🚨︎ report

Please note that this site uses cookies to personalise content and adverts, to provide social media features, and to analyse web traffic. Click here for more information.