On 2015-08-21 11:35:08 +0200, bgr...@toplitzer.net wrote:
> According to [1] special crafted filenames containing control characters
> can cause scp to execute commands in the current shell.
It cannot execute arbitrary shell commands (except if the terminal has
an extension to do that via escape s
On Fri, Aug 21, 2015 at 11:35:08AM +0200, bgr...@toplitzer.net wrote:
> According to [1] special crafted filenames containing control characters
> can cause scp to execute commands in the current shell.
For clarity, that's not what the upstream bug report says. This is
*not* a matter of scp execu
Hi,
On Fri, Aug 21, 2015 at 11:35:08AM +0200, bgr...@toplitzer.net wrote:
> Source: openssh
> Severity: important
> Tags: upstream security
>
>
> According to [1] special crafted filenames containing control characters
> can cause scp to execute commands in the current shell. This works also on
Source: openssh
Severity: important
Tags: upstream security
According to [1] special crafted filenames containing control characters
can cause scp to execute commands in the current shell. This works also on
copying files from remote (potential untrusted) servers
to local client.
this works:
rem
4 matches
Mail list logo
