similar to: Modify $TERM from config

A user at a Windows PC uses our SSH client software (Anzio) to access a Linux sshd. User would like the banner from the server to display BEFORE entering a login name. According to the SSH spec, this should be allowed. But the OpenSSH source seems to have specifically prevented this. Is there a good reason for this? Regards, ....Bob Rasmussen, President, Rasmussen Software, Inc.

I setup a ssh chroot jail following this[1] guide. It works for my user to login, use ls and use scp which is all I really want. I do have a problem I cannot solve: when connected and navigating the filesystem, the backspace key actually moves the cursor forward and does not delete what I type. I may have found a hint from some googling that readline will read in /etc/inputrc on login but if

I don't believe you've said: are the disconnects happening during periods of idleness on the connection, or periods of activity? If idleness, some device or script could be actively doing a disconnect-on-idle. On Mon, 26 Feb 2018, Kip Warner wrote: > Hey list, > > I've read the man page for both the client and server daemon, so either > I missed something or this

Debian GNU/Linux 8.0 (jessie) OpenSSL 1.0.1k gcc (Debian 4.9.2-10) 4.9.2 "make tests" fails here: /usr/src/INET/openssh/ssh-keygen -lf /usr/src/INET/openssh/regress//t12.out.pub | grep test-comment-1234 >/dev/null run test connect.sh ... ssh connect with protocol 1 failed ssh connect with protocol 2 failed failed simple connect Makefile:192: recipe for target 't-exec' failed

I connect with the OpenSSH client on Windows to the OpenSSH server on FreeBSD, all in one LAN, Wifi to Eithernet. After a while, usually when the connection is inactive for some time, it becomes dysfunctional: it becomes impossible to connect through reverse port forwards from FreeBSD to Windows. At such times killing the ssh server process on FreeBSD, corresponding to the connection,

> On 2020-05-31 18:39, Ira wrote: > > I typed this at the terminal prompt: export ASTERISK_PROMPT="%C31[%H]: " > > Typing at the same place: echo $TERM returns xterm > > And now I have colored prompts at the Asterisk command line, so I can > assure you it can work. Kind of cool, 14 years using Asterisk and > because of your question, I now have colored

Hi, I'm using the official 3.6 release binaries for x64 Linux. When compiling with warnings, I don't see any color diagnostics. Explicitly enabling -fcolor-diagnostics works fine. I have TERM set to xterm-256color. Any idea why? For what it's worth, I tried compiling LLVM/clang from trunk and color diagnostics work fine by default. Upon further investigation, I saw that the official

I have discovered that the JUNOS DHCP server in Juniper J-series routers doesn't support setting the next-server IP address field (I have filed a bug report with Juniper and they are working on it). Instead, it puts the "boot server" in the sname field, which PXELINUX currently ignores. Here's a simple patch (vs. 3.36) that will take an IP string in the field. My assembly is

Hi I''ve installed xen with debian sarge as dom0 and domU''s. I''ve used debootstrap to install the first domU, and it worked fine except one little thing: When I connect to the domU console (xm console 2) and execute base-config (a debian thing), it failes. To solve the problem, set the TERM env to xterm (export TERM=xterm) and then execute base-config, and you have a

I know it is just after a release, but I'm trying to see how the regression tests look on Tru64. I hadn't had a chance to really look at them before because I didn't have sudo installed on Tru64 (now I do). Anyway, for the 3.9p1 release, all of them run except for a couple of problems: - agent-ptrace fails; it looks like setgid isn't enough to kill tracing under Tru64, and I

On 31.05.20 at 19:26 Jeff LaCoursiere wrote: > Hi, > > I had posted this a few hours ago, but got caught in moderation for size.  I trimmed down the pic and attached. > > I am on an Ubuntu 16 workstation, in an Ubuntu terminal window, ssh'ed to the PBX (amazon instance).  You can see my term type matches yours. Same problem here (asterisk 16.x / CentOS 7). # echo $TERM

I have an old (1997) Best Ferrups (model FE18KVA) that I am trying to monitor for the first time, but all the Best drivers fail to communicate with it. In ups_sync() in bestuferrups.c and bestfcom.c, the "time" command is sent and a one-line response is read. However, on my UPS, that command returns the current time and then prompts for a new time setting. I worked around that by just

I had a power hiccup yesterday and a server connected to a Best Ferrups 18KVA shutdown. The problem is that the UPS is reporting remaining runtime in minutes but nut treats it as seconds (so nut thought it only had 46 seconds left). Simple patch: diff -urN nut-2.2.1-dist/drivers/bestfcom.c nut-2.2.1/drivers/bestfcom.c --- nut-2.2.1-dist/drivers/bestfcom.c 2008-06-13 14:04:07.000000000 -0500

Well, after digging around and thinking some more, I'm giving up on the idea of preallocating a TTY to get post-auth privsep working on Tru64. I don't think it will work, because just allocating a TTY doesn't fix the problem - there's no valid way to tie that TTY back to the client process (because it hasn't requested a TTY yet and may not ever do so). The problem is that the

Is it possible to have memdisk emulate multiple drives? Here's why I'm asking: I have a Dell server that I replaced the motherboard. I want to reset the service tag to the correct tag for the system, and the only way to do that is to run a Dell tool under DOS. I have downloaded the tool, but it is doubly-wrapped: a self-extracting ZIP file (which I unzipped under Linux) which contains a

Hi Hans, I used the official Ubuntu binary: http://llvm.org/releases/3.6.0/clang+llvm-3.6.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz Seems to me that it should be an optional dependency. If the target system has tinfo or ncurses, it should use it, otherwise fallback to no color. On Mon, Mar 30, 2015 at 6:02 PM, Hans Wennborg <hans at chromium.org> wrote: > Hi Perry, > > On Mon, Mar

If a user doesn't have a ~/mail directory and logs in, the directory is created for them. However, it is created with insecure permissions, 0770 (full group access). The problem is this bit in src/lib-storage/index/mbox/mbox-storage.c: #define CREATE_MODE 0770 /* umask() should limit it more */ The code then uses CREATE_MODE as an argument to mkdir_parents(), but mkdir_parents()

It depends how you "kill" the SSH server. If you kill it by sending it a SIGKILL signal, it will NOT notify the client, so the client will stay running until the client discovers the connection is broken. What happens if you send the SSH server a SIGHUP signal? This should cause an orderly shutdown on the server, which should notify the client, which should cause the client to do

Looks like the binaries weren't built against tinfo correctly. On Mon, Mar 30, 2015 at 2:30 PM David Blaikie <dblaikie at gmail.com> wrote: > +Chandler, who made the change > +Hans, who released the compiler > > I'm really not sure what the right answer is here, though I don't know > that much about releasing software & dependencies (whether they can be made

I am trying to get my xterm window under gnome to open with large fonts, with light green foreground and dark green background. I have the following .Xdefaults file contents: $ cat .Xdefaults ! This is a comment ;-) #ifdef COLOR *customization: -color #endif !! Let's cast a wide net, for any app supporting these ! Blink instead of beeping *visualBell: True *scrollTtyOutput: False