invalidate the nvram first and make sure you set the secstore password correctly to the one that you have set for hostowner's user in secstored when it asks you on the next reboot. if you have done already then simply cat the nvram partition: you should be able to see it in full and in plain text and see if it's truncated.
if the system and secstore passwords are different for hostowner perhaps there may be a bug in parsing the nvram. they are the same around here so i've never tested that condition. On 7/27/07, erik quanstrom <[EMAIL PROTECTED]> wrote: > i get this error > > ladd# auth/secstore -nG factotum > ladd# echo $status > secstore 1517: invalid password in nvram > > however if i do it this way, it works: > > ladd# auth/secstore -G factotum > secstore password: <same password entered> > secstore > <keys printed here> > > i have a longish password, but it doesn't exceed ANAMELEN. > does nvram truncate the password? are there any magic characters > which must be avoided? > > - erik >
