From: C H Forsyth <forsyth@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] sources cd images (was lp...)
Date: Wed, 9 Oct 2002 10:17:10 +0100 [thread overview]
Message-ID: <04a32340e38d0350f57c0d90513af11c@vitanuova.com> (raw)
>>Many such people do exist. In my experience more and more organizations are
>>restricting what ports are accessible to the outside world, in some cases
>>bringing these down to just HTTP and HTTPS.
even though more and more software systems seem to provide http tunnels
so that their RPC requests can pop up the other side of a firewall
presumably to allow people to get their work done.
(rob's earlier post on `Security' is relevant here.)
next reply other threads:[~2002-10-09 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 9:17 C H Forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-09 5:49 Russ Cox
2002-10-09 6:22 ` Dan Cross
2002-10-09 8:45 ` Adrian Tritschler
2002-10-08 16:20 Fco.J.Ballesteros
2002-10-08 16:11 Russ Cox
2002-10-09 3:44 ` Roman V. Shaposhnick
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=04a32340e38d0350f57c0d90513af11c@vitanuova.com \
--to=forsyth@vitanuova.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).