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

[Daniel Johnson]

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

address@hidden:~$ pidof sks
10042 10027
address@hidden:~$ v *sock
srwxr-xr-x    1 keyserv  keyserv         0 Jun 19 01:37 db_com_sock=
srwxr-xr-x    1 keyserv  keyserv         0 Jun 19 01:37 recon_com_sock=
address@hidden:~$ sks drop BF291C42AE681A88EDC2EDAB06A0A3B9
Wrong number of arguments: must specify exactly 1 hash

I just verified that the hash still exists and can be retrieved,
so this isn't a strange "hash not found" message.

Interestingly, it never complains if the hash length is wrong
unless I try the commands from another directory.  Then, of
course, I get:
Fatal error: exception Unix.Unix_error(20, "connect", "")

Thor is [mis-]behaving the same way.

I don't recall whether I got my source from a 1.0.7 tarball or
CVS.  Could that be the problem?

Daniel Johnson
address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFA1FPM6vGcUBY+ge8RAs++AKC+eNJ9vK1oxcREEqVBvB4OVWsVvgCbBivC
CCX5sEcEatWogWm51dQ68lw=
=vuS8
-----END PGP SIGNATURE-----