From: mehta kiran <kiranmehta1981@yahoo.com>
Subject: Re: problem mounting using NFSv4 when using -o sec=krb5  option
Date: Tue, 22 Mar 2005 07:39:03 -0800 (PST)
Message-ID: <20050322153903.42221.qmail@web51604.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: nfs@lists.sourceforge.net
To: Kevin Coffman <kwc@citi.umich.edu>
Sender: nfs-admin@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net

Hi Kevin , 
 This are some of the lines from your previos mails.
 Sorry , but i could not digest this lines.
------------------

if you create a principal using a password, you should
be able to 
authenticate as that pricipal using that password. 
However, once you 
do a ktadd for that principal the password will no
longer work.  See my 
previous message about what ktadd does.


P.S.  Here is what the ktadd command does:
- It generates a new random key value for the
  principal (with a new key version)
- It puts this new key into the Kerberos DB, replacing
  any previous key with a lower kvno
- It puts this new key into the keytab file that was
  specified

Therefore, each time you run ktadd, the old keytab
entry
becomes obsolete.
---------------------
Why(reason)should password become ineffective after
ktadd ?And if that is the case , why does it ask for
password during addprinc? continuing with this:what is
use of this password then?

thanks,
 --kiran


__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 


-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs