And the Starter System (Initial System) has very limited page and spool 
space, too...  And, if they are going to expand on the page and spool 
space, they really should know enough to get onto their own (hopefully 
secure) system.
 




"Huegel, Thomas" <[EMAIL PROTECTED]> 
Sent by: The IBM z/VM Operating System <[email protected]>
10/09/2007 01:20 PM
Please respond to
The IBM z/VM Operating System <[email protected]>


To
[email protected]
cc

Subject
Re: Initial User Directory ( was: hacking vm/cms (probably old news))







I'm sorry, but if I have to learn LINUX I think it only fitting that LINUX 
people learn a little VM.. Didn't we all have to learn VM at one time? and 
probably at least one other OS MVS or VSE.. 
Maybe IBM could supply a LINUX only directory using names like ROOT 
instead of MAINT. 
-----Original Message----- 
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] 
Behalf Of Thomas Kern 
Sent: Tuesday, October 09, 2007 12:09 PM 
To: [email protected] 
Subject: Re: Initial User Directory ( was: hacking vm/cms (probably old 
news)) 

unfortunately lots of new Linux-server VM systems are being run off that 
initial starter system. They deserve the most secure starter system that 
IBM can give them. 
/Tom Kern 
[EMAIL PROTECTED] wrote: 
> 
> Isn't that a bit of an overkill for a starter system?? 
> 
> 
> 
> 
> *Thomas Kern <[EMAIL PROTECTED]>* 
> Sent by: The IBM z/VM Operating System <[email protected]> 
> 
> 10/09/2007 10:00 AM 
> Please respond to 
> The IBM z/VM Operating System <[email protected]> 
> 
> 
> 
> To 
>       [email protected] 
> cc 
> 
> Subject 
>       Initial User Directory ( was: hacking vm/cms (probably old news)) 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> I would like it to go a step further, like with some linux installations 

> that ask for a root password and another userid to be added. I like 
> having ALL system related userids be AUTOONLY, LBYONLY, NOLOG or have a 
> randomly generated password. All userids that need to actually need to 
> be logged onto must have a LOGONBY record authorizing that initial 
> sysprog userid. After that initial setup, it isn't hard to replace the 
> passwords for those users that need to logged on. No one ever really 
> needs the password to those accounts if properly LOGONBY authorized. 
> That random password could be randomized daily, until you can properly 
> divide all accounts into the proper AUTOONLY, LBYONLY, NOLOG or personal 

> password categories. 
> 
> /Tom Kern 
> /301-903-2211 
> 
> 
> 
> Nick Laflamme wrote: 
>  > Robert Nix wrote: 
>  >> Hi Alan; 
>  >> 
>  >> Given that the starting CP Directory is dynamically created, for the 

> most 
>  >> part, today, how hard would it be to allow the installer to select a 

>  >> "root 
>  >> password" to be applied to all of the initial accounts? 
>  >> 
>  > 
>  > I'll go one step further: how about a default of all userids except 
>  > MAINT, OPERATOR, and CMSUSER (does that still ship on fresh system?) 
>  > being LBYONLY, defaulting to MAINT as the user who can do LOGONBY. 
>  > Anyone who wants a different LOGONBY user (or additional users) 
should 
>  > know which trivial XEDIT command will change that. 
>  > 
>  > Nick 
>  > 
> 

__________________________________________________________________ 
<< ella for Spam Control >> has removed VSE-List messages and set aside 
VM-List for me 
You can use it too - and it's FREE!  http://www.ellaforspam.com 

Reply via email to