1 |
Thanks for the replies |
2 |
|
3 |
I have done some further reading on the matter and seem to have come |
4 |
across a paradox of sorts. |
5 |
What got me intersted was that an article claiming that the hash |
6 |
tables may be used for "evil " purposes but it was pointed out to me |
7 |
that without the hash you have no comparison so what use is a hash |
8 |
table, indeed you would also have had to gain access to the |
9 |
/etc/shadow file to get the hash and since that requires root |
10 |
priviledge it would seem you allready have a larger problem than |
11 |
losing a password to clear text. |
12 |
Of course I am only thinking of a remote login via 22 as that is what |
13 |
primarily concerns me at the moment. So in short it seems I am safe |
14 |
with my system as it is for now. |
15 |
|
16 |
stu |
17 |
|
18 |
ps on a side note |
19 |
NBS DES |
20 |
National Bureau of Standards Data Encryption Standard |
21 |
http://www.garykessler.net/library/crypto.html#desmath |
22 |
|
23 |
|
24 |
|
25 |
On 15/11/05, stian@×××××.no <stian@×××××.no> wrote: |
26 |
> > Fields are separated by a semicolon. So in the first one you have the |
27 |
> > username, and in the second one there is the encrypted password but |
28 |
> > this field is again separated in three new fields by a $ sign. So the |
29 |
> > first one (1 in this case) is the encryption algorithm used (I'll have |
30 |
> |
31 |
> $1$ meens MD5 (with salt). glibc crypt() function also reflects this. If |
32 |
> the salt format doesn't match $1$xxxxxxx$ format, DES encryption is |
33 |
> assumed, which has a very weak salt. |
34 |
> |
35 |
> |
36 |
> Stian Skjelstad |
37 |
> -- |
38 |
> gentoo-security@g.o mailing list |
39 |
> |
40 |
> |
41 |
|
42 |
|
43 |
-- |
44 |
"There are 10 types of people in this world: those who understand |
45 |
binary, those who don't" |
46 |
|
47 |
--Unknown |
48 |
|
49 |
-- |
50 |
gentoo-security@g.o mailing list |