@VM.MARIST.EDU>
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Auto login root on 3270 console ttyS0
I think that would be a problem. Indeed these solutions will not work when the
boot phase is stuck in INITRD.
We have had boot problems in the past, either because of an error in /etc/fstab
or because of boo
,
Berry van Sleeuwen
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Rick Troth
Sent: Wednesday, August 16, 2017 6:24 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Auto login root on 3270 console ttyS0
> sudo nor pmrun address the issue of the &quo
Dear Rick,
One slight embellishment...
On Wed, 16 Aug 2017, Rick Troth wrote:
Conflicting requirements between your security people and your
business continuity people. Lock them in a room together and let them
fight it out.
Either sell tickets or televise (pay-per-view :^)
Kindest
On 08/16/2017 12:04 PM, Donald Russell wrote:
> Our security model does not allow sudo. Instead we use something called
> pmrun which requires authentication across a network. (Don't get me started
> on the pitfalls of that)
PBRUN at least fits the model of "don't sign on as root - sign on as
Thanks Paul,
Our security model does not allow sudo. Instead we use something called
pmrun which requires authentication across a network. (Don't get me started
on the pitfalls of that)
sudo nor pmrun address the issue of the "*Enter root password for
maintenance, or CTL-D to continue*" prompt
> How/what do I have to configure so logging onto the 3270 console gets me
> logged into root in a bash shell automatically? Similar question for
> sometimes the system has problems coming up and it's prompting for
"Enter
> root password or CTL-D to continue". How can that be bypassed so it just
Greetings Donald,
The model that many debian packages has preferred over the years is that
of a "rootless" security model. In this configuration you must log in as
a user and then "sudo" to root. In order to do this you must be in the
sudoers group or be explicitly mentioned in
On 16 August 2017 at 00:47, Rick Troth wrote:
>
> It's arguable that having to enter a password at a "login:" prompt would
> actually be /less/ secure.
>
Indeed. It can be argued, and I did that a lot :-) A lot of the security
rituals we follow were created for problems that
login root on 3270 console ttyS0
>>> On 8/15/2017 at 06:17 PM, Donald Russell <russell@gmail.com> wrote:
> I run a SLES 11 (for emergency recovery) and RHEL 7 system on zVM
> 6.3/6.4
>
> Sysadmins can LOGON BY to get to the zLinux console if necessary.
>
> H
Thanks Mark, and others for the suggestions. I'll check those out.
Cheers,
Don
On Tue, Aug 15, 2017 at 15:28 Mark Post wrote:
> >>> On 8/15/2017 at 06:17 PM, Donald Russell
> wrote:
> > I run a SLES 11 (for emergency recovery) and RHEL 7 system on
Not that most users have it - but those with Class C have the ability to
talk to all the zLinux guests via CP SEND. So in a sense it is a console
just sitting there, but only those with class C can get in the room.
This privilege is hopefully covered by security policy elsewhere, ensuring
the
On 8/15/2017 at 06:17 PM, Donald Russell wrote:
>> I run a SLES 11 (for emergency recovery) and RHEL 7 system on zVM 6.3/6.4
>>
>> Sysadmins can LOGON BY to get to the zLinux console if necessary.
>>
>> How/what do I have to configure so logging onto the 3270 console gets
>>> On 8/15/2017 at 06:17 PM, Donald Russell wrote:
> I run a SLES 11 (for emergency recovery) and RHEL 7 system on zVM 6.3/6.4
>
> Sysadmins can LOGON BY to get to the zLinux console if necessary.
>
> How/what do I have to configure so logging onto the 3270 console gets
13 matches
Mail list logo