On 2/15/2012 5:03 AM, Michael Monnerie wrote:
Thanks, but it must have been a delay in DNS propagation, as I could
already resolve that. # ping sa.zmi.at PING sa.zmi.at (212.69.164.60)
56(84) bytes of data.
I believe you've got something working only locally. Try it from
another network. Perhaps a bind view?
As of 10:55AM EDT on 2:15, I see no A record checking my root-hint
servers or checking directly to one of your published nameservers.
ping sa.zmi.at
ping: unknown host sa.zmi.at
domain: zmi.at
registrant: IMA2683144-NICAT
admin-c: IMA2595008-NICAT
tech-c: IMA2595008-NICAT
nserver: dns1.zmi.at
remarks: 195.202.170.130
nserver: dns2.zmi.at
remarks: 212.69.162.196
changed: 20120214 14:36:21
source: AT-DOM
nslookup
> server dns1.zmi.at
Default server: dns1.zmi.at
Address: 195.202.170.130#53
>
> set type=aaaa
> sa.zmi.at.
Server: dns1.zmi.at
Address: 195.202.170.130#53
** server can't find sa.zmi.at: REFUSED
> set type=a
> sa.zmi.at.
Server: dns1.zmi.at
Address: 195.202.170.130#53
** server can't find sa.zmi.at: REFUSED
However, in short, what you do is you sign your releases and provide
the signature in ascii format in the .asc file and sha1 format in
.sha1 file.
The sha1 is already there. What I need is to generate a new gpg key with
which I can sign my channel. It should be an extra key as I need it on
several servers. So I need to create a new private key and public key,
export both into files.
The sign goes like
gpg -bas UPDATE_NUMBER.tar.gz
But how do I tell gpg to use a different key to sign that file?
I believe you can use the option "-r, --recipient name". So I would
have a key stored in my ring for that purpose.
During gpg --gen-key you specify the email address. I think you use
that with the -r option.
Regards,
KAM
