On 11/5/20 7:49 PM, Michael Hennebry wrote:
On Wed, 4 Nov 2020, George N. White III wrote:
On Wed, 4 Nov 2020 at 11:39, Michael Hennebry <
henne...@web.cs.ndsu.nodak.edu> wrote:
In this particular case, I'd think the client
could tell that a .BAT file was not a .c file.
Downloading 1000's
On Wed, 4 Nov 2020, George N. White III wrote:
On Wed, 4 Nov 2020 at 11:39, Michael Hennebry <
henne...@web.cs.ndsu.nodak.edu> wrote:
In this particular case, I'd think the client
could tell that a .BAT file was not a .c file.
Downloading 1000's of files resulting from some HPC calculation
On Wed, 4 Nov 2020 at 11:39, Michael Hennebry <
henne...@web.cs.ndsu.nodak.edu> wrote:
> I've not used sftp at all.
> I've only used scp when I had control at both ends.
>
> On Wed, 4 Nov 2020, George N. White III wrote:
>
> > This is due to a fundamental insecurity in the old-style SCP protocol:
I've not used sftp at all.
I've only used scp when I had control at both ends.
On Wed, 4 Nov 2020, George N. White III wrote:
This is due to a fundamental insecurity in the old-style SCP protocol: the
client sends the wildcard string (*.c) to the server, and the server sends
back a sequence of
On Mon, 2 Nov 2020, Jakub Jelen wrote:
I'm using scp: a lot to edit remote files with vim and I'm pretty sure
that many remote admins are doing the same.
So I'm wondering how this change will affect my use case scenario and if
you have considered it when moving to sftp.
That is a good
On Wed, Nov 4, 2020 at 6:34 PM George N. White III wrote:
> On Tue, 3 Nov 2020 at 12:20, Tom Horsley wrote:
>
>> On Mon, 2 Nov 2020 15:44:39 +0100
>> Jakub Jelen wrote:
>>
>> > Do you have something against this?
>>
>> I use the scp command all the time, if the command is still there
>> I don't
On Tue, 3 Nov 2020 at 12:20, Tom Horsley wrote:
> On Mon, 2 Nov 2020 15:44:39 +0100
> Jakub Jelen wrote:
>
> > Do you have something against this?
>
> I use the scp command all the time, if the command is still there
> I don't care if it does something different under the hood.
> I suppose I coul
On Mon, 2 Nov 2020 15:44:39 +0100
Jakub Jelen wrote:
> Do you have something against this?
I use the scp command all the time, if the command is still there
I don't care if it does something different under the hood.
I suppose I could always use rsync instead of the command
disappeared.
_
On 11/2/20 4:57 PM, francis.montag...@inria.fr wrote:
Hi.
On Mon, 02 Nov 2020 15:44:39 +0100 Jakub Jelen wrote:
Is this something you would like to see in Fedora soon?
No. I prefer a lot to use rsync, because scp:
- has no dry-run mode
- is not incremental
- follows symlinks when use
On 11/2/20 5:13 PM, Joe Wulf via users wrote:
Improving the state of security for SCP is overdue. Like you've said,
Jakub, the code just hasn't been worked on in a long time, nor been
well-maintained.
I am curious to better understand if the scp binary, as implemented, has
security-related i
On 11/2/20 4:09 PM, Ian Pilcher wrote:
On 11/2/20 8:44 AM, Jakub Jelen wrote:
I am looking for any kind of feedback from the idea through the
usability, implementation. Is this something you would like to see in
Fedora soon? Do you have something against this? Is your use case
missing?
What
Joe makes a good point re: hardening. We ( a very large IT company, top 10
in size) are mandated to have sftp turned off except on specific servers.
As such, we use scp extensively. It would be better off for everybody
involved to "fix" scp's shortcomings as opposed to expecting the world at
larg
Improving the state of security for SCP is overdue. Like you've said, Jakub,
the code just hasn't been worked on in a long time, nor been well-maintained.
I am curious to better understand if the scp binary, as implemented, has
security-related issues of concern here (along with old code), or i
On Mon, Nov 02, 2020 at 03:44:39PM +0100, Jakub Jelen wrote:
> Over the last years, there were several issues in the SCP protocol, which
> lead us into discussions if we can get rid of it in upstream [1]. Most of
> the voices there said that they use SCP mostly for simple ad-hoc copy and
> because
On 02/11/2020 15:44, Jakub Jelen wrote:
Hi Fedora users!
Over the last years, there were several issues in the SCP protocol, which lead
us into discussions if we can get rid of it in upstream [1]. Most of the voices
there said that they use SCP mostly for simple ad-hoc copy and because sftp
u
Hi.
On Mon, 02 Nov 2020 15:44:39 +0100 Jakub Jelen wrote:
> Is this something you would like to see in Fedora soon?
No. I prefer a lot to use rsync, because scp:
- has no dry-run mode
- is not incremental
- follows symlinks when used with the -r option
- has too few options: no --chown --c
On 11/2/20 4:36 PM, Kamil Dudka wrote:
On Monday, November 2, 2020 3:44:39 PM CET Jakub Jelen wrote:
Hi Fedora users!
Over the last years, there were several issues in the SCP protocol,
which lead us into discussions if we can get rid of it in upstream [1].
Most of the voices there said that th
On 11/2/20 3:57 PM, Walter Cazzola wrote:
Hi,
I don't know if and how the internet protocol scp: is related to the scp
command. But I suppose it is.
Hi,
SCP is not an internet protocol -- it is simple protocol that is used
inside of encrypted SSH session, similarly to SFTP protocol. The name
On 11/2/20 8:44 AM, Jakub Jelen wrote:
I am looking for any kind of feedback from the idea through the
usability, implementation. Is this something you would like to see in
Fedora soon? Do you have something against this? Is your use case missing?
What impact will this have on compatibility wi
Hi,
I don't know how if and how the internet protocol scp: is related to the scp
command. But I suppose it is.
I'm using scp: a lot to edit remote files with vim and I'm pretty sure that
many remote admins are doing the same.
So I'm wondering how this change will affect my use case scenario and
Hi Fedora users!
Over the last years, there were several issues in the SCP protocol,
which lead us into discussions if we can get rid of it in upstream [1].
Most of the voices there said that they use SCP mostly for simple ad-hoc
copy and because sftp utility does not provide simple interface
21 matches
Mail list logo