X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C87A20.597757A6@onstor-exch02.onstor.net>; Thu, 28 Feb 2008 08:41:13 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C87A20.597757A6"
Content-class: urn:content-classes:message
Subject: RE: Cougar migration issue
Date: Thu, 28 Feb 2008 08:36:58 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E12BFA8@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Cougar migration issue
Thread-Index: Ach53ftt8qxQC/FMQDquteiXN4SGZAAQcWPZ
From: "Narain Ramadass" <narain.ramadass@onstor.com>
To: "Tim Gardner" <tim.gardner@onstor.com>,
	"dl-Cougar" <dl-Cougar@onstor.com>
Cc: "Sripal Surendiran (HCL)" <sripal.surendiran@onstor.com>,
	"Sudharsan Srinivasan" <sudharsan@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C87A20.597757A6
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Tim,

Another alternative we had discussed last time was to reset the =
passwords for the root and admin accounts to their ONStor defaults and =
add an expiry date for the password such that the next login by the =
respective users would force them to change the password.

I do not believe that we store anything except admin and root in the =
passwd file - but then ONStor created ID's show up to BSD as "admin". =
Therefore if I logged in as "ndmp", "who" run from BSD would show an =
instance of "admin" having logged in. This may need a bit of testing and =
validation IMHO.

My 2c.

Narain.


-----Original Message-----
From: Tim Gardner
Sent: Wed 2/27/2008 11:53 PM
To: dl-Cougar
Cc: Sripal Surendiran (HCL); Sudharsan Srinivasan
Subject: Cougar migration issue
=20
Folks,
=20
There is a migration issue regarding the password file.
The format (blowfish) used on BSD is not supported on our Linux =
distribution.
How important is this?
Do we store any passwords in this file other than the passwords for the =
admin and root users?
If not, would it be sufficient to just prompt the user for these =
passwords during migration?
=20
Tim
=20


------_=_NextPart_001_01C87A20.597757A6
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>RE: Cougar migration issue</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Tim,<BR>
<BR>
Another alternative we had discussed last time was to reset the =
passwords for the root and admin accounts to their ONStor defaults and =
add an expiry date for the password such that the next login by the =
respective users would force them to change the password.<BR>
<BR>
I do not believe that we store anything except admin and root in the =
passwd file - but then ONStor created ID's show up to BSD as =
&quot;admin&quot;. Therefore if I logged in as &quot;ndmp&quot;, =
&quot;who&quot; run from BSD would show an instance of &quot;admin&quot; =
having logged in. This may need a bit of testing and validation =
IMHO.<BR>
<BR>
My 2c.<BR>
<BR>
Narain.<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Tim Gardner<BR>
Sent: Wed 2/27/2008 11:53 PM<BR>
To: dl-Cougar<BR>
Cc: Sripal Surendiran (HCL); Sudharsan Srinivasan<BR>
Subject: Cougar migration issue<BR>
<BR>
Folks,<BR>
<BR>
There is a migration issue regarding the password file.<BR>
The format (blowfish) used on BSD is not supported on our Linux =
distribution.<BR>
How important is this?<BR>
Do we store any passwords in this file other than the passwords for the =
admin and root users?<BR>
If not, would it be sufficient to just prompt the user for these =
passwords during migration?<BR>
<BR>
Tim<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C87A20.597757A6--
