On Sun, Feb 22, 2015 at 10:31:08PM +, Philip Hands wrote:
It seems to me it needs something along the lines of this near the -X
and -Y options' documentation:
***WARNING***
-Y option is basically irrelevant as the result of Debian
shipping a modified binary that treats -X
On Wed, Aug 19, 2015 at 11:51:36PM +0200, Christoph Anton Mitterer wrote:
On Wed, 2015-08-19 at 20:59 +0100, Colin Watson wrote:
Run xterm and try to select something, bam, your xterm crashes with
BadAccess.
Which means that people would typically note quite quickly that they
need to open
Colin Watson cjwat...@debian.org writes:
I tried some experiments with ForwardX11Trusted=no today, and frankly,
it doesn't even pass the laugh test for usability. Run xterm and try to
select something, bam, your xterm crashes with BadAccess. Now, sure,
that's telling me that the X SECURITY
Le mercredi 19 août 2015 à 20:59 +0100, Colin Watson a écrit :
debian-devel, debian-x, do you think that it's at all realistic to
expect clients to be fixed to handle such failures rather more
gracefully?
Well, I guess it is possible, if we were to introduce appropriate error
checking in
On Wed, 2015-08-19 at 20:59 +0100, Colin Watson wrote:
I tried some experiments with ForwardX11Trusted=no today, and
frankly,
it doesn't even pass the laugh test for usability.
Well but it's ssh Secure Shell - and not ush (Usability Shell).
So the defaults should be always the secure ones, and
On Sun, 2015-02-22 at 22:31 +, Philip Hands wrote:
The primary thrust of this report seems to be about the modification
From upstream of the default for ForwardX11Trusted to now be set.
Well my mean reason, was actually more that Debian really changes some
default values in the program
Hi,
This bug got mentioned on the openssh-unix-dev mailing list yesterday,
so I had a look.
The primary thrust of this report seems to be about the modification
From upstream of the default for ForwardX11Trusted to now be set.
Frankly, I'm astonished by this -- I have been aware of -Y since it
7 matches
Mail list logo
