Valeri Galtsev wrote:
> On Wed, April 1, 2015 11:09 am, Andrew Holway wrote:
>>>
>>> This is all interesting, but I've got one dumb question: why do you
>>> need to decrypt it?
>>
>> In the UK we have a law which give you the right to remain silent; so as
>> not to incriminate yourself. I think in
On Wed, 2015-04-01 at 18:09 +0200, Andrew Holway wrote:
> >
> > This is all interesting, but I've got one dumb question: why do you need
> > to decrypt it?
> >
>
> In the UK we have a law which give you the right to remain silent; so as
> not to incriminate yourself. I think in the US its known a
On Wed, Apr 01, 2015 at 06:09:01PM +0200, Andrew Holway wrote:
> In the UK we have a law which give you the right to remain silent; so as
> not to incriminate yourself. I think in the US its known as "taking the
> fifth".
The UK RIPA act requires you to hand over decryption keys upon presentation
On Wed, April 1, 2015 11:09 am, Andrew Holway wrote:
>>
>> This is all interesting, but I've got one dumb question: why do you need
>> to decrypt it?
>>
>
> In the UK we have a law which give you the right to remain silent; so as
> not to incriminate yourself. I think in the US its known as "takin
>
> This is all interesting, but I've got one dumb question: why do you need
> to decrypt it?
>
In the UK we have a law which give you the right to remain silent; so as
not to incriminate yourself. I think in the US its known as "taking the
fifth".
___
C
Warren Young wrote:
> On Mar 30, 2015, at 11:08 PM, Jegadeesh Kumar wrote:
>> # Root password
>> rootpw --iscrypted $1$1SItJOAg$UM9n7lRFK1/OCs./rgQtQ/
>> # System authorization information
>> auth --useshadow --passalgo=sha512
>
> Those two settings are inconsistent. The $1 at the beginning of
On Mar 30, 2015, at 11:37 PM, Eero Volotinen wrote:
>
> Well, you could bruteforce sha512 hashed password or use dictionary attack
> against it.
The sad thing is that dictionary attacks still work. Just a few months ago on
this very mailing list, we had a big battle over whether the default pa
On Mar 30, 2015, at 11:08 PM, Jegadeesh Kumar wrote:
> # Root password
> rootpw --iscrypted $1$1SItJOAg$UM9n7lRFK1/OCs./rgQtQ/
> # System authorization information
> auth --useshadow --passalgo=sha512
Those two settings are inconsistent. The $1 at the beginning of that crypt(3)
string means i
On 03/31/2015 12:08 AM, Jegadeesh Kumar wrote:
<>
> Is there any way to decry pt the password and get it as plain text.
yes. but not inexpensive.
from this group;
http://www.openwall.com/
you will find;
http://www.openwall.com/john/pro/linux/
and a shell script for using;
http://linu
On 03/31/2015 06:08 PM, Jegadeesh Kumar wrote:
> I have the kick start file where my root password is store like
>
> # Root password
> rootpw --iscrypted $1$1SItJOAg$UM9n7lRFK1/OCs./rgQtQ/
> # System authorization information
> auth --useshadow --passalgo=sha512
>
> Is there any way to decry pt
2015-03-31 8:08 GMT+03:00 Jegadeesh Kumar :
> Hi Team,
>
> I have the kick start file where my root password is store like
>
>
> # Root password
> rootpw --iscrypted $1$1SItJOAg$UM9n7lRFK1/OCs./rgQtQ/
> # System authorization information
> auth --useshadow --passalgo=sha512
>
>
>
> Is there any
Hi Team,
I have the kick start file where my root password is store like
# Root password
rootpw --iscrypted $1$1SItJOAg$UM9n7lRFK1/OCs./rgQtQ/
# System authorization information
auth --useshadow --passalgo=sha512
Is there any way to decry pt the password and get it as plain text.
I know
12 matches
Mail list logo
