public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Elble <elbles@sessys.com>
To: Matthias Schniedermeyer <ms@citd.de>
Cc: xfs@oss.sgi.com
Subject: Re: Using xfsdump On Linux With IRIX Version 1 FS?
Date: Fri, 24 Jul 2009 15:13:20 -0400	[thread overview]
Message-ID: <C68F8010.B953%elbles@sessys.com> (raw)
In-Reply-To: <20090724171151.GA23077@citd.de>


[-- Attachment #1.1: Type: text/plain, Size: 2404 bytes --]

On 7/24/09 1:11 PM, "Matthias Schniedermeyer" <ms@citd.de> wrote:

> On 24.07.2009 11:36, Sean Elble wrote:
>> On 7/24/09 3:30 AM, "Matthias Schniedermeyer" <ms@citd.de> wrote:
>> 
>>> 
>>> I'd guess the disc isn't very big.
>>> 
>>> You just dd it completly (for backup).
>>> 
>>> Then search for the content of the shadow-file and blank out the entry
>>> with a hex-editor. Make sure that you don't change the filesize, pad
>>> the previous/following entry with any character you have to remove.
>> 
>> Right, the disk is only 2 GB.  Presumably, to back the disk up, all I'd have
>> to do would be something like:
>> 
>>     dd if=/dev/sda of=IRIXbackup
>> 
>> Correct?  No need to specify bs or count, I presume...
> 
> Exactly.
> 
>> Then, I could use hexedit in the following manner to edit the disk:
>> 
>>     hexedit -d -f /dev/sda
> 
> Don't know hexedit. Last time i used a hex editor it was "khexedit",
> worked good enough.
> 
>> I suppose I could search for the encrypted password string itself, but as
>> Chris Wedgwood suggested, I might be better off finding the offset of the
>> /etc/shadow file by doing something like the following:
>>     
>>     xfs_ncheck /dev/sda | grep /etc/shadow
>> 
>> I'm not sure if I can use the inode number directly as an offset or not, but
>> I *think* I could use it in conjunction with a xfs_db convert command to get
>> something usable as an offset.  Something like the following, perhaps?
>> 
>>     xfs_db -c convert inode <inode from xfs_ncheck command> daddr /dev/sda
> 
> 2GB is small enough to just use "brute force".
> 
> - Make a backup-copy of the image
> - Open the image in a/the hexeditor
> - Search for something that appears in the shadow file
>   it should be pretty obvious if the hit is inside the shadow file.
> - Make the changes, (Remember filesize has to stay the same!)
> - dd the image back to the HDD.
> 
> Not very complicated and it still shouldn't take too long. :-)
> 

Yeah, that's probably what I'll do then.  I figure the disk will thrash for
a while during the search for a string in /etc/shadow, but hopefully it'll
work.  Thanks for all the advice!

-Sean

-- 
+-------------------------------------------------
|  Sean Elble      
|  Virginia Tech, Class of 2009
|  E-Mail:   elbles@sessys.com
|  Web:      http://www.sessys.com/~elbles/
|  Cell:     860.946.9477
+-------------------------------------------------

[-- Attachment #1.2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2139 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-07-24 19:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23 23:57 Using xfsdump On Linux With IRIX Version 1 FS? Sean Elble
2009-07-24  2:23 ` Eric Sandeen
2009-07-24  3:02   ` Sean Elble
2009-07-24  3:32   ` Sean Elble
2009-07-24  7:30     ` Matthias Schniedermeyer
2009-07-24 15:36       ` Sean Elble
2009-07-24 17:11         ` Matthias Schniedermeyer
2009-07-24 19:13           ` Sean Elble [this message]
2009-07-25  3:53             ` Christian Kujau
2009-07-25  7:26               ` Matthias Schniedermeyer
2009-07-25  9:46                 ` Christian Kujau
2009-07-25 10:22                   ` Matthias Schniedermeyer
2009-07-25 10:36                     ` Christian Kujau
2009-07-25 16:25                   ` Sean Elble
2009-07-26  0:24                   ` Sean Elble
2009-07-24  8:23     ` Andi Kleen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C68F8010.B953%elbles@sessys.com \
    --to=elbles@sessys.com \
    --cc=ms@citd.de \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox