On Sun, Aug 21, 2005 at 09:01:40PM -0400, Yaron Minsky wrote:
> You can also use "sks drop" to delete keys that you know are bad. "sks drop"
> requires the "sks db" process to be running.
Not for unparseable keys, which these were. Again, check the archives.
--
Jason Harris | NIC:
You can also use "sks drop" to delete keys that you know are bad. "sks drop" requires the "sks db" process to be running.
yOn 8/21/05, Chris Kuethe <[EMAIL PROTECTED]> wrote:
On Sun, 21 Aug 2005, Jason Harris wrote:> On Sun, Aug 21, 2005 at 09:32:24AM -0600, Chris Kuethe wrote:>>> Not sure what's
On Sun, 21 Aug 2005, Jason Harris wrote:
On Sun, Aug 21, 2005 at 09:32:24AM -0600, Chris Kuethe wrote:
Not sure what's going on there...
Last reconciliation run was less than 10 minutes ago, and my keyserver
thinks it has all the keys that you have.
# ls -l diff-62.94.26.10_11371.txt
-rw-r--
On Sun, Aug 21, 2005 at 09:32:24AM -0600, Chris Kuethe wrote:
> Not sure what's going on there...
>
> Last reconciliation run was less than 10 minutes ago, and my keyserver
> thinks it has all the keys that you have.
>
> # ls -l diff-62.94.26.10_11371.txt
> -rw-r--r-- 1 sks sks 0 Aug 21 09:0
Not sure what's going on there...
Last reconciliation run was less than 10 minutes ago, and my keyserver
thinks it has all the keys that you have.
# ls -l diff-62.94.26.10_11371.txt
-rw-r--r-- 1 sks sks 0 Aug 21 09:08 diff-62.94.26.10_11371.txt
What if you remove the diff file? Does sks sh
