Re: [Sks-devel] a few diffs to sks

[Daniel Johnson]

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

On 28 Jan 2004 at 11:53, Chris Kuethe wrote:
> gpg --send-keys && gpg --refresh-keys
> 
> that was junk from local testing. What if I do have a whole pile of
> big keys (some are 1.2MB) to which photoids get added. That does
seem
> a bit insane though :) Chewing on 5MB of RSA/DSA ain't cheap.

I thought mass-uploads were discouraged, and that the transfers were
one key at a time.

> > Which brings up a related idea: What is the best way to throttle
> > up/downstream traffic?  Add options to sks_db & sks_recon, or
look
> > into kernel-side controls?  Some people may feel better with an
> > absolute cap on speed, even with good connections.
> 
> This would be handy. Exactly what kind of controls did you have in
> mind? B/s or keys/sec or ... ?

Bps.  For instance, since Thor is only semi-official at the office
I've told our firewall to limit the throughput to something like
64kbps on the SKS ports.  If it got hammered by a large transfer
while uncapped, one of our in-house busybody PHBs would make noise.

I suppose that since sks has to do some processing on inbound keys, a
keys/sec limit might not be a bad idea either.  Of course I haven't
the time or experience to examine/add such things, so I can't do much
more than make suggestions for now.  :)

Ah, that's why my message never showed up in the list.  I sent it to
you [Chris] directly.  Oops.

- -- 
Through the modem, off the server, over the T1, past the frame-relay,
< < NOTHIN' BUT NET > >
 
Daniel Johnson
address@hidden
http://dannyj.come.to/
Public PGP Keys & other info: http://dannyj.come.to/pgp/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32) - GPGshell v2.95

iD8DBQFAGU0G6vGcUBY+ge8RApAtAKCcUh0IwmCTSjQPpHy4czENwsGmJACg0oPo
zxNBAosmKjvQBvGo6IK4Sms=
=Gjdg
-----END PGP SIGNATURE-----