Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.security > #4419 > unrolled thread
| Started by | Simon Josefsson <simon@josefsson.org> |
|---|---|
| First post | 2015-11-12 11:10 +0100 |
| Last post | 2015-11-12 11:10 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.debian.security
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Bug#803204: libiksemel: utterly insecure GNUTLS settings Simon Josefsson <simon@josefsson.org> - 2015-11-12 11:10 +0100
| From | Simon Josefsson <simon@josefsson.org> |
|---|---|
| Date | 2015-11-12 11:10 +0100 |
| Subject | Re: Bug#803204: libiksemel: utterly insecure GNUTLS settings |
| Message-ID | <qtWZk-7yp-7@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
I would suggest to use gnutls_set_default_priority() instead of hard-coding a priority string into applications. Your hard coded priority string will be just as obsolete as the hard coded values you are replacing in a couple of years. /Simon
Back to top | Article view | linux.debian.security
csiph-web