From: Gerald Pfeifer <gerald@pfeifer.com>
To: Caroline Tice <cmtice@google.com>
Cc: Richard Earnshaw <rearnsha@arm.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Add vtable verification feature announcement to news on main page...
Date: Fri, 10 Apr 2015 23:55:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1504110153490.9357@tuna.site> (raw)
In-Reply-To: <CABtf2+TYp0+sDhr+20hDik0Y_z_sXW4XsabvM9nxMgXn+SOKTg@mail.gmail.com>
On Sun, 8 Sep 2013, Caroline Tice wrote:
> I believe I have addressed all the issues with the Vtable Verification
> feature. I have updated the announcement patch, and have attached the
> updated patch. Is this OK to commit?
Eeh, I just noticed nobody ever applied the patch below. :-(
Sorry about that.
It's too late for the main page now, but can you push this
into the appropriate place of news.html (or let me know, and
I'll do it)?
Gerald
Index: htdocs/index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/index.html,v
retrieving revision 1.890
diff -r1.890 index.html
55a56,64
> <dt><span>The Vtable Verification Feature is now in GCC</span>
> <span class="date">[2013-09-08]</span></dt>
> <dd>The <a href="http://gcc.gnu.org/wiki/vtv">vtable verification</a>
> branch has been merged into trunk. This adds a new security feature
> for C++ programs, to detect/prevent vtable pointer corruption or attacks.
> For more details see the documentation on the feature wiki page. This work
> was contributed by Caroline Tice, Luis Lozano and Geoff Pike of Google,
> and Benjamin Kosnik of Red Hat.</dd>
>
next prev parent reply other threads:[~2015-04-10 23:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 17:19 Caroline Tice
2013-08-08 16:00 ` Richard Earnshaw
2013-09-09 2:45 ` Caroline Tice
2015-04-10 23:55 ` Gerald Pfeifer [this message]
2015-04-10 23:58 ` Caroline Tice
2015-04-11 12:28 ` Gerald Pfeifer
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=alpine.LSU.2.20.1504110153490.9357@tuna.site \
--to=gerald@pfeifer.com \
--cc=cmtice@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rearnsha@arm.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).