Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#10275 - Apache Portable Runtime (APR) uses /dev/random

Attached to Project: Arch Linux
Opened by Alexander Veit (alexanderv) - Thursday, 24 April 2008, 20:10 GMT
Last edited by Greg (dolby) - Tuesday, 17 June 2008, 19:25 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Pierre Schmitz (Pierre)
Architecture All
Severity High
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
libapr seems to be built to use /dev/random instead of /dev/urandom as entropy source.

Even though using /dev/random is theoretically more secure than using /dev/urandom, to do so is generally not a good idea since /dev/random blocks if no random bits are available. This leads to severe performance degradation on servers that have no hardware random device.

Additional info:
* package version(s)
* config and/or log files etc.
apr-1.2.12-1

Steps to reproduce:
Access somewhat larger subversion repositories that are hosted on archlinux boxes.

Ref.:
http://subversion.tigris.org/issues/show_bug.cgi?id=2590
http://subversion.tigris.org/faq.html#slow-private-svnserve


This task depends upon

Closed by  Greg (dolby)
Tuesday, 17 June 2008, 19:25 GMT
Reason for closing:  Upstream
Additional comments about closing:  Fixed upstream
Comment by Pierre Schmitz (Pierre) - Friday, 25 April 2008, 12:08 GMT
I think this could be done. ATM apr does not compile with our toolchain and I have no time to look into it till mid of may.
Comment by Alexander Veit (alexanderv) - Saturday, 26 April 2008, 15:32 GMT
FYI: I've also filed a bug report on APR's bug database (https://issues.apache.org/bugzilla/show_bug.cgi?id=44881).
Comment by Greg (dolby) - Saturday, 17 May 2008, 14:25 GMT
Thanks to your report, its fixed upstream :)

Loading...