This is an update to the freeradius 1.0.0. Added a new patch that fixes a problem with the running of external programs with quoted arguments. Removed old patch.
Created attachment 37554 [details]
freeradius 1.0.0 ebuild
Created attachment 37555 [details, diff]
Patch to freeradius 1.0.0
fixes problem with running of external commands w/quoted args
Created attachment 39967 [details]
This ebuild contains several modifications:
- correction of use flag frnothred -> frnothread; However, in my opinion it
will be best to have just one global "thread" flag. After all, you could set
your flags on package level by using /etc/portage/package.use
- correction for bug #42718
- creation of radiusd user & group
- safe permissions on various directories
I've forget to mention in comment #3 that I've removed flag frlargefiles. Don't see the point in making support for large files selectable by user. I've took a peek in other ebuilds and saw everywhere that where it's the case, large file support is enabled.
reassigning to firstname.lastname@example.org since freeradius 1.0.1 addresses security issues:
"2004.09.14 v1.0.0 - Multiple external DoS attacks exist in the server. These are related to the attacks below, in 0.9.2, but were not caught then. The vulnerabilities are fixed in 1.0.1, and in all later versions of the server. The vulnerabilities are not exploitable, but can be used to remotely crash the server."
Multiple unspecified vulnerabilities have been reported in FreeRADIUS, which can be exploited by malicious people to cause a DoS (Denial of Service).
No more information is currently available.
Update to version 1.0.1 or later."
*** Bug 64738 has been marked as a duplicate of this bug. ***
net-dialup please bump.
*** Bug 57043 has been marked as a duplicate of this bug. ***
added and marked stable on x86
btw: good work alin ;)
This one is ready for GLSA. Security please draft.
Just checked out, it's not stable on x86.
freeradius-1.0.1.ebuild: KEYWORDS="~x86 ~amd64"
lanius: could you correct it ?
sorry, stable on x86, amd64 needn't mark it stable since the previous versions wasn't