From: David Dyck <dcd@TC.FLUKE.COM>
To: Mikey <jeffdb@netzone.com>
Cc: dahms@ifk20.mach.uni-karlsruhe.de, gnu-win32@cygnus.com
Subject: Re: Security hole in gnu-win32-gcc
Date: Thu, 11 Sep 1997 09:20:00 -0000 [thread overview]
Message-ID: <97Sep11.083107pdt.35783-1@gateway.fluke.com> (raw)
In-Reply-To: <34179c7e.111775356@smtp.netzone.com>
Quite a while ago I read the documents that described
the test that were done for the higher level security.
It assumed that Networking must have been turned off!
It also assumed that the ability to debug programs was
also turned off.
Obviously, the didn't plan on C2 developer security :-)
On Thu, 11 Sep 1997, Mikey wrote:
> Happens even on NT if system isn't configured for C2 security.
>
> +10% security -20% speed
>
> Don't you love Bill?
>
> On Thu, 11 Sep 1997 02:28:54 +0200 (METDST), you wrote:
>
> >Hi Daniel, you wrote:
> >
> >: I discovered a security hole in cygnus gnu-win32 gcc: Obviously,
> >: allocated ram is not initialised. The generated binaries thus contain
> >
> >W95 only. Shouldn't happen under NT, else it wouldn't be C2 certified.
> >
> >
> >Bye, Heribert (dahms@ifk20.mach.uni-karlsruhe.de)
> >-
> >For help on using this list (especially unsubscribing), send a message to
> >"gnu-win32-request@cygnus.com" with one line of text: "help".
> >
>
> (jeffdbREMOVETHIS@netzone.com)
> delete REMOVETHIS from the above to reply
> Mikey
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next prev parent reply other threads:[~1997-09-11 9:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <009BA1E2.EA079D00.23009@ifk20.mach.uni-karlsruhe.de>
1997-09-11 0:49 ` Mikey
1997-09-11 9:20 ` David Dyck [this message]
1997-09-11 10:00 Boatwright, Charles
1997-09-12 15:56 ` Geoffrey Noer
-- strict thread matches above, loose matches on Subject: below --
1997-09-10 10:28 Daniel Kroening
1997-09-11 10:00 ` jman
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=97Sep11.083107pdt.35783-1@gateway.fluke.com \
--to=dcd@tc.fluke.com \
--cc=dahms@ifk20.mach.uni-karlsruhe.de \
--cc=gnu-win32@cygnus.com \
--cc=jeffdb@netzone.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).