Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Fri 25 Apr 2014, 04:21
All times are UTC - 4
 Forum index » House Training » Beginners Help ( Start Here)
Puppy does not wait for pup_save file password.
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 1 [14 Posts]  
Author Message
machare

Joined: 22 Dec 2007
Posts: 5

PostPosted: Sat 22 Dec 2007, 18:31    Post subject:  Puppy does not wait for pup_save file password.
Subject description: Pup_save file password prompt not working
 

I am running Puppy from a Kingston 2GB USB memory stick on an Asus P5B-V motherboard also with 2GB.

If I don't encrypt my save file I can save my settings etc and use them the next time without problem. (512MB pup_save file.)

If I encrypt the save file then when booting the PC does not stop and ask for a password. Rather it displays a PASSWORD prompt in blue followed by red text to the effect that the save file is corrupt and perhaps I would like to use the e2fsck -b 8193.

How can I persuade this puppy to ask for password before trying to open the pup_save file?
I was also expecting a menu where I could choose which save file to use!
Back to top
View user's profile Send private message 
PaulBx1

Joined: 16 Jun 2006
Posts: 2308
Location: Wyoming, USA

PostPosted: Sat 22 Dec 2007, 19:44    Post subject:  

Try making another encrypted pupsave. Maybe the last one got torqued some way.

What puppy version are you using anyway?

I might have to figure out a script to fsck encrypted pupsaves. It is kind of a fiddly manual process now.
Back to top
View user's profile Send private message 
machare

Joined: 22 Dec 2007
Posts: 5

PostPosted: Sat 22 Dec 2007, 20:15    Post subject:  

PaulBx1 wrote:
Try making another encrypted pupsave. Maybe the last one got torqued some way.
I tried several times with and without passwords, and wasted some time as I initially thought that it was the USB stick that was corrupt.

PaulBx1 wrote:
What puppy version are you using anyway?.
Should have said 3.01 (Just downloaded today)

PaulBx1 wrote:
I might have to figure out a script to fsck encrypted pupsaves. It is kind of a fiddly manual process now.
The way I see the problem is that the boot process does ask for a password before trying to process the pup_save file.

Thanks for your help
Back to top
View user's profile Send private message 
machare

Joined: 22 Dec 2007
Posts: 5

PostPosted: Sat 22 Dec 2007, 20:15    Post subject:  

PaulBx1 wrote:
Try making another encrypted pupsave. Maybe the last one got torqued some way.
I tried several times with and without passwords, and wasted some time as I initially thought that it was the USB stick that was corrupt.

PaulBx1 wrote:
What puppy version are you using anyway?.
Should have said 3.01 (Just downloaded today)

PaulBx1 wrote:
I might have to figure out a script to fsck encrypted pupsaves. It is kind of a fiddly manual process now.
The way I see the problem is that the boot process does not ask for a password before trying to process the pup_save file.

Thanks for your help
Back to top
View user's profile Send private message 
aarf

Joined: 30 Aug 2007
Posts: 3620
Location: around the bend

PostPosted: Wed 09 Jan 2008, 03:02    Post subject:  

I have this same problem too.
saved a heavy encrypted pup_save to a sda mounted USB flash.
got the nonstop boot with bad file message after the password-prompt. as above: "PASSWORD prompt in blue followed by red text to the effect that the save file is corrupt and perhaps I would like to use the e2fsck -b 8193."

copied the encrypted pup_save from sda to hda1 and the pup_save then booted correctly with password as is correct.

then copied the encrypted pup_save to a sda1 mounted flash drive and once again the pup_save mounted correctly.

so it seems it is a problem with sda mounts of (heavy?) encrypted pup_saves only.

a solution for sda mounts would be nice. there is nothing wrong with the sda USB as I use it in preference to boot puppy from. it is ext3.
Back to top
View user's profile Send private message Visit poster's website 
Pizzasgood


Joined: 04 May 2005
Posts: 6270
Location: Knoxville, TN, USA

PostPosted: Wed 09 Jan 2008, 17:16    Post subject:  

I ran into this last night, with a normal ide (hda) harddrive and both xor and aes encryption in 3.01. I looked at the code that mounts them and it looked correct, but I didn't look very hard. I haven't worked with the encrypted files in at least half a year so I'm pretty rusty.

Quote:
The way I see the problem is that the boot process does not ask for a password before trying to process the pup_save file.
There isn't an actual line in the boot scripts that requests the password. If I remember right, that happens automatically when the loopback device is set up. So the real problem is that the loobpack device is failing to be set up correctly. Without going in and testing, I don't know whether that's caused by a failure to detect the encryption method, a failure to load the correct modules, a glitch in the losetup app, or something else entirely.

If nothing more important comes up, I might take a closer look at it tonight or tomorrow.

_________________
Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

Back to top
View user's profile Send private message Visit poster's website 
Pizzasgood


Joined: 04 May 2005
Posts: 6270
Location: Knoxville, TN, USA

PostPosted: Wed 09 Jan 2008, 19:58    Post subject:  

This is the line where we're getting the problem:
losetup $CRYPTO /dev/loop1 /mnt/dev_save$PUPSAVEFILE
(note: that line occurs twice - once for if you want to resize the save file, and again for if you don't).

As for the problem itself, it's that losetup isn't honoring the '-e aes' and '-E 1' options (which are passed in through the $CRYPTO variable, but I tried hard-coding them too). Why? No idea.

What's weird is that if I use pfix=rdsh and try it after being dropped out, it works fine. But if I modify the init script to drop me out where the losetup is and try it, it doesn't work right.

I've compared lsmod from both locations and the same modules are loaded.

_________________
Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

Back to top
View user's profile Send private message Visit poster's website 
John Doe

Joined: 01 Aug 2005
Posts: 1689
Location: Michigan, US

PostPosted: Wed 09 Jan 2008, 22:32    Post subject:  

Pizzasgood wrote:
I've compared lsmod from both locations and the same modules are loaded.


is losetup the same?

is the variable $CRYPTO not getting passed over?

just trying to help you brainstorm. Very Happy
Back to top
View user's profile Send private message 
Pizzasgood


Joined: 04 May 2005
Posts: 6270
Location: Knoxville, TN, USA

PostPosted: Wed 09 Jan 2008, 23:27    Post subject:  

I just checked the md5sums. They're the same. As for the $CRYPTO, I set up an echo statement before to check that it was set. Even if it wasn't, I also tried hard-coding the exact command, with no variables at all.

I also checked to make sure the filesystem was actually mounted and the save-file accessible.

I have no more ideas.

_________________
Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

Back to top
View user's profile Send private message Visit poster's website 
PaulBx1

Joined: 16 Jun 2006
Posts: 2308
Location: Wyoming, USA

PostPosted: Thu 10 Jan 2008, 20:40    Post subject:  

I thought we are supposed to use losetup-FULL. Wasn't the busybox losetup lacking in features? Or is that old information? I use losetup-FULL in my convert-pupsave program...
Back to top
View user's profile Send private message 
Pizzasgood


Joined: 04 May 2005
Posts: 6270
Location: Knoxville, TN, USA

PostPosted: Thu 10 Jan 2008, 22:16    Post subject:  

In the initrd.gz stage of Puppy 3.01, the only losetup available is the full one. It just doesn't have the -FULL suffix.
_________________
Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

Back to top
View user's profile Send private message Visit poster's website 
PaulBx1

Joined: 16 Jun 2006
Posts: 2308
Location: Wyoming, USA

PostPosted: Fri 11 Jan 2008, 21:12    Post subject:  

What about the other variable, $PUPSAVEFILE? Could it be getting confused between your two cases?
Back to top
View user's profile Send private message 
Pizzasgood


Joined: 04 May 2005
Posts: 6270
Location: Knoxville, TN, USA

PostPosted: Fri 11 Jan 2008, 23:48    Post subject:  

I had an echo statement to make sure that was set correctly too.
Quote:
Even if it wasn't, I also tried hard-coding the exact command, with no variables at all.

I've been taking a break from this and working on some other stuff to let my brain empty. Depending on how long my next couple tasks take, I might do some more testing this weekend. Obviously there's some difference between when it's run normally and when it's run from using pfix=rdsh. I just need to figure out what that difference is. I've eliminated the command string and losetup itself, along with the module loadout. Maybe the modules themselves are different...

_________________
Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

Back to top
View user's profile Send private message Visit poster's website 
aarf

Joined: 30 Aug 2007
Posts: 3620
Location: around the bend

PostPosted: Wed 23 Jan 2008, 00:49    Post subject:  

variable length of hda and sda is three(3), variable length of sda1 and hda1 is four(4). is it this variable that is causing the problem somewhere?
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 1 of 1 [14 Posts]  
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » Beginners Help ( Start Here)
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0742s ][ Queries: 11 (0.0111s) ][ GZIP on ]