5 ms·
Ah, the old "too many boring bugs, let's rewrite instead of fixing them (this time in rust!)" adagio.
by sildur 6y ago
Ah, the old "too many boring bugs, let's rewrite instead of fixing them (this time in rust!)" adagio.
- nix23 6y agoNo it's whe have already sftp wich is better and whe have unfixed bugs in scp so whe throw it out. >>The scp command is a historical protocol (called rcp) which relies upon that style of argument passing and encounters expansion problems. It has proven very difficult to add "security" to the scp model. All attempts to "detect" and "prevent" anomalous argument transfers stand a great chance of breaking existing workflows. Yes, we recognize it the situation sucks. But we don't want to break the easy patterns people use scp for, until there is a commonplace replacement
- deleted 6y ago[deleted]
- sildur 6y agoThat's not better.
- nix23 6y agoI see your totally not into "let's read the article first" thing.
- adrian_b 6y agoNo, "sildur" was correct that the "sftp" protocol is not better than the "scp" protocol. Another poster described in detail the problems with the "scp" and "sftp" protocols. They have different advantages and disadvantages and neither of them can be considered a good file copy protocol.
- nix23 6y ago>It has proven very difficult to add "security" to the scp model. >>Compared to the SCP protocol, which only allows file transfers, the SFTP protocol allows for a range of operations on remote files which make it more like a remote file system protocol. https://en.wikipedia.org/wiki/SSH_File_Transfer_Protocol https://en.wikipedia.org/wiki/SSH_File_Transfer_Protocol If you want the best "JUST File-transfer prog" use nc or rsync over ssh
- tgragnato 6y agoYou are lucky that someone is working on a rewrite! If it were up to me I would have solved the problem with a nice rm -rf. Be careful what you wish for.. https://news.ycombinator.com/item?id=19520312 https://news.ycombinator.com/item?id=19520312
- sildur 6y agoDo you mean "gnome 3 lucky" or "KDE 4 lucky"?
- deleted 6y ago[deleted]
- mrighele 6y agoFrom the article: > The scp command is a historical protocol (called rcp) which relies upon that style of argument passing and encounters expansion problems. It has proven very difficult to add "security" to the scp model. All attempts to "detect" and "prevent" anomalous argument transfers stand a great chance of breaking existing workflows. Yes, we recognize it the situation sucks. But we don't want to break the easy patterns people use scp for, until there is a commonplace replacement. The problem is that in many cases those bugs are in fact the intended behavior and changing it would break backward compatibility. I think it is better to leave it as it is and move to a different tool.
- dan00 6y agoI have to say, that I enjoy using the Rust replacements for ‘grep’ and ‘find’ - ‘ripgrep’ and ‘fd’ - quite a bit. The ui of a few old unix programs isn’t the best.
- simias 6y agoYou don't make sense, this is a protocol problem, not a code problem, you can't just incrementally address the issue without breaking everything. Fixing the scp (really, rcp) protocol would incur more churn than just moving to rsync or sftp which are already well established replacements.