similar to: Help with exporting keys

Some terminals support CSI u style encoding of keystrokes, typically via the Kitty keyboard protocol[1]. Program wishing to receive this encoding need to send a sequence like "CSI > 5 u" to enable it. Imagine a process tree like xterm -> bash -> ssh -> foo where foo is any program that enables CSI u mode (such as a newfangled shell or text editor). If the network

ssh already restores all TTY flags on exit: https://github.com/openssh/openssh-portable/blob/V_9_8_P1/sshtty.c#L56-L78 It's possible there are some exit cases that are not hitting the leave_raw_mode(), but if so then they aren't obvious. On Sun, 7 Jul 2024, Johannes Altmanninger wrote: > Some terminals support CSI u style encoding of keystrokes, typically via > the Kitty keyboard

I've been installing OpenSSH 2.9p2 onto several RedHat Linux machines, after compiling in the GSSAPI/Kerberos5 patch from here: http://www.sxw.org.uk/computing/patches/openssh.html I've been using ssh both to let users in via passwords and Kerberos tickets, and both have been working fine... except for one irritating machine, which (for no good reason I can see) fails when using kerberos

The purpose of this email is to (1) report an example where fisher.test returns p > 1 (2) ask if there is a reliable way to avoid p>1 with fisher.test. If one has designed one's code to return an error when it finds a "nonsensical" probability, of course a value of p>1 can cause havoc. Example: > junk<-data.frame(score=c(rep(0,14), rep(1,29), rep(2, 16))) >

Running "ls" on a large directory (/usr/bin) locks the term when using protocol 2.0. A tilde works to escape the session. Client: OpenSSH_2.9p2 on NetBSD Server: OpenSSH_2.3.0 on FreeBSD Output of ssh -v <FreeBSD host>: OpenSSH_2.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090602f debug1: Seeding random number generator debug1: Rhosts Authentication disabled, originating port will

Hello, I believe I may have discovered what appears to be a small anomoly in the way OpenSSH closes connections and thought if I gave you some feedback I might be able to make a very small contributution to the development of openssh. This might be a Solaris 2.6 anomoly or an openssh anomoly or a combination of both. I came across this apparent anomoly because we use openssh (via cron) here to

Markus Friedl wrote: > > ?'m not sure where the 'bug' is and whether this is 'really' a bug. > > try to talk to the openssh-unix-dev list, i'm too busy right now :( > > -m > > On Thu, Aug 16, 2001 at 03:51:19PM +0100, Mark Reardon wrote: > > Hello Markus, > > > > I recently posted you with a mention of the 2.9p2 possible problem

I was taught in kitty school that running a ntp server in a vm was a bad idea. Is that still the case?

Hi, We're running Samba version 1.9.16p2 under Solaris 2.5.1 (w HW update 11/97). Our PCs run Windows95 with Network Neighborhood and a few have been upgraded to Windows98. I am currently looking at upgrading to Samba 1.9.18p10. On Fri., 12/4 one of our users reported when she selecting Entire Network she received the error "Unable to browse the network. The specified computer

When I SSH using protocol 1 from a Debian box running OpenSSH 2.9p2-4 to a sparc.sunos5 box running vanilla OpenSSH 2.9.1, after a little while (of inactivity?) I get the following message on the client terminal: Disconnecting: protocol error: rcvd type 98 Looking further, this message is actually caused by the SSH daemon. However, I'm at a loss to determine why sshd is doing this. I attach

Dear list, Hi, I am trying to get the second derivative of a logistic formula, in R summary the model is given as : ### >$nls >Nonlinear regression model >model: data ~ logistic(time, A, mu, lambda, addpar) >data: parent.frame() > A mu lambda >0.53243 0.03741 6.94296 ### but I know the formula used is #

The System: RedHat 7.0 OpenSSH_2.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090581f Client: PuTTY The Problem: I've installed the newest version of OpenSSH on RedHat 7.0 and can get most things to work, except when I want to use Public Keys with version 2.0. If I use straight password authentication, I can get PuTTY to connect using either SSH 1 or SSH 2. If I RSA authentication for SSH1, it

Message: 1 Date: Mon, 14 Feb 2005 09:53:36 +1100 From: "PHP Mechanic" <oliver.bode@phpmechanic.com> Subject: [Asterisk-Users] Who makes these phones? To: "Asterisk Users Mailing List - Non-Commercial Discussion" <asterisk-users@lists.digium.com> Message-ID: <08d401c5121e$dbea4750$0200a8c0@oliver> Content-Type: text/plain; format=flowed;

Hi I'm currently testing OpenSSH_2.9p2 on AIX. Is there any reason why the hostname is used for the DISPLAY variable instead of localhost? I just had problems with X11 forwarding on a AIX test machine that has HCMP configured but not running. (the network interface has a different IP address in that state) After changing the DISPLAY variable X11 forwarding worked fine. Frank -- Diese

Using OpenSSH_2.9p2 on Linux and Sparc Solaris. Trying to connect from Linux to Solaris, with remote port-forwarding i.e. On Linux, ssh -R 3000:Linux:23 Solaris The connection is established okay, but the port-forwarding does not work; on Solaris, the connection to localhost port 3000 is accepted, but it appears as if no data makes it back to port 23 on Linux. If an older 1.2.30 sshd is used

Dear list, I am trying to predict species volume from bioclimatic data, I have various sites and I have a data frame with species volume and the corresponding bioclimatic data for each site. I read on a discussion forum that you can use ordination to predict species abundance (in my case volume) from 'new' climate data for sites where you do not know the abundance. Unfortunately I

I am using a multiple additive model (in the quantreg package) and I would like to 'extract' the fitted model formulae ie- for a straight line the formula would be y= 'a+b*c' for my multiple model I would expect somthing more complex because the model is not linear (its a bit like a GAM) but given I can plot the model using # f<-fitted(model) #lines(f) there must be a formula

On Mon, 8 Jul 2024, David Leadbeater wrote: >manifestation of the problem. As mentioned in the Kitty issue, shells >should really gain support for input modes. Pretty sure that not. That would totally mess up things like OS/2 console windows and possibly VT100 (hardware) terminals and just look like extra junk spewed before the prompt (also throwing off the shell surrounding the ssh

On Mon, 8 Jul 2024 at 11:58, Damien Miller <djm at mindrot.org> wrote: > ssh already restores all TTY flags on exit: This isn't a TTY flag, it's a terminal mode enabled via an escape sequence, there's actually multiple modes involved (CSI u as in the subject), but xterm also supports "modifyOtherKeys" and Vim for example will pick depending what the terminal reports

according to the openssh mailing list page, this is the spot to report/discuss bugs and i have a potential one. on the other hand, it is probably something i am not doing correctly. the system is red hat linux 6.2 (yuk) running the openssh rpm i grabbed off of the portable openssh site listing, with sshd version OpenSSH_2.9p2 i have it installed via rpm and when i go to launch sshd it gives me