Thanks. Unfortunately, running fdisk -p (-l is an invalid option) tells me the "fdisk: mounted root fs resource doesn't match expectations (regexec returned 1)"<div><br></div><div>Editing the /etc/shadow file requires getting past the problem with not being able to mount the slice rw.</div>
<div><div><br clear="all">-Mathew<br><br>"When you do things right, people won't be sure you've done anything at all." - God; Futurama<div><br></div><div>"<span style="background-color:rgb(255,255,255);font-family:arial,sans-serif;font-size:13px;line-height:18px">We'll get along much better once you accept that you're wrong and neither am I." - Me</span></div>
<br>
<br><br><div class="gmail_quote">On Tue, Oct 23, 2012 at 3:01 PM, Josh Boon <span dir="ltr"><<a href="mailto:j@80ok.be" target="_blank">j@80ok.be</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div style="font-size:10pt;font-family:arial,helvetica,sans-serif">I've never booted a FreeBSD system but from my rough googling you could just edit the hash directly.<div><br></div><div>This md5 password hash would do for now. The password is averageavenger</div>
<div><div>#password generating command used</div><div>md5pass averageavenger B32eK3KY</div><div>#hash</div><div>$1$B32eK3KY$dfZf8QJCEwQDNRJoapUEI/</div><div><br></div><div>You'd have to find the physical device you're interested in </div>
<div>#a good start</div><div>fdisk -l</div><div><br></div><div>and mount it directly to somewhere in the filesystem and then just edit the etc/shadow file in the mounted filesystem replacing the full hash for root with the one above and then you would login in using averageavenger as the pass when you reboot. Do copy the shadow file </div>
<div>cp etc/shadow{,.old}</div><div>first. </div><div><br></div><div>All the best,</div><div>Josh</div><div><br></div><div><br></div><br><hr><div style="font-size:12pt;font-style:normal;font-family:Helvetica,Arial,sans-serif;text-decoration:none;font-weight:normal">
<b>From: </b>"Mathew Snyder" <<a href="mailto:mathew.snyder@gmail.com" target="_blank">mathew.snyder@gmail.com</a>><br><b>To: </b>"Richard E.MGH Morse" <<a href="mailto:REMORSE@partners.org" target="_blank">REMORSE@partners.org</a>><br>
<b>Cc: </b>"Bblisa@Bblisa. Org" <<a href="mailto:bblisa@bblisa.org" target="_blank">bblisa@bblisa.org</a>>, "<<a href="mailto:kurin@delete.org" target="_blank">kurin@delete.org</a>>" <<a href="mailto:kurin@delete.org" target="_blank">kurin@delete.org</a>><br>
<b>Sent: </b>Tuesday, October 23, 2012 2:50:23 PM<br><b>Subject: </b>Re: [BBLISA] Reset root password on FreeBSD<div><div class="h5"><br><br>I tried the toor option. Didn't work. I guess these people are smarter than the average vendor. ;)<div>
<br></div><div>I've booted to installation media and selected the single-user mode. I've got the shell but when I attempt to follow the steps I've found on various sites it doesn't work. Generally, they all follow the same procedure:</div>
<div><br></div><div>mount -a (or mount -u /)</div><div>passwd</div><div><br></div><div>However, this doesn't accomplish anything. when I look at df I'm only seeing the installation media and devfs as mounted. I looked at /dev but can't make out which, if any, of the entries are the partition I'm trying to mount.</div>
<div><br></div><div>When I run passwd it seems to be executing from the installation media as it fails to change the password due to what I've ascertained is a problem making changes to a read-only filesystem. After I ran mount -o rw -a I get the same result.</div>
<div><br></div><div>Any further help is appreciated.</div><div>-Mathew<br><br>"When you do things right, people won't be sure you've done anything at all." - God; Futurama<div><br></div><div>"<span>We'll get along much better once you accept that you're wrong and neither am I." - Me</span></div>
<br>
<br><br><div class="gmail_quote">On Tue, Oct 23, 2012 at 1:53 PM, Morse, Richard E.MGH <span dir="ltr"><<a href="mailto:REMORSE@partners.org" target="_blank">REMORSE@partners.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
You might also try using the 'toor' account -- this usually exists on FreeBSD, although I forget if it needs a password -- but if the vendor isn't paying attention they might have left this account unrestricted.<br>
<br>
Ricky<br>
<div><div><br>
On Oct 23, 2012, at 11:50 AM, Mathew Snyder wrote:<br>
<br>
> Thanks guys. I'm downloading an ISO right now.<br>
><br>
> -Mathew<br>
><br>
> "When you do things right, people won't be sure you've done anything at<br>
> all." - God; Futurama<br>
><br>
> "We'll get along much better once you accept that you're wrong and neither<br>
> am I." - Me<br>
><br>
><br>
><br>
> On Tue, Oct 23, 2012 at 11:48 AM, <<a href="mailto:kurin@delete.org" target="_blank">kurin@delete.org</a>> wrote:<br>
><br>
>> I haven't *tested* this, but I'm 99% sure it works:<br>
>><br>
>> 1. Download a copy of the 9.0 install media.<br>
>> 2. Boot to the 'live CD' option.<br>
>> 3. Mount the root fs somewhere.<br>
>> 4. chroot into it.<br>
>> 5. `passwd`<br>
>><br>
>> It's *possible* but not likely that the live CD will also want a password,<br>
>> in which case you can choose 'shell' instead of 'live CD'.<br>
>><br>
>> On Tue, Oct 23, 2012 at 11:21:11AM -0400, Mathew Snyder wrote:<br>
>>> We have a single FreeBSD server installed by a vendor. They have let it<br>
>> sit<br>
>>> idle for who knows how long before coming around for a full<br>
>> configuration.<br>
>>> In that time, their default admin account has expired and no one kept<br>
>> track<br>
>>> of the root password. Now it needs to be reset.<br>
>>><br>
>>> Unfortunately, they configured single-user mode to require said root<br>
>>> password. This is quite a hinderance, naturally. I'm not familiar with<br>
>> the<br>
>>> BSDs. Can someone point me in the direction of instructions for reseting<br>
>> a<br>
>>> password with boot media or something. Everything I've found online so<br>
>> far<br>
>>> assumes no password for single-user mode.<br>
>>><br>
>>> -Mathew<br>
>>><br>
>>> "When you do things right, people won't be sure you've done anything at<br>
>>> all." - God; Futurama<br>
>>><br>
>>> "We'll get along much better once you accept that you're wrong and<br>
>> neither<br>
>>> am I." - Me<br>
>><br>
>>> _______________________________________________<br>
>>> bblisa mailing list<br>
>>> <a href="mailto:bblisa@bblisa.org" target="_blank">bblisa@bblisa.org</a><br>
>>> <a href="http://www.bblisa.org/mailman/listinfo/bblisa" target="_blank">http://www.bblisa.org/mailman/listinfo/bblisa</a><br>
>><br>
>><br>
>><br>
> _______________________________________________<br>
> bblisa mailing list<br>
> <a href="mailto:bblisa@bblisa.org" target="_blank">bblisa@bblisa.org</a><br>
> <a href="http://www.bblisa.org/mailman/listinfo/bblisa" target="_blank">http://www.bblisa.org/mailman/listinfo/bblisa</a><br>
<br>
<br>
<br>
</div></div>The information in this e-mail is intended only for the person to whom it is<br>
addressed. If you believe this e-mail was sent to you in error and the e-mail<br>
contains patient information, please contact the Partners Compliance HelpLine at<br>
<a href="http://www.partners.org/complianceline" target="_blank">http://www.partners.org/complianceline</a> . If the e-mail was sent to you in error<br>
but does not contain patient information, please contact the sender and properly<br>
dispose of the e-mail.<br>
<br>
</blockquote></div><br></div>
<br>_______________________________________________<br>bblisa mailing list<br><a href="mailto:bblisa@bblisa.org" target="_blank">bblisa@bblisa.org</a><br><a href="http://www.bblisa.org/mailman/listinfo/bblisa" target="_blank">http://www.bblisa.org/mailman/listinfo/bblisa</a></div>
</div></div><br></div></div></div></blockquote></div><br></div></div>