similar to: gnuclient X11 & openssh

Dear list, Not strictly R ... In R on Xemacs with ESS (R-2.0.1, Xemacs-21.4.15-r3, ESS-5.2.6) on gentoo-linux when I use k<-edit(k) or fix(k) to change a small vector k <- c(1,2,3,4,5,6) the opened window (called '6b8b4567') appears not to be connected to the gnuclient and I'm able to edit the file but has no instructions in the minibuffer and C-x # gives '6b8b4567 does

In switching to openssh from ssh-1.2.27, I have encountered the following problem with the way openssh handles its XAUTHORITY files separately from ~/.Xauthority. XEmacs has a gnuserv process that runs and allows commands to be issued to a remote XEmacs process. The trouble is when the command is to make a new frame ( window ) on a different X display, it fails because the Xauth cookie is not in

Hi, I see there are some previous threads on gnuclient.exe, but I can't figure this out based on those... I recently started using ESS with Xemacs. I'm on Windows XP. On starting iESS, my editor gets set to 'gnuclient.exe'. I don't understand how this works, since there is no executable anywhere on my machine called "gnuclient.exe". But I have no complaints: I like

I decided to try out Xemacs instead of Emacs in Linux (RH 7.2). After doing lots of configuration of Xemacs, I finally discovered a major problem. With Emacs, when I use R, I start Emacs twice (at least), in different viewports, once as emacs -f R and once as emacs myfile.R Then I try commands in the first one, and, when they work (which isn't very often), I cut the command with C-w,

I'm trying to use ESS & xemacs under debian linux testing and KDE. My problem is that I didn't find any document in the internet explaining a **step by step** session with R and xemacs. The (wrong) procedure I follow (to no avail!) is: 1) I start R in a terminal window; 2) I start xemacs and open a file with the extension .R (test.R); 3) I issue M-x R RET and I can see an Rd new

Hello all, $XAUTHORITY location has moved from under /tmp to ~/.Xauthority in 2.9p2. The commit message was: --- remove xauth-cookie-in-tmp handling. use default $XAUTHORITY, since we do already trust $HOME/.ssh you can use .ssh/sshrc and .ssh/environment if you want to customize the location of the xauth cookies --- The latter is true, but can only be enabled in per-user basis as far as I see.

As a user of only R, I don't use much of the potential of ESS and Emacs. Without entering a religious feud, is there any reason I should use XEmacs rather than my current GNU Emacs? (I looked on the XEmacs site, but I didn't understand the programming issues they were talking about (over my head).) Martin Henry H. Stevens, Assistant Professor 338 Pearson Hall Botany Department Miami

Hi, if I do the following: ssh -X localhost su - another_user xterm I get: X connection to ming:10.0 broken (explicit kill or server shutdown). Where what is really wanted was something like: Xlib: connection to ":0.0" refused by server Xlib: Client is not authorized to connect to Server xterm Xt error: Can't open display: :0.0 'tis easy to reproduce the bug, but the debug

http://bugzilla.mindrot.org/show_bug.cgi?id=803 Summary: Security Bug: X11 Forwarding is more powerful than it needs to be. Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: major Priority: P2 Component: ssh AssignedTo: openssh-bugs

Hi. I see this XAUTHORITY=/tmp/ssh-*/cookies issue has been discussed repeatedly, but I haven't seen a solution to the following problem. Remote user logs into firewall. On firewall, DISPLAY var set to secure channel, XAUTHORITY set to /tmp/ssh-*/cookies. X11 forwarding from firewall works fine. User logs into machine behind firewall, and sets DISPLAY var to firewall:X11DisplayOffset.0.

http://bugzilla.mindrot.org/show_bug.cgi?id=771 Summary: Add option to override XAUTHORITY env variable Product: Portable OpenSSH Version: 3.7.1p1 Platform: UltraSparc OS/Version: SunOS Status: NEW Severity: enhancement Priority: P5 Component: sshd AssignedTo: openssh-bugs at mindrot.org

Bob Proulx wrote: >> The error shown with "ssh -Xvvv" in all failure cases is, >> debug3: send packet: type 91 >> debug2: X11 auth data does not match fake data. >> X11 connection rejected because of wrong authentication. >> debug2: X11 rejected 1 i0/o0 >I don't know but I do have questions. So maybe... What is the output >of these

On Thu, 15 Nov 2001, Dan Astoorian wrote: > Date: Thu, 15 Nov 2001 16:09:20 -0500 > From: Dan Astoorian <djast at cs.toronto.edu> > To: Ed Phillips <ed at UDel.Edu> > Subject: Re: X11 cookies and forwarding > > On Thu, 15 Nov 2001 15:46:22 EST, Ed Phillips writes: > > I'm guess I wasn't following the whole cookies discussion completely > >

Dave Close wrote: > The error shown with "ssh -Xvvv" in all failure cases is, > debug3: send packet: type 91 > debug2: X11 auth data does not match fake data. > X11 connection rejected because of wrong authentication. > debug2: X11 rejected 1 i0/o0 I don't know but I do have questions. So maybe... What is the output of these commands? type xauth

Currently, ~/.ssh/environment can set static environment variables, and ~/.ssh/rc can run initialization routines. But there is no way for sshrc to propagate changes to the environment to the user's shell or command. There is, however, a possible way to do this. If the PermitUserEnvironment option is set, sshd could treat the stdout of sshrc as additional assignment lines of the form

I asked this question a while ago, but never got any response. Since then, I've researched the problem some more, so I can give a much more concise description of what's happening. I'm mounting the home directories of the users upon login (using pam_mount) from the Windows server. However, none of the users can run X Windows. It says there's a problem with the .Xauthority file.

https://bugzilla.mindrot.org/show_bug.cgi?id=2440 Bug ID: 2440 Summary: X11 connection will fail if user's home directory is read-only Product: Portable OpenSSH Version: 6.8p1 Hardware: Sparc OS: Solaris Status: NEW Severity: normal Priority: P5 Component: sshd

Since I had a problem and resolved with the JuiceSSH app on Android a couple of weeks ago, I've had a new problem with one of my local machines. Although I've checked everything I remember changing back then, I can't find the cause and would appreciate a clue or two. (Note, JuiceSSH is not involved in this problem.) I have four local machines which should be able to use "ssh

Hi! Is there any reason why support for the libwrap code isn't included in the X11 forwarding code? I'd like to restrict access to that port. How many applications would break if the tcp port would be closed and only the unix-domain socket would be available? It's true that x11 forwardings can be considered as a security risk and they are disabled because of that by default. I

Hi! Several people noticed problems with openssh Version 1.2.2 through 1.2.3 related to X11 forwarding under Linux. For example: Magnus Holmberg <pucko at lysator.liu.se> wrote: > I have just installed openssh-1.2.2p1-1 > on two of my machines and I have one problem. > > I have > X11Forwarding yes > in my /etc/ssh/sshd_config > > but when I try to ssh to that