> This is a DOS because Mallory could effectively increase Alice's
> public key to a size that it would be untenable for Bob to
> download it from the pool.
There are so many other, better ways to DoS the entire keyserver network
that I have real trouble taking this one seriously.
I think Kristia
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 17, 2015, Alain Wolf wrote:
>
> If you have Nginx in front of your SKS, uploads are limited to
> 1 MB by default or 8 MB if you follow Matt Rudes installation
> guide.
>
> SKS itself seems to have a hard-coded 5 MB limit (wserver.ml
> line 174).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am 17.05.2015 um 17:03 schrieb Alain Wolf:
> this blog post by Andy Steingruebl:
> http://securityretentive.blogspot.ch/2010/11/quick-clarification-on-hs
ts
> -http-strict.html
>
Sorry the link broke because of line-breaks introduced when signin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am 17.05.2015 um 23:29 schrieb Daniel Roesler:
> On May 17, 2015, Kristian Fiskerstrand wrote:
>>> 2. Prevents denial of service attacks that allows Mallory to
>>> spam a bunch of new subkeys, user ids, or huge images onto a
>>> public key.
>
>> P
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 17, 2015, Kristian Fiskerstrand wrote:
>> 2. Prevents denial of service attacks that allows Mallory to
>> spam a bunch of new subkeys, user ids, or huge images onto a
>> public key.
>
> Please elaborate on how this is a DoS, I can see it being
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 17, 2015, Kristian Fiskerstrand wrote:
> PS! Ironically your message itself has a bad signature, not
> sure if that was intended ironically or not.
Oh the joy of Gmail inserting line breaks where it wants... :P
Daniel
-BEGIN PGP SIGNATURE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/17/2015 10:47 PM, Daniel Roesler wrote:
> Howdy all,
>
> I'm sure by many of you have read the news that a very poorly
> generated 4096 RSA keypair was factored.
>
> Disclosure:
> http://trilema.com/2015/full-disclosure-4096-rsa-key-in-the-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Howdy all,
I'm sure by many of you have read the news that a very poorly
generated 4096 RSA keypair was factored.
Disclosure:
http://trilema.com/2015/full-disclosure-4096-rsa-key-in-the-strongset-factored/
Discussion: https://news.ycombinator.com/i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all
I don't suppose that a lot of people a affected by this. But it doesn't
look nice so I had to do something about it. Maybe some of you are
interested.
If the domain of your keyserver has strict HSTS enabled it may create a
problem for browse
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am 17.05.2015 um 06:52 schrieb Christian Felsing:
> Hi,
>
> I am wondering, if CAcert would offer CA solutions to handle this
> type of "special" applications. I can imagine a sub CA which offers
> a web service (authenticated by a specific client c
10 matches
Mail list logo
