From: "rob pike, esq." <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] a bug in freopen
Date: Fri, 9 Aug 2002 08:36:01 -0400 [thread overview]
Message-ID: <d4ad7a48edaf81d8152a35ca53d1853d@plan9.bell-labs.com> (raw)
> It can be safely assumed that any really large software product
> contains bugs, period. One might as well set up a procedure to
> deal with them.. As to security flaws, there are numerous
> contributing factors.
Are you sure?
-rob
next reply other threads:[~2002-08-09 12:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 12:36 rob pike, esq. [this message]
2002-08-09 17:18 ` Douglas A. Gwyn
2002-08-10 16:14 ` Jim Choate
-- strict thread matches above, loose matches on Subject: below --
2002-08-06 2:38 presotto
2002-08-07 16:52 ` Jack Johnson
2002-08-08 15:39 ` Douglas A. Gwyn
2002-08-08 17:34 ` Jack Johnson
2002-08-09 8:57 ` Douglas A. Gwyn
2002-08-05 12:29 presotto
2002-08-05 9:55 Saroj Mahapatra
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=d4ad7a48edaf81d8152a35ca53d1853d@plan9.bell-labs.com \
--to=rob@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).