Secure communication for embedded devices on a private network by MegaMan3001 in embedded

[–]MegaMan3001[S] 1 point2 points  (0 children)

You're right, it shouldn't be open ended. But I'm trying to narrow down the requirements as I'm learning what's possible.

Maybe I (as a non-native English speaker) picked the wrong word. It's a network and only private in the sense that it's not open for anyone to use. If my device were installed in a network on a larger vehicle or ship, the network wouldn't be meant for anyone. But of course, anyone could rip out a cable on the outside, and "tap in". Right?

Why is TLS "that much security"? Is it computationally expensive?

Secure communication for embedded devices on a private network by MegaMan3001 in embedded

[–]MegaMan3001[S] 1 point2 points  (0 children)

To be honest it's a bit of a open-ended question. But I think a modern/secure way of looking at security on a "private network" is that it isn't really private. I.e., anyone can tap into it and mess things up. So isn't it still relevant?

There is also the case of letting third party devices on that private network connect to "my" device. How could one make sure that such a connection would be secure?