From: rmccabe@sourceware.org <rmccabe@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] conga ./conga.spec.in.in make/version.in
Date: 27 Mar 2007 17:14:47 -0000 [thread overview]
Message-ID: <20070327171447.11213.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: conga
Branch: RHEL4
Changes by: rmccabe at sourceware.org 2007-03-27 18:14:46
Modified files:
. : conga.spec.in.in
make : version.in
Log message:
- Changelog update
- Version bump
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/conga.spec.in.in.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.67.2.6&r2=1.67.2.7
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/make/version.in.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.28.2.3&r2=1.28.2.4
--- conga/conga.spec.in.in 2007/03/20 20:52:52 1.67.2.6
+++ conga/conga.spec.in.in 2007/03/27 17:14:45 1.67.2.7
@@ -289,6 +289,10 @@
%changelog
+* Tue Mar 27 2007 Stanko Kupcevic <kupcevic@redhat.com> 0.9.1-7
+- Fixed bz234196 (CVE-2007-0240 Conga includes version of Zope that is vulnerable to a XSS attack)
+- Resolves: bz234196
+
* Tue Mar 20 2007 Stanko Kupcevic <kupcevic@redhat.com> 0.9.1-6
- Do not fail on i18n machines
- Fixed bz225747 (Create/delete cluster - then access disk on node = Generic error on host: cluster tools: cman_tool errored)
--- conga/make/version.in 2007/03/20 20:52:53 1.28.2.3
+++ conga/make/version.in 2007/03/27 17:14:45 1.28.2.4
@@ -1,5 +1,5 @@
VERSION=0.9.1
-RELEASE=6
+RELEASE=7
# Remove "_UNRELEASED" at release time.
# Put release num at the beggining,
# so that after it gets released, it has
next reply other threads:[~2007-03-27 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 17:14 rmccabe [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-29 17:11 [Cluster-devel] conga ./conga.spec.in.in make/version.in rmccabe
2008-09-23 16:05 rmccabe
2006-08-03 20:54 kupcevic
2006-07-25 19:51 kupcevic
2006-06-27 21:15 kupcevic
2006-06-16 21:34 kupcevic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070327171447.11213.qmail@sourceware.org \
--to=rmccabe@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).