Re^2: arp and mac addresses

And the only way to do that is to have a unique identifier on the remote (Linux) box which you can check in a secure way, i.e. in a way that can't be snooped or spoofed. So you need to encrypt that identifier exchange as well, which is a lot of work, only ssh already does it for you.

Inventing your own secure transmission channels is always a bad idea unless you really know what you're doing.

Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian W. Kernighan

Comment on Re^2: arp and mac addresses

Replies are listed 'Best First'.
Re^3: arp and mac addresses by fluffyvoidwarrior (Monk) on Dec 19, 2005 at 17:15 UTC
yes, I had in mind inventing my own secure transmission thingy but it started to get a bit sticky - using a unique identifier on the linux box as you suggest. Like you say a bit of a pain. It seems the consensus is that ssh is the way to go then and arp and MAC addresses isn't - even if my data is encrypted I don't want it poked at by just anyone. Thanks everyone. 2 mins of monkly advice is worth 2 weeks of my arsing about.	[reply]

Replies are listed 'Best First'.

Re^3: arp and mac addresses
by fluffyvoidwarrior (Monk) on Dec 19, 2005 at 17:15 UTC

yes, I had in mind inventing my own secure transmission thingy but it started to get a bit sticky - using a unique identifier on the linux box as you suggest. Like you say a bit of a pain. It seems the consensus is that ssh is the way to go then and arp and MAC addresses isn't - even if my data is encrypted I don't want it poked at by just anyone. Thanks everyone. 2 mins of monkly advice is worth 2 weeks of my arsing about.

[reply]