Displaying 20 results from an estimated 20000 matches similar to: "[Bug 1459] New: Request for better documentation of shell used to run commands"
2015 May 01
0
[Bug 1459] Request for better documentation of shell used to run commands
https://bugzilla.mindrot.org/show_bug.cgi?id=1459
Damien Miller <djm at mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |djm at mindrot.org,
| |dtucker at zip.com.au
2015 May 01
0
[Bug 1459] Request for better documentation of shell used to run commands
https://bugzilla.mindrot.org/show_bug.cgi?id=1459
Damien Miller <djm at mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |2360
--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching
2015 May 01
0
[Bug 1459] Request for better documentation of shell used to run commands
https://bugzilla.mindrot.org/show_bug.cgi?id=1459
Darren Tucker <dtucker at zip.com.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #2613|ok?(dtucker at zip.com.au) |ok+
Flags| |
--
You are receiving this mail because:
You are
2015 May 01
0
[Bug 1459] Request for better documentation of shell used to run commands
https://bugzilla.mindrot.org/show_bug.cgi?id=1459
Damien Miller <djm at mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #2 from Damien Miller <djm at
2015 Aug 11
0
[Bug 1459] Request for better documentation of shell used to run commands
https://bugzilla.mindrot.org/show_bug.cgi?id=1459
Damien Miller <djm at mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
--- Comment #3 from Damien Miller <djm at mindrot.org> ---
Set all RESOLVED bugs to CLOSED with release
2001 Mar 17
1
sshd executes ~/.ssh/sshrc without using user's shell
I am considering allowing (relitivly) untrusted local users onto my
fileserver, so they can use SFTP to access their home directories.
I have a custom shell, (a taint-mode enabled perl script) that allows
users to change their password, which I have modifed to only allow a
'-c' command for the sftp-server.
I have also disabled TCP port forwarding. However, some reading of the
OpenSSH
2002 Apr 03
0
scp fails with "ls" or other command in sshrc
sshrc MUST NOT produce any output on 'stdout', use 'stderr' instead.
On Wed, Apr 03, 2002 at 01:13:07AM -0800, Mark Pitt wrote:
> On AIX 4.3.3 with 2.9.9 and 3.1.p1, once I place "ls"
> or any other command in sshrc such as:
>
> ls
> ls > /tmp7junk.txt
> cat /tmp/junk.txt
>
> then scp simply ceases to work, stopping at first
> "file
2016 Aug 01
4
OpenSSH 7.3p1 can't be build on Solaris 10
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Solaris 10 x64 kernel 150401-35
LibreSSL 2.4.1
GCC 5.2
./configure --with-privsep-user=sshd --with-pam --with-pie
--with-ssl-dir=/usr/local 'CFLAGS=-O3 -m64 -mtune=native -pipe'
'LDFLAGS=-m64'
successful.
gmake produces error:
root @ khorne /patch/openssh-7.3p1 # gmake
conffile=`echo sshd_config.out | sed
2005 Feb 07
1
treat output of sshrc as environment assignment lines?
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
2002 Mar 15
1
Problems compiling on Redhat
Hello,
I have a x86 Red Hat Linux release 7.0 (Guinness) box.
OpenSSL 0.9.6b
I downloaded the most recent version of OpenSSH (3.1p1).
Attached is the result of ./configure and make.
Thanks in advance
-------------- next part --------------
# ./configure
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are
2005 Oct 17
1
Liebert ESP-II protocol
I see there has been some Liebert work here recently. I have a Liebert
UPS that has no USB, just RS-232. I reverse engineered the ESP-II
protocol, at least as far as normal MultiLink monitoring goes, which was
pretty simple. The protocol provides a table of parameter types and
index ranges. So, I can read and (if I dare) write the parameter tables.
We might be able to share info between
2002 Sep 24
0
[Bug 402] New: Suggested sshrc script unsafe
http://bugzilla.mindrot.org/show_bug.cgi?id=402
Summary: Suggested sshrc script unsafe
Product: Portable OpenSSH
Version: -current
Platform: All
OS/Version: All
Status: NEW
Severity: minor
Priority: P2
Component: Documentation
AssignedTo: openssh-unix-dev at mindrot.org
ReportedBy: kolya at
2011 Sep 16
2
weird make errors on portable snapshots
When doing a make with the portable developer version,
I came across this error:
ssh/ssh_host_ecdsa_key|/opt/etc/ssh_host_ecdsa_key|g' -e
's|/etc/ssh/ssh_host_dsa_key|/opt/etc/ssh_host_dsa_key|g' -e
's|/etc/ssh/ssh_host_rsa_key|/opt/etc/ssh_host_rsa_key|g' -e
's|/var/run/sshd.pid|/var/run/sshd.pid|g' -e
's|/etc/moduli|/opt/etc/moduli|g' -e
2001 Aug 18
0
installing openssh-2.9p2 after openssl-0.9.6b on freebsd-4.3-RELEASE
hi.
please cc comments 2 me, i'm not subscribed.
what i did is simply this (you might have guessed :)
i had to install the improved version of openssl after recent, urgent
improvements. with this came came the urgent desire for openssh-CURRENT,
which had to be reinstalled, because an old(?) version comes with the
distribution.
here's the diff. spare me and yourselfs a desciption of
2018 Jan 08
3
SFTP chroot: Writable root
On Sun, 2018-01-07 at 18:41 +0000, halfdog wrote:
> Hello list,
>
> I created a page to demonstrate, what would happen when chroot
> root directory is writeable. In fact, code execution is possible
> already, when only /etc and /bin are writable. I also tried to
> escape the chroot jail, but that did not work for non-root users.
>
> As the 2009 CVE activities mention,
2020 Sep 18
2
Aborting an ssh connection on sshrc execution failure
Hi!
It feels like there is an obvious answer to this that I'm not seeing,
but I've been testing, reading manuals and googling for a while now and
can't seem to get it to work.
I have an SSH server that mounts a windows share on login, to act as a
SFTP proxy for windows home directories. The mounting of the users'
homedirs is done via a call from /etc/ssh/sshrc. This mount
2014 Apr 09
2
immediate "gotcha" in compilation!? 6.6p1 versus openssl 1.0.1g
So they released openssl 101g to patch for a hole. One then wishes to
recompile openssh.
After ".configure" I get this:
synergy[124]# make
if test "doc" = "cat"; then manpage=./`echo scp.1.out | sed
's/\.[1-9]\.out$/\.0/'`; else manpage=./`echo scp.1.out | sed
's/\.out$//'`; fi; if test "doc" = "man"; then
2004 Oct 27
1
winbind: using idmap only if user doesn't exist in UNIX getpw*(3) ?
Greetings all.
I have a requirement to use winbind to allocate UID/GIDs for
users but only if they aren't in the non-winbind nsswitch sources.
I.e, given
smb.conf ; samba 3.0.7
realm = DOMAIN
workgroup = DOMAIN
log level = 3 idmap:10 winbind:10
idmap gid = 50000-59999
idmap uid = 50000-59999
ADS users:
DOMAIN\adsuser1 ; only in ADS, not NIS
DOMAIN\adsuser2 ; only in ADS, not
2008 May 12
12
[Bug 1463] New: Running nohup sleep 70 & and then exiting shell, hangs ssh
https://bugzilla.mindrot.org/show_bug.cgi?id=1463
Summary: Running nohup sleep 70 & and then exiting shell, hangs
ssh
Classification: Unclassified
Product: Portable OpenSSH
Version: 5.0p1
Platform: Sparc
OS/Version: Solaris
Status: NEW
Severity: normal
Priority: P2
Component:
2004 Feb 10
1
Dovecot on FreeBSD 4.9 - "Invalid Password Field"
Hi,
I am attempting to get dovecot up and running on FreeBSD 4.9..... Tried
with the default config file and my own one (below) but when trying to
login I get the following:
Feb 10 17:59:53 cobain dovecot-auth: passwd(jamie): invalid password
field '*'
It seems like it is trying to read straight from /etc/passwd? I thought
it called getpw().
Is this a common error and could anyone shed