-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/11/2014 11:18 PM, Kristian Fiskerstrand wrote:
On 05/11/2014 10:43 PM, Kristian Fiskerstrand wrote:
On 05/06/2014 02:55 PM, Jeremy T. Bouse wrote:
On 05/06/2014 05:08 AM, Kristian Fiskerstrand wrote:
Dear lists,
Following the release of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/12/2014 07:40 AM, Gabor Kiss wrote:
In recognition of package-maintainers backporting the security
fixes to older versions of SKS for stable systems I'm revising
the latter statement a bit. I have now implemented a test for
affected
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/12/2014 01:34 AM, Jeremy T. Bouse wrote:
On 05/11/2014 05:18 PM, Kristian Fiskerstrand wrote:
On 05/11/2014 10:43 PM, Kristian Fiskerstrand wrote:
On 05/06/2014 02:55 PM, Jeremy T. Bouse wrote:
On 05/06/2014 05:08 AM, Kristian Fiskerstrand
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/06/2014 02:55 PM, Jeremy T. Bouse wrote:
On 05/06/2014 05:08 AM, Kristian Fiskerstrand wrote:
Dear lists,
Following the release of SKS 1.1.5[0] the following changes will
be made to the pools of sks-keyservers.net
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/11/2014 10:43 PM, Kristian Fiskerstrand wrote:
On 05/06/2014 02:55 PM, Jeremy T. Bouse wrote:
On 05/06/2014 05:08 AM, Kristian Fiskerstrand wrote:
Dear lists,
Following the release of SKS 1.1.5[0] the following changes
will be made to
On 05/11/2014 05:18 PM, Kristian Fiskerstrand wrote:
On 05/11/2014 10:43 PM, Kristian Fiskerstrand wrote:
On 05/06/2014 02:55 PM, Jeremy T. Bouse wrote:
On 05/06/2014 05:08 AM, Kristian Fiskerstrand wrote:
Dear lists,
Following the release of SKS 1.1.5[0] the following changes
will be made
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In recognition of package-maintainers backporting the security fixes
to older versions of SKS for stable systems I'm revising the latter
statement a bit. I have now implemented a test for affected servers
instead of relying on the version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/06/2014 11:22 PM, Phil Pennock wrote:
On 2014-05-06 at 17:53 +0200, Dinko Korunic wrote:
IMO delisting is fine as long as there is proper communication
involved and people actually are aware that's going on -- I'm
sure that not all the
On 05/06/2014 05:08 AM, Kristian Fiskerstrand wrote:
Dear lists,
Following the release of SKS 1.1.5[0] the following changes will be
made to the pools of sks-keyservers.net
subset.pool.sks-keyservers.net has been set to a minimum requirement
of SKS 1.1.5 with immediate effect.
Due to
Might I suggest that there be some time given for servers to be upgraded
before making this change? My servers run a stable baseline distro but I
deploy SKS via backported packaging which hasn't been upgraded and I'm
not going to compromise my system and run hand rolled source deployments
as
On 05/06/2014 05:08 AM, Kristian Fiskerstrand wrote:
Dear lists,
Following the release of SKS 1.1.5[0] the following changes will be
made to the pools of sks-keyservers.net
subset.pool.sks-keyservers.net has been set to a minimum requirement
of SKS 1.1.5 with immediate effect.
Due to
On Tue, 6 May 2014 14:58:48 +0200 (CEST), Gabor Kiss
ki...@ssg.ki.iif.hu wrote:
Might I suggest that there be some time given for servers to be upgraded
before making this change? My servers run a stable baseline distro but I
deploy SKS via backported packaging which hasn't been upgraded and
On 06.05.2014 11:08, Kristian Fiskerstrand wrote:
[...]
context / zone, however I'm giving this a grace period of (at
least) 45-60 days to allow server administrators to upgrade their
servers.
I'm not making any changes to the main pool at this point.
Hi,
If possible, I'd suggest actually
On 2014-05-06 at 17:53 +0200, Dinko Korunic wrote:
IMO delisting is fine as long as there is proper communication
involved and people actually are aware that's going on -- I'm sure
that not all the SKS administrators read the sks-devel on a
daily/weekly basis.
For clarity, this becomes:
14 matches
Mail list logo
