Re:MCP Security Vulnerabilities and Attack Vectors
by iotku on Saturday July 19, 2025 @05:49PM
(#44619747)
I do love the joke, but it is worth remembering as well that all of those S were to a certain extent afterthoughts to fix otherwise insecure protocols.
Given how old FTP and HTTP are it's fairly understandable that they weren't initially designed with security in mind, but I think it's valid to question why we're still designing insecure systems in 2025.
Re:MCP Security Vulnerabilities and Attack Vectors
by amitksingh1490 on Saturday July 19, 2025 @07:25PM
(#44620439)
Totally agree, If we have made a mistakes in past we must have learnt from it and when designing a standard specially with AI where the outcome is non deterministic we got be more careful.
Re:MCP Security Vulnerabilities and Attack Vectors
by dotancohen on Sunday July 20, 2025 @02:38AM
(#44622528)
That's quite the point of the joke. Even today, we still design things that will need an S tacked onto it at some point in the future.
The S in SSH?
The S in HTTPS?
The S in MCP?
All stand for the same thing!
I remember when this joke was first applied to IoT.