diff options
| author | remko <remko@FreeBSD.org> | 2006-08-13 03:44:22 +0800 |
|---|---|---|
| committer | remko <remko@FreeBSD.org> | 2006-08-13 03:44:22 +0800 |
| commit | c4da77cbe43305c99c9e9fc3ade04078873abd02 (patch) | |
| tree | e7108322507445024fb54bd9039cf1d9478a10c6 /security | |
| parent | 28f84a65fb494d53231547bf043584eecc4a1b65 (diff) | |
| download | freebsd-ports-gnome-c4da77cbe43305c99c9e9fc3ade04078873abd02.tar.gz freebsd-ports-gnome-c4da77cbe43305c99c9e9fc3ade04078873abd02.tar.zst freebsd-ports-gnome-c4da77cbe43305c99c9e9fc3ade04078873abd02.zip | |
OK after some more discussions with Simon it appeared that the ,2
marked all future releases of squirrelmail as vulnerable.
The negative side-effect of PORTEPOCH. Split the previous entry
into two seperated entries again, restoring the old entry for
squirrelmail, and having the 'new' entry for ja-squirrelmail.
This would grab any future versions of ja-squirrelmail if it were
to be readded, and does not conflict with future versions of
squirrelmail.
For more information about the portepoch discussion etc:
http://lists.freebsd.org/pipermail/freebsd-vuxml/2006-July/000185.html
Diffstat (limited to 'security')
| -rw-r--r-- | security/vuxml/vuln.xml | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/security/vuxml/vuln.xml b/security/vuxml/vuln.xml index 9a501bc9a0c3..c5ead6f315c5 100644 --- a/security/vuxml/vuln.xml +++ b/security/vuxml/vuln.xml @@ -39,9 +39,12 @@ Note: Please add new entries to the beginning of this file. <affects> <package> <name>ja-squirrelmail</name> - <name>squirrelmail</name> <range><ge>1.4.0</ge><lt>1.4.8,2</lt></range> </package> + <package> + <name>squirrelmail</name> + <range><ge>1.4.0</ge><lt>1.4.8</lt></range> + </package> </affects> <description> <body xmlns="http://www.w3.org/1999/xhtml"> |