Your message dated Sat, 24 Feb 2018 04:36:04 +0000
with message-id <>
and subject line Bug#891248: Removed package(s) from unstable
has caused the Debian Bug report #456667,
regarding pound: spends too much time generating SSL keys
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Package: pound
Version: 2.2.7-2
Severity: normal

I noticed that pound was using far more CPU time than the backend
servers behind it, which struck me as strange.

Upon investigation it appears that it regenerates 2 x 11 RSA keys every
300 seconds. On my not too shabby system that takes about 5 seconds, or
20 minutes every day.

Now this may be a good thing security-wise, but I'm not even using pound
for SSL connections!  Only plain HTTP connections go through it. It also
removes entropy from the pool for things that need it, which IMHO is

I modified my local copy to only regenerate every 24 hours, and that's
much better. However, a couple of suggestion came to mind:

- only regenerate keys that have actually been used
- make the regeneration period configurable
- why 11 times? Why not 10, or 12, or 16? Make this configurable?

Paul Slootman

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (650, 'testing'), (625, 'stable'), (600, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-rc5
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

--- End Message ---
--- Begin Message ---
Version: 2.7-1.3+rm

Dear submitter,

as the package pound has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see

The version of this package that was in Debian prior to this removal
can still be found using

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing

Debian distribution maintenance software
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to