Re: Using signify into shell script

2017-07-15 Thread Ted Unangst 
Stephane HUC PengouinBSD wrote:
> 
> $ signify -G -p Test.pub -s Test.sec
> passphrase:
> signify: please provide a password
> $ ls -al | egrep Test
> $
> 
> If not entry password, key files are not created!

you can create keys without passphrases using -n.

Re: Using signify into shell script

2017-07-15 Thread Stephane HUC "PengouinBSD" 


Le 07/15/17 à 14:30, Stuart Henderson a écrit :
> On 2017-07-15, Stephane HUC "PengouinBSD" <b...@stephane-huc.net> wrote:
>> This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
>> --96VlOUuKePF5djM1twvqfOX9BiuExBLDd
>> From: "Stephane HUC \"PengouinBSD\"" <b...@stephane-huc.net>
>> Reply-To: b...@stephane-huc.net
>> To: misc@openbsd.org
>> Message-ID: <bb0f15c9-8fb1-c94d-e757-05b48db30...@stephane-huc.net>
>> Subject: Using signify into shell script
>> Content-Type: text/plain; charset=utf-8
>> Content-Transfer-Encoding: quoted-printable
>> Content-Language: fr-xx-classique+reforme1990
>>
>> Hi, all.
>>
>> I  use signify tool on few projects, into ksh script.
>>
>> When i use as:
>>
>> signify -S -s "${dir_sec_key_signify}" -m "ProjectName.sha512" -e -x
>> "ProjectName.sha512.sig"
>>
>> the invite ask the passphrase. normal!
>>
>> If i use cron task, how can i inject passphrase for signify?
> 
> Is there any advantage to doing that - wouldn't it be equally safe
> to just use a key with no passphrase?
> 
> 

Because:

$ signify -G -p Test.pub -s Test.sec
passphrase:
signify: please provide a password
$ ls -al | egrep Test
$

If not entry password, key files are not created!


-- 
~ " Fully Basic System Distinguish Life! " ~ " Libre as a BSD " +=<<<

Stephane HUC as PengouinBSD or CIOTBSD
b...@stephane-huc.net



signature.asc
Description: OpenPGP digital signature

Re: Using signify into shell script

2017-07-15 Thread Stuart Henderson 
On 2017-07-15, Stephane HUC "PengouinBSD" <b...@stephane-huc.net> wrote:
> This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
> --96VlOUuKePF5djM1twvqfOX9BiuExBLDd
> From: "Stephane HUC \"PengouinBSD\"" <b...@stephane-huc.net>
> Reply-To: b...@stephane-huc.net
> To: misc@openbsd.org
> Message-ID: <bb0f15c9-8fb1-c94d-e757-05b48db30...@stephane-huc.net>
> Subject: Using signify into shell script
> Content-Type: text/plain; charset=utf-8
> Content-Transfer-Encoding: quoted-printable
> Content-Language: fr-xx-classique+reforme1990
>
> Hi, all.
>
> I  use signify tool on few projects, into ksh script.
>
> When i use as:
>
> signify -S -s "${dir_sec_key_signify}" -m "ProjectName.sha512" -e -x
> "ProjectName.sha512.sig"
>
> the invite ask the passphrase. normal!
>
> If i use cron task, how can i inject passphrase for signify?

Is there any advantage to doing that - wouldn't it be equally safe
to just use a key with no passphrase?

Using signify into shell script

2017-07-15 Thread Stephane HUC "PengouinBSD" 
Hi, all.

I  use signify tool on few projects, into ksh script.

When i use as:

signify -S -s "${dir_sec_key_signify}" -m "ProjectName.sha512" -e -x
"ProjectName.sha512.sig"

the invite ask the passphrase. normal!

If i use cron task, how can i inject passphrase for signify?



-- 
~ " Fully Basic System Distinguish Life! " ~ " Libre as a BSD " +=<<<

Stephane HUC as PengouinBSD or CIOTBSD
b...@stephane-huc.net



signature.asc
Description: OpenPGP digital signature