From: Rufiao <rufiao@gmx.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] RFP: System to account users configurations
Date: Sun, 16 Jun 2002 21:12:59 -0300 [thread overview]
Message-ID: <20020616211259.6d5f4544.rufiao@gmx.net> (raw)
In-Reply-To: <F203h9IdDJLyyErMLrE000033ef@hotmail.com>
Using https is not a big deal, but how would it help on this problem?
On Sun, 16 Jun 2002 20:01:20 -0400
"Faust Tanasescu" <faust_tanasescu@hotmail.com> wrote:
> I'm thinking of lots of glue, a perl script for client and https server on
> gentoo.org to allow SSL (secure socket layer) communication between
> client/server. It's a fresh approach to solve just this problem... Well
> fresh is relative here ;)
>
> Here's a link
> http://developer.netscape.com/docs/manuals/security/sslin/contents.htm
next prev parent reply other threads:[~2002-06-17 0:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-17 0:01 [gentoo-dev] RFP: System to account users configurations Faust Tanasescu
2002-06-17 0:12 ` Rufiao [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-16 21:12 Faust Tanasescu
2002-06-16 23:11 ` Rufiao
2002-06-18 10:37 ` George Shapovalov
2002-06-16 20:16 Rufiao
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=20020616211259.6d5f4544.rufiao@gmx.net \
--to=rufiao@gmx.net \
--cc=gentoo-dev@gentoo.org \
/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