Re: [Sks-devel] v3 keys w/(v4) subkeys still afflicting SKS

[Chris Kuethe]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The offending hashes have been removed from pgp.cns...

cd /home/sks
./bin/sks drop 08AA24E2F387480CB210BDCB873941FB
./bin/sks drop 13E37C592A17EA2A345ED114BEA5D281
./bin/sks drop 14D0F46517A209FB45E99D561CF4416C
...

worked for me

On Fri, 18 Jun 2004, Daniel Johnson wrote:

> > On Fri, 18 Jun 2004, Peter Palfrader wrote:
> > You can remove a key by hash using "sks drop <hash>".  The db process
> > need to be running while you do this.
> 
> I'd like to comply, but I keep getting "Wrong number of arguments: must
> specify exactly 1 hash".  I've tried
>   sks drop hash
>   sks drop "hash"
>   sks drop 'hash'
>   sks drop ha:..:..:..:sh
>   sks drop [hash]
> all from the root of the sks tree.
> 
> I've looked at sks_do.ml, but it wasn't very enlightening.  Running
> v1.0.7.  Hints appreciated!

- -- 
Chris Kuethe, GCIA CISSP: Secure Systems Specialist - U of A CNS
      office: 157 General Services Bldg.    +1.780.492.8135
              address@hidden

     GDB has a 'break' feature; why doesn't it have 'fix' too?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (OpenBSD)

iD8DBQFA07ju8bLxfOPbiw4RAlXCAJ49AHmyP9ELY4sT/iijJHFTRFf2FQCgvm/B
n67kSBOdlBFqnsuK0dyn4co=
=P8er
-----END PGP SIGNATURE-----