Displaying 20 results from an estimated 500 matches similar to: "strange stuff from ''last''"
2003 Oct 19
1
jail + devfs + snp problem (FreeBSD 5.1-RELEASE-p10)
shell# /sbin/devfs rule -s 2 delset
shell# /sbin/devfs rule -s 2 add hide
shell# /sbin/devfs rule -s 2 add path random unhide
shell# /sbin/devfs rule -s 2 add path urandom unhide
shell# /sbin/devfs rule -s 2 add path zero unhide
shell# /sbin/devfs rule -s 2 add path pty\* unhide
shell# /sbin/devfs rule -s 2 add path pty\* unhide
shell# /sbin/devfs rule -s 2 add path tty\* unhide
shell#
1998 Aug 13
0
summary of replies to [strange stuff in 'last' command]
Sheldon E. Newhouse writes:
> Anyone have ideas on what this output from the 'last' command means?
>
> TIA,
> -sen
>
> xF*@**** otify ***@ Sat Aug 1 20:52 still logged in
> xF*@**** otify ***@ Sat Aug 1 20:52 - 20:52 (00:00)
> xF*@**** otify ***@ Sat Aug 1 20:52 - 20:52 (00:00)
>
1998 Aug 02
0
ipportfw - security
Hi
Are there any known security holes or necessary precautions in using port
forwarding with ipportfw?
I'm planning on forwarding ports from an outer firewall/router (connected
to the Internet) to a host in the DMZ, then on from the DMZ host to the
inner firewall, and finally from the inner firewall to some host on the
inside.
Thanks,
Jens
jph@strengur.is
From mail@mail.redhat.com Wed
2003 Jul 04
1
who am i
I don't think this is a problem with su. The same occurs when running login
in a shell, then logging out. I've seen this bug in FreeBSD since early 4.x,
I guess I just never bothered to mention it, thinking someone would notice
and fix it. It has certainly scared me a few times, it would be nice if it
was corrected.
Thanks.
-----Original Message-----
From:
2003 Jul 04
2
FW: who am i
Also, try doing 'who /etc' or any other directory.
-----Original Message-----
From: Mike Jakubik [mailto:mikej@trigger.net]
Sent: Friday, July 04, 2003 1:23 PM
To: Stable
Subject: RE: who am i
root@ns1:~# who am i
root ttyp1 Jul 4 13:20 (wettoast.org)
root@ns1:~# login
login: wettoast
Password:
Last login: Fri Jul 4 09:48:25 on ttyp1
Copyright (c) 1980, 1983, 1986,
2007 Jul 10
3
No password prompt for ssh from perl script
Hi,
I need some help from you guys for one issue I am facing with my script.
While logging into localhost using ssh from command prompt it works:
It works from command prompt --> ssh loginid at localhost
But when we try to login to localhost using ssh from perl script using
pseudo terminal, I am getting the following without any password prompt.
We are getting following instead of
2005 Dec 31
0
winecfg hangs forever
I installed wine-0.9 from pkgsrc on NetBSD/i386 3.0. When I run
winecfg, it never finishes, but it outputs:
wine: creating configuration directory '/home/ben/.wine'...
I see a number of wine processes:
sanctum $ ps alwwx | grep wine
1000 316 1 0 2 0 360 1016 poll Ss ? 0:00.03 /usr/pkg/bin/wineserver
1000 322 793 0 10 0 80 1212 wait I+ ttyp4
2001 Feb 20
1
2.5.1p1 ssh-agent path problem in Solaris
I'm having a path problem with OpenSSH 2.5.1p1 in Solaris (7). When
ssh-agent is run, environment variables aren't being passed to the
spawned shell.
sol# env | wc -l
23
sol# env | grep -i ssh
SSH_CLIENT=10.0.1.146 1047 22
SSH_TTY=/dev/pts/0
sol#
sol# ssh-agent sh
sol# env | wc -l
1
sol# env
SSH_AGENT_PID=12032
sol#
If I
2000 Mar 31
4
anomalous wtmp logging bug
I've noticed rather strange wtmp logging behavior in sshd. Can anyone
confirm or solve the following:
Once a user authenticates themself to sshd, sshd among other things
records the login in the wtmp, which `last` reads. However, sshd logs
hostnames which are longer than 16 characters instead of IPs like normal
programs would. As a result, I have useless entries such as:
tempest
1997 Sep 26
1
tty chowning
About a year ago I outlined a scheme for arranging chowning of the tty
end of ptys without needing root privileges. Since then, I haven''t had
time to actually implement it.
I was thinking about the problem again today, and, having learned a
bit about sessions and controlling ttys and stuff, was able to come up
with a simpler mechanism.
First, observe that the POSIX session mechanism, if
2003 Apr 09
2
[Bug 540] sshd [priv] doesn't give shell a tty and is killed by ^C too easily
http://bugzilla.mindrot.org/show_bug.cgi?id=540
stuge-openssh-unix-dev at cdy.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|sshd [priv] has PPID 1 and |sshd [priv] doesn't give
|is killed by ^C in terminal |shell a tty and is killed by
2000 Mar 13
0
duplicate log entries
When i use openssh's UseLogin option (i.e. set it to "Yes").. i get
duplicate entries in the wtmp file (when i type 'last' it displays
users who logged on via sshd twice), like this:
tempest ttyp4 63.10.229.126 Sat Mar 11 22:33 - 14:03 (15:29)
tempest ttyp4 1cust126.tnt5.ta Sat Mar 11 22:33 still logged in
note however that this is AFTER a user
2014 Sep 09
2
Re: CoreOS support
Here it is :D
root@ny2proxd03:/var/lib/vz/images/100# virt-resize --expand /dev/sda3 vm-100-disk-1.qcow2 vm-100-disk-1.qcow2.resized
Examining vm-100-disk-1.qcow2 ...
libguestfs: trace: set_verbose true
libguestfs: trace: set_verbose = 0
libguestfs: create: flags = 0, handle = 0x246f780
libguestfs: trace: add_drive "vm-100-disk-1.qcow2" "readonly:true"
libguestfs: trace:
2005 Oct 26
1
Error message with fbt::copen:entry probe
All,
The attached script is causing the following error message ...
bash-3.00# ./zmon_bug.d
dtrace: error on enabled probe ID 2 (ID 4394: fbt:genunix:copen:entry):
invalid address (0xfd91747f) in predicate at DIF offset 120
dtrace: error on enabled probe ID 2 (ID 4394: fbt:genunix:copen:entry):
invalid address (0xfef81a3f) in predicate at DIF offset 120
Any ideas?
thxs
Joe
--
2003 Sep 05
2
3.6p1 bug on SCO OpenServer
SCO OpenServer 5.0.x
Openssh 3.6p1
loginrec.c writes incorrect data into the ut_id field of the utmp file.
This has been an issue since at least openssh 3.0.2 but I never bothered
to report it. For Openssh 3.6p1, defining WITH_ABBREV_NO_TTY corrects
the problem. Below is a brief patch to configure which does this. You
can observe the errant results in the "Line" column from the
2002 Aug 28
5
Tru64 privsep patch testing
OK, I got a chance to try out the Tru64 patch for privsep. I applied the patch
to 3.4p1. Partial success, in that it now works for me for logins to "root".
Logins to ordinary accounts fail after authentication, when trying to set tty
characteristics. See the excerpt from the debug messages below. This is for
Tru64 V4.0F (with enhanced_security turned on, obviously.) I guess it's time
2019 Jan 06
0
Dovecot no logs by sieve user script
Op 06/01/2019 om 18:58 schreef Christian Wolf:
>
> Dear mailinglist,
>
> I have the problem that I had to migrate a setup and since then my
> user's sieve script does no longer log anything.
>
> I have sieve_user_log unset and sieve points to a folder (ready for
> ManageSievev service). In the old config I had sieve point to the
> symlink and sieve_dir point to
2000 Dec 06
1
openssh-2.3.0p1 (Linux) fails using options with dss key
I'm trying to change my local setup from ssh2 to openssh-2.3.0p1. I need
captive comands and specific environments for each key, i.e. the
"command=XXX" and "environment=X=y" options. Unfortunately I *also* need
to support the existing ssh2 client for a transition period, since it's
impractical to change all user's environments to openssh in one go.
I have converted
2000 Jun 16
3
login reporting (utmp?) problem on Linux
I have recently compiled and installed openssh-2.1.1p1 on a linux box.
The login reporting does not seem to work properly.
When logging into the box via ssh (protocol 1) utmp shows the user logged
in and the tty properly, but the field for the login date/time and the
field for originating host contain all NULLs.
Is anyone else seeing this same behavior, or have I just done something
really
2010 Mar 09
1
sshd version OpenSSH_5.4p1 fails on OpenBSD 4.2 GENERIC macppc
Because OpenSSH_5.4 doesn't build on my OpenBSD 4.2 box, I tried
OpenSSH_5.4p1 which builds and installs fine.
After starting server with sudo /opt/sbin/sshd -p 2222 -d, my ssh
client can connect, but the session is closed by server as soon as it is
started:
[...]
User child is on pid 10318
debug1: Entering interactive session for SSH2.
debug1: server_init_dispatch_20
debug1: