Re:File Transfer with SSH, Tee, and Base64
by EvanAnderson on Thursday September 17, 2020 @05:27PM
(#24510154)
I wouldn't necessarily "dismiss" somebody, but knowing about simple tools is a proxy in my mind for experience level. I can tailor my communication appropriately when I have some idea of experience level. If I know I can't say to somebody plugged-in to my laptop directly w/ a patch cable "Give me the last two octets of your APIPA address and start listening on port 31338 piped out to a file" then I know that there are a lot of other tasks that I'll need to break down in minute detail.
Re:File Transfer with SSH, Tee, and Base64
by johnisgood on Thursday September 17, 2020 @06:29PM
(#24510756)
Okay, you are right. I would not dismiss them either for this alone, I would first perhaps ask them why they think that it is the best option, or what alternatives there are, and so forth.
> Give me the last two octets of your APIPA address
Is not APIPA Windows-only, by the way?
I can definitely give you two octets of an IP address through using awk, sed, or using C and bitwise operations. Do I pass? :D
Re:File Transfer with SSH, Tee, and Base64
by EvanAnderson on Thursday September 17, 2020 @08:49PM
(#24511785)
APIPA was standardized as IPv4LL in RFC 3927[1]. I never remember the acronym IPv4LL-- I always remember APIPA instead. It was a Microsoft construct, but it has fairly broad OS support now, to my knowledge.
For myself I have written two shell functions; nc_send and nc_recv. It uses Nmap's ncat with SSL. It uses GPG and to verify data integrity, I use b2sum. Simple, yet perfect for the task. I use it often besides scp, but of course sometimes netcat is all I need.