From: Ali-Reza Anghaie <ali@packetknife.com>
To: gentoo-dev@gentoo.org
Cc: steveb@nebcoinc.com
Subject: [gentoo-dev] RE: stackguard, formatguard, etc.
Date: 19 Feb 2002 04:40:11 -0500 [thread overview]
Message-ID: <1014111615.3452.12.camel@damascus.packetknife.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
Well, WireX hasn't yet released a modern Stackguard compiler. Don't know
how long it will be but I'm sure it's in the works. Cryptomark II is
still in development, I don't know where CM I stands even. Subdomain is
a pain to use. Formatguard is just fine..
I'd be interested to see a few things along that line as separate
ebuilds. Installing a Stackguard GCC3 along-side the current GCC would
be nice. Don't want to replace the default GCC.. just use the Stackguard
compiler on those things internet-facing. { And particular package
maintainers may choose to have Stackguard as a dependency. }
It occurred to me that using RH compilers might not be a bad idea (not
directly related to the above). I guess we'll have to wait-and-see what
this GCC 3.1 in Rawhide becomes.
I haven't looked at the GCC ebuilds to see what all patches are done but
RH at least keeps that aspect pretty clean. There is the whole binary
incompatibility issue which burns ppl but it's just a thought.
Anyhow... perhaps when WireX releases a GCC 3.x Stackguard we can
re-visit the issue?
-Ali
--
OpenPGP key 53F7FF5F
--
Well, you know boys, a nuclear reactor is a lot like a woman. You
just have to read the manual and press the right button.
-- Homer Simpson
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 240 bytes --]
next reply other threads:[~2002-02-19 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 9:40 Ali-Reza Anghaie [this message]
2002-02-21 18:20 ` [gentoo-dev] RE: stackguard, formatguard, etc Andreas Kinzl
2002-02-22 4:49 ` Ali-Reza Anghaie
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=1014111615.3452.12.camel@damascus.packetknife.com \
--to=ali@packetknife.com \
--cc=gentoo-dev@gentoo.org \
--cc=steveb@nebcoinc.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