View Single Post
Posts: 1,680 | Thanked: 3,685 times | Joined on Jan 2011
#694
Originally Posted by RobbieThe1st View Post
Did I say it may? I don't recall seeing the word 'may' anywhere in that sentance...
That being said, I could have used 'this may produce a broken backup', but I felt that wasn't strong enough knowing how it works internally. 'this will produce a broken backup' is more correct, but leaves out the edge-cases(i.e. tar finished but locked up somehow). So "can and WILL" it is. I used that because I remember seeing that turn of phrase elsewhere and thought it sounded nice.

Edit: Oh, btw, does anyone know of a good way to take a plaintext password string and validate it against the (DES encrypted? ) passwd file? I can do everything but the encrypting of the password to compare... anyone know a tool that'll do that?
I was simply pointing out that the turn of phrase, while sounding nice is somwhat redundant. It is like saying:

Code:
f=1+(0.1)
i.e. Always true! Excuse my boole!

Surely you would attempt to decrypt the the encrypted data with the plaintext and then run some kind of check to to see that the decrypted output is logical, given the nature of DES you would simply have to check if the output file was garbage or not.

Is this what you are asking?

edit: oopz, misread what you said. nvm.

double edit: john the ripper, possibly in the repos as 'john'.

Also, as you are using busybox (?) in backup menu, can I have a shell as an option so I can run a forced FSCK on my file system?
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.

Last edited by vi_; 2011-04-14 at 14:22.