Earlier quoted context omitted.
Yes, but the packet replay protection is due to the sequence number of the packet that happens after the session is established. BTW, our technology uses pre-shared keys.
> Yes, but the packet replay protection is due to the sequence number of the packet that happens after the session is established. The TLS does not use pre-shared keys. Instead, every time a client establishes a new connection, there is a "key exchange" phase. Here is a simplified explanation: 1. client generates a random number, does some math on it, encrypts with server's certifcate, and sends to server; 2. server…
ControlMQ – Secure communications for control system applications
31–34 of 34 posts
Re: ControlMQ – Secure communications for control system applications
#32Earlier quoted context omitted.
> ... built a secure messaging system using the principles mentioned above. > This has so far shown itself to be highly successful. What do you mean by this? Can a system be "highly successful" at being secure without having been targeted, or have you actually hired testers and/or auditors to attack/study the system?
Well, you saw the quotes on the website, they did hire the best pentesters! For example, one pentester ran "nmap", which did not find any ports open, so he said "There doesn't seem to be an available service to attack." This means the system is SUPER SECURE.
Re: ControlMQ – Secure communications for control system applications
#33Earlier quoted context omitted.
> Yes, but the packet replay protection is due to the sequence number of the packet that happens after the session is established. The TLS does not use pre-shared keys. Instead, every time a client establishes a new connection, there is a "key exchange" phase. Here is a simplified explanation: 1. client generates a random number, does some math on it, encrypts with server's certifcate, and sends to server; 2. server…
Yes, I agree that TLS provides replay protection on a suitably reliable network. Don’t know about DTLS or QUIC but I will look further into these. We didn’t really look to much at TCP and TLS, etc. because early on we made design decisions to have components adopt an autonomous posture and work with unreliable networks, as can often be the case for controls. That led us to reject all connection based network protocol…
Can you PLEASE tell me how unreliable network allows TLS replay (or DTLS replay, or QUIC replay -- they all do key negotiation)
Re: ControlMQ – Secure communications for control system applications
#34Earlier quoted context omitted.
Well, you saw the quotes on the website, they did hire the best pentesters! For example, one pentester ran "nmap", which did not find any ports open, so he said "There doesn't seem to be an available service to attack." This means the system is SUPER SECURE.
These were just a selection of quotes that looked good on the web site, particularly the "GREAT JOB!" quote. That's kind of nice to see.