Daniel Braniss wrote:
On Aug 22, 2015, at 12:46 AM, Rick Macklem rmack...@uoguelph.ca wrote:
Yonghyeon PYUN wrote:
On Wed, Aug 19, 2015 at 09:00:35AM -0400, Rick Macklem wrote:
Hans Petter Selasky wrote:
On 08/19/15 09:42, Yonghyeon PYUN wrote:
On Wed, Aug 19, 2015 at 09:00:52AM
On Aug 22, 2015, at 12:46 AM, Rick Macklem rmack...@uoguelph.ca wrote:
Yonghyeon PYUN wrote:
On Wed, Aug 19, 2015 at 09:00:35AM -0400, Rick Macklem wrote:
Hans Petter Selasky wrote:
On 08/19/15 09:42, Yonghyeon PYUN wrote:
On Wed, Aug 19, 2015 at 09:00:52AM +0200, Hans Petter Selasky
On Sat, Aug 22, 2015 at 9:32 AM, Johan Hendriks joh.hendr...@gmail.com
wrote:
Last login: Sat Aug 22 17:05:52 2015 from 192.168.1.13
Could not chdir to home directory /restricted/testuser1: No such file or
directory
Cannot read termcap database;
using dumb terminal settings.
%
From here I
Am 22.08.2015 um 15:45 schrieb Brandon Allbery allber...@gmail.com:
On Sat, Aug 22, 2015 at 9:32 AM, Johan Hendriks joh.hendr...@gmail.com
wrote:
chroot is what it says on the tin: once set, the specified directory is
/. Every file accessed from that point on MUST be available from a
Hello all.
I want to use the Chrootdirctory feature of openssh on FreeBSD 10.2 And
I tried it on 10.1 but gave up...
Whatever I do I can not make it work on 10 without error messages, but I
got it working on FreeBSD 8
This is what I have in my /etc/ssh/sshd_config file.
# Example of overriding
=== procfs (cleandir)
rm -f export_syms procfs.ko procfs.kld procfs_ctl.o procfs_dbregs.o
procfs_fpregs.o procfs_ioctl.o procfs_map.o procfs_mem.o procfs_note.o
procfs_osrel.o procfs_regs.o procfs_rlimit.o procfs_status.o
procfs_type.o procfs.o procfs.ko.debug procfs.ko.symbols opt_compat.h
On Sat, Aug 22, 2015 at 10:54 AM, Rainer Duffner rai...@ultra-secure.de
wrote:
I found it’s much easier to have actual chroot’ed ssh users once the users
themselves are in an LDAP-directory.
Also, for doing anything useful on that shell, it turned out you need a
some more devices in /dev than
On 22/08/2015 15:01, Brandon Allbery wrote:
On Sat, Aug 22, 2015 at 10:54 AM, Rainer Duffner rai...@ultra-secure.de
wrote:
I found it’s much easier to have actual chroot’ed ssh users once the users
themselves are in an LDAP-directory.
Also, for doing anything useful on that shell, it turned
you can try one more thing. If there is a cd/dvd drive attached, see if
removing the sata connectors for that helps avoid the ahci timeouts. it may
not be the ssd at all.
Thx.
On Wed, Aug 19, 2015 at 9:19 AM, Dot Yet dot@gmail.com wrote:
Seems to be related to be related to your SSD drive
