StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3739907
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-09-18T00:41:37.713
FavoriteCount
0
LastActivityDate
2010-09-18T00:41:37.713
LastEditDate
LastEditorUserId
0
OwnerUserId
372643
ParentId
3738574
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
According to the <a href="http://packages.debian.org/changelogs/pool/main/a/apache2/apache2_2.2.9-10+lenny8/changelog" rel="noreferrer">Debian changelog</a>, you're using the apache2 package version 2.2.9-10+lenny8 (the latest one available for Lenny), built Apr 20 2010. Version 2.2.9-10+lenny6 had introduced a quick fix for the problem (CVE-2009-3555): <blockquote> Reject any client-initiated SSL/TLS renegotiations. This is a partial fix for the TLS renegotiation prefix injection attack (CVE-2009-3555). Any configuration which requires renegotiation for per-directory/location access control or uses "SSLVerifyClient optional" is still vulnerable. </blockquote> Therefore, you should disable <code>SSLVerifyClient optional</code> in <code>Directory</code> or <code>Location</code> directives. The TLS renegotiation extension (RFC 5746), which addresses the problem in <code>SSLVerifyClient optional</code> more generally, was implemented in OpenSSL versions 0.9.8m and 1.0.0a, which you would need if you wanted to use it. If you're not using <code>SSLVerifyClient optional</code> in location/directory directives, your configuration doesn't seem insecure, it just doesn't support this TLS extension that would have allowed you to keep using client-certificate authentication on a per-directory/location basis. <a href="http://www.apache.org/dist/httpd/CHANGES_2.2" rel="noreferrer">Apache Httpd 2.2.15</a> also introduced the <a href="http://httpd.apache.org/docs/2.2/mod/mod_ssl.html#sslinsecurerenegotiation" rel="noreferrer"><code>SSLInsecureRenegotiation</code></a> directive if you want to force the insecure behaviour (and use OpenSSL 0.9.8m or above).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POhttps: Apache TLS renegotiation: Debian, Apache2, openssl. How to?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USBruno
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POhttps: Apache TLS renegotiation: Debian, Apache2, openssl. How to?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.