×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Looks like we just have the defaults. I compared the /QOpenSys/QIBM/UserData/SC1/OpenSSH/etc/sshd_config to /QOpenSys/QIBM/ProdData/SC1/OpenSSH/etc_template/sshd_config and they are identical.
Here is the PrivilegeSeperationUser value:
UsePrivilegeSeparation sandbox
I'll check with my administrator and see if he can help me out.
Zach
-----Original Message-----
From: OpenSource [mailto:opensource-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Thursday, July 21, 2016 9:05 AM
To: IBMi Open Source Roundtable
Subject: Re: [IBMiOSS] Starting SSH Daemon
The e-mail below is from an external source. Please do not open attachments or click links from an unknown or suspicious origin.
Zach,
The configuration for the sshd is under:
/QOpenSys/QIBM/UserData/SC1/OpenSSH/etc/sshd_config
It sounds like someone tried to configure that file for "UsePrivilegeSeparation no", but accidentally typed "UserPrivilegeSeparation" instead of "UsePrivilegeSeparation"? The word "no" should be used to disable User Privilege Separation, it should not be used as a userid.
-SK
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.