Displaying 20 results from an estimated 6000 matches similar to: "[Bug 1682] New: verbose log message unclear when X11 forwarding denied"
2015 Apr 17
0
[Bug 1682] verbose log message unclear when X11 forwarding denied
https://bugzilla.mindrot.org/show_bug.cgi?id=1682
Damien Miller <djm at mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned-bugs at mindrot.org |djm at mindrot.org
CC| |djm at mindrot.org,
|
2015 Apr 17
0
[Bug 1682] verbose log message unclear when X11 forwarding denied
https://bugzilla.mindrot.org/show_bug.cgi?id=1682
Damien Miller <djm at mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |2360
--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching
2015 Apr 17
0
[Bug 1682] verbose log message unclear when X11 forwarding denied
https://bugzilla.mindrot.org/show_bug.cgi?id=1682
Darren Tucker <dtucker at zip.com.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #2595|ok?(dtucker at zip.com.au) |ok+
Flags| |
--
You are receiving this mail because:
You are
2015 Apr 17
0
[Bug 1682] verbose log message unclear when X11 forwarding denied
https://bugzilla.mindrot.org/show_bug.cgi?id=1682
Damien Miller <djm at mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Damien Miller <djm at
2008 Jul 26
0
Still no joy: no X11 protocols
Hello,
I know this is likely to give me a brute force attack hit,
but the only thing anyone can accomplish by ssh-ing to my machine
is to provide me with a tunnel into your machine. So don't bother.
Anyway, my server machine is running this:
/usr/bin/ssh -X -R ${port}:localhost:22 -o BatchMode=yes \
-o StrictHostKeyChecking=no ${user}@${my_home_machine}
On my local machine:
ssh -vvv -X
2004 Apr 22
2
[Bug 851] some X11 prgs generate ``BadAtom (invalid Atom parameter)'' in X_GetProperty when using X11 forwarding
http://bugzilla.mindrot.org/show_bug.cgi?id=851
Summary: some X11 prgs generate ``BadAtom (invalid Atom
parameter)'' in X_GetProperty when using X11 forwarding
Product: Portable OpenSSH
Version: 3.8.1p1
Platform: All
OS/Version: Solaris
Status: NEW
Severity: normal
Priority: P2
2005 Apr 18
1
X11 connection rejected because of wrong authentication
Hello, I am new at ssh, think it is a simple config problem, but have not
found the error.
Wenn I connect from an client (winpc vai cygwin) to server A (hpup) the
connectionon and xlogo ist okay.
Wenn I connect from the same client to server B I got the following error
message.
The problem is only by starting xlogo, the connection via ssh to Server A+B
ist okay.
The sshd_config on server a+b is
2017 Oct 12
2
X11forwarding yes: how to debug/setup after xauth fix
On 08/10/2017 23:32, Michael Felt wrote:
> On 04/10/2017 11:07, Michael Felt wrote:
>> I do not often use X11 - but when I do I prefer to enable
>> X11forwarding, and when finished - turn it off. This is preferable,
>> imho, to having "clear" X11 processing when local - and otherwise
>> impossible when working remote.
>>
>> Working with
2004 Aug 24
1
Possible problem with hostbased protocol 1 rhosts authentication
I found this problem when working with the Suse9.1 distribution, but have
since reproduced it with a vanilla build of Openssh
(openssh-3.9p1.tar.gz). Basically I cannot get a command like this:
XXXX>ssh -vvv -1 -o "RhostsAuthentication yes" AAAA
to work. Yes the appropriate settings are in the servers sshd_config file.
Hostbased protocol 1 ssh using rhosts between computers is
2002 May 06
2
X11 forwarding does not work as normal user
We installed openssh 3.1p1 on our Solaris 2.8 machine using gcc 2.95.2. During
the installation, we modified ssh_config and sshd_config to enable X11 and
agent forwarding.
In sshd_config, we changed the following line to read:
X11Forwarding yes
In ssh_config, we changed the following two lines to read:
ForwardAgent yes
ForwardX11 yes
Both files are set to permission readable
2008 Nov 19
1
HELPA
I have a problem in ssh login without password
Systems: vmware-centos 5.2: 192.168.0.4 vista copssh: 192.168.0.2
[192.168.0.4 $] ssh-keygen -t dsa
[192.168.0.4 $] scp -p id_dsa.pub tester at 192.168.0.2:.ssh
[192.168.0.2 $] cat .ssh/id_dsa.pub >> .ssh/authorized_keys
[192.168.0.2 $] chmod 700 .ssh
[192.168.0.2 $] chmod 600 .ssh/authorized_keys
[192.168.0.4 $] ssh id at 192.168.0.2
2001 Apr 09
2
"X11Forwarding yes" causes "error: socket: Protocol not supported"
Greetings,
I'm running OpenSSH_2.5.2p2, and OpenSSL-0.9.6a, on BSD/OS 4.0.
Following the FAQ, I added the following line to my sshd_config
in order to enable X11 forwarding:
X11Forwarding yes
Now openssh is disconnecting my sessions immediately after
authentication and login with the following error messages:
"error: socket: Protocol not supported"
"Disconnecting: Command
2011 Oct 26
4
C6: ssh X-forwarding does not work
Hi all,
I have C6 i386 with cr repo enabled;
problem is, I can't get x-forwarding to work, xorg-x11-auth rpm is
installed, have checked sshd config for
#X11Forwarding no
X11Forwarding yes
#X11DisplayOffset 10
Here is a verbose ssh logon, I can't see any difference to a working server:
debug1: Authentication succeeded (password).
debug1: channel 0: new [client-session]
debug3:
2003 Jan 21
3
X11 forwarding problem -- openssh-3.5p1 -- redhat 8.0 -- linux 2.4.18
All,
I'm working on upgrading a machine from RH 6.2 to RH 8.0. I've
encountered one major (for me) snag in that I cannot get X11 forwarding to
work anymore.
I've been google-ing the error messages all morning, with no luck.
Here is debugging output from the server (client debugging output sent
upon request... I don't feel it is relevant). What I feel is interesting
is at the
2017 Oct 13
2
X11forwarding yes: how to debug/setup after xauth fix
On 13/10/2017 08:03, Damien Miller wrote:
> On Thu, 12 Oct 2017, Michael Felt wrote:
>
>> On 08/10/2017 23:32, Michael Felt wrote:
>>> On 04/10/2017 11:07, Michael Felt wrote:
>>>> I do not often use X11 - but when I do I prefer to enable
>>>> X11forwarding, and when finished - turn it off. This is preferable,
>>>> imho, to having
2002 Jul 08
0
[Bug 342] New: RhostsRSAAuthentication does not work with 3.4p1
http://bugzilla.mindrot.org/show_bug.cgi?id=342
Summary: RhostsRSAAuthentication does not work with 3.4p1
Product: Portable OpenSSH
Version: -current
Platform: ix86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ssh
AssignedTo: openssh-unix-dev at mindrot.org
2001 May 21
1
PasswordAuthentication no and protocol V2
PasswordAuthentication seems to be accepted regardless when DSA
authentication is not available. Client and server are Linux -
openssh-2.5.2p2-1.7.2
Server config is:
Port 22
ListenAddress 0.0.0.0
HostKey /etc/ssh/ssh_host_key
HostKey /etc/ssh/ssh_host_dsa_key
KeyRegenerationInterval 3600
LoginGraceTime 600
ServerKeyBits 768
IgnoreRhosts yes
PasswordAuthentication no
2002 Oct 10
1
NEdit Highligth patterns for R
Hi
I've just submitted to the NEdit development team a R highligth patterns
for NEdit (www.nedit.org).
NEdit is a text editor for LINUX which I use to write small R functions.
In my opinion is a very good tool for small scripts, maybe for huge
projects is not the best.
I'm attaching the R-5.1.pats file so you can try it.
As usual contributions and comments are welcome.
Regards
EJ
2004 Mar 18
1
3.8p1 password expiry, Solaris 8
I can't seem to get the /etc/shadow password expiry working on
3.8p1 on Solaris 8. It works fine with 3.7.1p2 and pwexp26.
Logins aren't affected after a 'passwd -df' or 'passwd -f'.
Here's the configure, using gcc 3.2:
--prefix=/usr --sysconfdir=/etc/ssh --with-tcp-wrappers \
--without-pam --libexecdir=/usr/sbin --mandir=/usr/share/man \
--with-shadow
'uname
2010 Dec 31
1
amanda backup ssh key
hello list,
I am attempting to ssh via a user account setup for amanda backups
from the backup server to the test backup client. AFAIK everything is
setup correctly yet when I ssh as the user to the client I have to
type the password. the public key is in the authorized_keys file of
the client and permissions all seem correct.
Here is a verbose output of the ssh session
[amandabackup at