't
> > think it has anything to do with forwarding traffic, X11 or
> > otherwise, through an ssh tunnel. Just to be sure I tried switching
> > that on, but it didn't seem to help.
> >
> > This is a reiteration of the problem so no one has to sift though
> > the arch
mitTunnel has something to do with
> using a specific software network loopback device, tun(4). I don't
> think it has anything to do with forwarding traffic, X11 or
> otherwise, through an ssh tunnel. Just to be sure I tried switching
> that on, but it didn't seem to help.
>
mitTunnel has something to do with
> using a specific software network loopback device, tun(4). I don't
> think it has anything to do with forwarding traffic, X11 or
> otherwise, through an ssh tunnel. Just to be sure I tried switching
> that on, but it didn't seem to help.
>
se, through an ssh tunnel. Just to be sure I tried switching
that on, but it didn't seem to help.
This is a reiteration of the problem so no one has to sift though
the archives to find it:
$ xhost +
$ ssh -Y 192.ip.of.freebsdserver
Warning: No xauth data; using fake authentication data for
On Wednesday 12 November 2008 15:51:42 Elliot Isaacson wrote:
>
> #UsePAM yes
> #AllowTcpForwarding yes
> #GatewayPorts no
> #X11Forwarding yes
> #X11DisplayOffset 10
> #X11UseLocalhost yes
> #PrintMotd yes
> #PrintLastLog yes
> #TCPKeepAlive yes
> #UseLogin no
> #UsePrivilegeSeparation yes
> #Per
7.0-RELEASE GENERIC).
> >
> > I have not changed the defaults in the sshd_config file.
> >
> > One the client computer:
> >
> > $ xhost +
> >
> > $ ssh -Y 192.ip.of.server
> > Warning: No xauth data; using fake authentication data for X11
> &g
; I have not changed the defaults in the sshd_config file.
>
> One the client computer:
>
> $ xhost +
>
> $ ssh -Y 192.ip.of.server
> Warning: No xauth data; using fake authentication data for X11
> forwarding.
>
> /usr/local/bin/xauth: creating new authority
&g
ost +
$ ssh -Y 192.ip.of.server
Warning: No xauth data; using fake authentication data for X11
forwarding.
/usr/local/bin/xauth: creating new authority
file /home/xxx/.Xauthority
/usr/local/bin/xauth: (stdin):1: bad display name "unix:10.0"
in "remove" command
/usr/local
How does this affect Windows VISta and OSX connections?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of matt donovan
Sent: Tuesday, August 14, 2007 12:42 PM
To: freebsd-questions@freebsd.org
Subject: I was having an xauth error about the hexkey not found
I just had to redo this part
# set up default Xauth info for this machine
case `uname` in
Linux*)
if [ -z "`hostname --version 2>&1 | grep GNU`" ]; then
hostname=`hostname -f`
else
hostname=`hostname`
fi
;;
*)
hostname=`hostname`
;;
esac
authdisplay=${display:-:0}
mc
On Thursday 12 July 2007 13:59:54 Andy Greenwood wrote:
>
> I had this same problem recently on my server. the sshd_config man
> page says that the default location for xauth is /usr/X11R6/bin/xauth,
> but mine was installed as /usr/local/bin/xauth. adding
>
> XAuthLocation /u
on
> > > the remote host running Linux: [EMAIL PROTECTED]:~$ kate
> > > Xlib: connection to "localhost:11.0" refused by server
> > > Xlib: Invalid MIT-MAGIC-COOKIE-1 key
> > > kate: cannot connect to X server localhost:11.0
> >
> > I just d
nection to "localhost:11.0" refused by server
> > Xlib: Invalid MIT-MAGIC-COOKIE-1 key
> > kate: cannot connect to X server localhost:11.0
>
> I just did 'ssh' to one of the Linux hosts and when the connection was made,
> I
> got this:
>
> Warning:
On 7/10/07, Pollywog <[EMAIL PROTECTED]> wrote:
On Tuesday 10 July 2007 14:41:01 Pollywog wrote:
>
> I just did 'ssh' to one of the Linux hosts and when the connection was
> made, I got this:
>
> Warning: No xauth data; using fake authentication data for X11 for
On Wednesday 11 July 2007, Pollywog wrote:
> I found out that "mcookie" generates magic cookies for xauth, but I do not
> have the mcookie command in FreeBSD, though it exists on my Debian Etch
> system and is part of the util-linux package.
I think you need to generate a new
On Tuesday 10 July 2007 14:41:01 Pollywog wrote:
>
> I just did 'ssh' to one of the Linux hosts and when the connection was
> made, I got this:
>
> Warning: No xauth data; using fake authentication data for X11 forwarding.
>
> Does this possibly have som
1 key
> kate: cannot connect to X server localhost:11.0
I just did 'ssh' to one of the Linux hosts and when the connection was made, I
got this:
Warning: No xauth data; using fake authentication data for X11 forwarding.
Does this possibly have something to do with the problem I ment
Hi list :)
is either of
1) having a host added to .Xauthority as trusted, and then doing "ssh -X [EMAIL
PROTECTED] cmd"
2) ssh -X -Y [EMAIL PROTECTED] cmd
inherintly less secure than the other? (or more prone to becoming an attack
vector to MY local computer?
thanks!
_
On Thu, 2005-10-13 at 19:34 -0700, James S Blankenship wrote:
> Thanks. Pardon me if this is a stupid question, but I don't know what my
> machines host name is; I used DHCP during installation, and believe that it
> may have been named .ontrca.adelphia.net by default. How can I determine the
> loc
adelphia.net" and when I
> > shutdown X I get the error: Xauth bad display name
> > ".ontrca.adelphia.net:0" in "remove" command. I tried
> > changing /etc/hosts from the default
> > localhost.my.domain to
> > localhost.ontrca.adelphia.net<h
On Thu, 2005-10-13 at 19:04 -0700, James S Blankenship wrote:
> I keep getting this error when gnome starts "could not
> lookup address .ontrca.adelphia.net" and when I
> shutdown X I get the error: Xauth bad display name
> ".ontrca.adelphia.net:0" in "remo
I keep getting this error when gnome starts "could not
lookup address .ontrca.adelphia.net" and when I
shutdown X I get the error: Xauth bad display name
".ontrca.adelphia.net:0" in "remove" command. I tried
changing /etc/hosts from the
El Osteguna 13 Urria 2005 05:23, James S Blankenship escribió:
> I've successfully installed FreeBSD 5.4, and have X running. But I get the
> error message Xauth bad hostname when logging out of gnome, and when
> starting gnome, so gnome doesn't run as well as it could. H
I've successfully installed FreeBSD 5.4, and have X running. But I get the
error message Xauth bad hostname when logging out of gnome, and when
starting gnome, so gnome doesn't run as well as it could. How can I fix
this? Sysinstall?
Best rega
On Mon, 08 Aug 2005 19:13:01 +0200, Adrian Gschwend wrote:
[...]
> I tried to check where I find xauth but I can't find the correct port so
> far, what I compiled so far is XFree86-libraries. Which port do I miss
> here?
Found it, I installed XFree86-4-clients and all is fine now.
So far so good, but the DISPLAY variable does not get set properly. So I
connected to the host with -v in ssh to get some more information:
debug1: Requesting X11 forwarding with authentication spoofing.
debug1: Remote: No xauth program; cannot forward with spoofing.
I tried to check where I find
How do you generate the hexkey for 'xauth add displ proto hexkey'
There doesn't seem to be a keygen program anymore...
sdb
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, s
to xauth as the
last pid. Unfortunately, this means I have to log out of my xsession
completely to free up the shared memory.
Unfortunately, I have not been able to determine the offending program.
Looking for assistance in determining problem.
ENVIRONMENT:
bash-2.05a$ uname -a
FreeBSD ip-34
to xauth as the
last pid. Unfortunately, this means I have to log out of my xsession
completely to free up the shared memory.
Unfortunately, I have not been able to determine the offending program.
Looking for assistance in determining problem.
ENVIRONMENT:
bash-2.05a$ uname -a
FreeBSD ip-34
29 matches
Mail list logo
