From MAILER-DAEMON Fri Aug 22 04:34:18 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19q6oh-00010k-Hc
	for mharc-unity-src@gnu.org; Fri, 22 Aug 2003 03:58:39 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19q57W-00021z-B3
	for unity-src@nongnu.org; Fri, 22 Aug 2003 02:09:58 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19q3Lj-0004uS-Ju
	for unity-src@nongnu.org; Fri, 22 Aug 2003 00:17:02 -0400
Received: from [134.130.3.131] (helo=ms-dienst.rz.rwth-aachen.de)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19q1Iz-0000cf-8F
	for unity-src@nongnu.org; Thu, 21 Aug 2003 22:05:33 -0400
Received: from r220-1 (r220-1.rz.RWTH-Aachen.DE [134.130.3.31])
	by ms-dienst.rz.rwth-aachen.de
	(iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003))
	with ESMTP id <0HJZ004HWR3WD3@ms-dienst.rz.rwth-aachen.de> for
	unity-src@nongnu.org; Fri, 22 Aug 2003 00:43:09 +0200 (MEST)
Received: from relay.RWTH-Aachen.DE ([134.130.3.1])
	by r220-1 (MailMonitor for SMTP v1.2.2 ) ; Fri,
	22 Aug 2003 00:43:08 +0200 (MEST)
Received: from neuron.gotdns.org
	(jast@p508D907C.dip.t-dialin.net [80.141.144.124])
	by relay.rwth-aachen.de (8.12.9/8.12.7-1) with SMTP id
	h7LMh6aW002105	for
	<unity-src@nongnu.org>; Fri, 22 Aug 2003 00:43:07 +0200 (MEST)
Date: Fri, 22 Aug 2003 00:43:22 +0200
From: Jan Krueger <jan.krueger@rwth-aachen.de>
To: unity-src@nongnu.org
Message-id: <200308212243.h7LMh6aW002105@relay.rwth-aachen.de>
MIME-version: 1.0
X-Mailer: Sylpheed version 0.9.0claws (GTK+ 1.2.10; i686-pc-linux-gnu)
Content-type: multipart/signed; boundary="=.S+hfl9g7mAhZDM"; micalg=pgp-sha1; 
	protocol="application/pgp-signature"
X-Entropy: provided by this line
Subject: [Unity-SRC] Server to server authentication
X-BeenThere: unity-src@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: "SRC \(Unity\) public discussion" <unity-src@nongnu.org>
List-Id: SRC (Unity) public discussion  <unity-src.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/unity-src>,
	<mailto:unity-src-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/unity-src>
List-Post: <mailto:unity-src@nongnu.org>
List-Help: <mailto:unity-src-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/unity-src>,
	<mailto:unity-src-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Aug 2003 07:58:30 -0000

--=.S+hfl9g7mAhZDM
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi everyone,
long time no see... since I'm currently stuck at this particular part of the
protocol specification, I want to know your opinion on it.

The more decentralised structure of the network brings us to the question of
the credibility of servers. IRC servers authenticate each other by predefin=
ed
linking passwords and IP addresses. However, we are not going to have a glo=
bal
database of all SRC servers along with their connection passwords (which wo=
uld
be stupid anyway since anyone could potentionally read out another server's
password and assume its identity).

So I came up with two solutions: host-based authentication and SSL
certification.

host-based:
  when a server connects to another, the reverse DNS entry is checked again=
st
  the A record for the reverse hostname and if they match, the server is
  authenticated by that name.
  Drawback: servers cannot use two different hostnames at the same time.

SSL:
  when a server connects to another, its SSL certificate is made sure to ha=
ve
  been signed by the "SRC Root CA". The certificate would contain a list of
  hostnames of the server.
  Drawback: either all certifications have to come from a central place(us,=
=20
  for example), or server admins have to maintain an up-to-date list of=20
  trusted CAs.

Basically we could allow both at the same time; host-based is cheap and easy
and no major thinking needs to be involved, SSL does need thinking, and is
much more work for either "the SRC group" or the server admins.

Do you have another suggestion or an addition? I'd love to hear it.

--=20
regards,                        |     http://arc.pasp.de
Jan Kr=FCger                      | ()  ascii ribbon campaign
Student, RWTH Aachen, Germany   | /\  - against html mail
http://www.jast.net.tc/         |     - against microsoft attachments

--=.S+hfl9g7mAhZDM
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/RUsOWfPf43hgPWgRArTuAJ9+WdFJ6revbT1mWT3ewRDlSh9vSACfbimr
ioDCIkJTkEkm3hgo/TYLk5A=
=FQQk
-----END PGP SIGNATURE-----

--=.S+hfl9g7mAhZDM--




From MAILER-DAEMON Fri Aug 22 12:11:04 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19qEJl-0002hS-Qo
	for mharc-unity-src@gnu.org; Fri, 22 Aug 2003 11:59:13 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19qDRZ-0000G6-D7
	for unity-src@nongnu.org; Fri, 22 Aug 2003 11:03:13 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19qBdm-0005uZ-83
	for unity-src@nongnu.org; Fri, 22 Aug 2003 09:08:14 -0400
Received: from [62.49.21.22] (helo=fragalot.com)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19qB3b-0003Zg-Jt
	for unity-src@nongnu.org; Fri, 22 Aug 2003 08:30:19 -0400
Received: from WorldClient ([10.0.0.5]) by fragalot.com ([10.0.0.5])
	with SMTP (MDaemon.PRO.v6.7.6.R)
	for <unity-src@nongnu.org>; Fri, 22 Aug 2003 13:29:44 +0100
Received: from [193.38.143.253] via WorldClient with HTTP;
	Fri, 22 Aug 2003 13:29:13 +0100
Date: Fri, 22 Aug 2003 13:29:13 +0100
From: "David Westley" <Dave@fragalot.com>
To: "SRC \(Unity\) public discussion" <unity-src@nongnu.org>
Subject: Re: [Unity-SRC] Server to server authentication
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Message-ID: <WorldClient-F200308221329.AA29131721@fragalot.com>
X-Mailer: WorldClient 6.7.6
In-Reply-To: <200308212243.h7LMh6aW002105@relay.rwth-aachen.de>
References: <200308212243.h7LMh6aW002105@relay.rwth-aachen.de>
X-Authenticated-Sender: Dave@fragalot.com
X-MDRemoteIP: 10.0.0.5
X-Return-Path: Dave@fragalot.com
X-MDaemon-Deliver-To: unity-src@nongnu.org
X-BeenThere: unity-src@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: "SRC \(Unity\) public discussion" <unity-src@nongnu.org>
List-Id: SRC (Unity) public discussion  <unity-src.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/unity-src>,
	<mailto:unity-src-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/unity-src>
List-Post: <mailto:unity-src@nongnu.org>
List-Help: <mailto:unity-src-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/unity-src>,
	<mailto:unity-src-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Aug 2003 15:59:12 -0000

What if we go with the SSL option but old style networks (can't remember what 
they are going to be called in SRC) could apply for a network Certificate from 
the SRC Root CA then they can generate Certificates for their servers, that way 
we would take the load off of us generating Certificates for everyone?

If this sounds really stupid to anyone then just slap me! :)

Dave

-----Original Message-----
From: Jan Krueger <jan.krueger@rwth-aachen.de>
To: unity-src@nongnu.org
Date: Fri, 22 Aug 2003 00:43:22 +0200
Subject: [Unity-SRC] Server to server authentication

> Hi everyone,
> long time no see... since I'm currently stuck at this particular part of the
> protocol specification, I want to know your opinion on it.
> 
> The more decentralised structure of the network brings us to the question of
> the credibility of servers. IRC servers authenticate each other by predefined
> linking passwords and IP addresses. However, we are not going to have a
> global
> database of all SRC servers along with their connection passwords (which
> would
> be stupid anyway since anyone could potentionally read out another server's
> password and assume its identity).
> 
> So I came up with two solutions: host-based authentication and SSL
> certification.
> 
> host-based:
>   when a server connects to another, the reverse DNS entry is checked against
>   the A record for the reverse hostname and if they match, the server is
>   authenticated by that name.
>   Drawback: servers cannot use two different hostnames at the same time.
> 
> SSL:
>   when a server connects to another, its SSL certificate is made sure to have
>   been signed by the "SRC Root CA". The certificate would contain a list of
>   hostnames of the server.
>   Drawback: either all certifications have to come from a central place(us, 
>   for example), or server admins have to maintain an up-to-date list of 
>   trusted CAs.
> 
> Basically we could allow both at the same time; host-based is cheap and easy
> and no major thinking needs to be involved, SSL does need thinking, and is
> much more work for either "the SRC group" or the server admins.
> 
> Do you have another suggestion or an addition? I'd love to hear it.
> 
> -- 
> regards,                        |     http://arc.pasp.de
> Jan Krüger                      | ()  ascii ribbon campaign
> Student, RWTH Aachen, Germany   | /\  - against html mail
> http://www.jast.net.tc/         |     - against microsoft attachments
> 




From MAILER-DAEMON Fri Aug 22 13:13:20 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19qEHW-0001qJ-EU
	for mharc-unity-src@gnu.org; Fri, 22 Aug 2003 11:56:54 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19qDEZ-0004E4-FF
	for unity-src@nongnu.org; Fri, 22 Aug 2003 10:49:47 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19qCxB-0006Kw-9O
	for unity-src@nongnu.org; Fri, 22 Aug 2003 10:32:21 -0400
Received: from [62.49.21.22] (helo=fragalot.com)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19qB6q-0004iN-2K
	for unity-src@nongnu.org; Fri, 22 Aug 2003 08:33:40 -0400
Received: from WorldClient ([10.0.0.5]) by fragalot.com ([10.0.0.5])
	with SMTP (MDaemon.PRO.v6.7.6.R)
	for <unity-src@nongnu.org>; Fri, 22 Aug 2003 13:33:35 +0100
Received: from [193.38.143.253] via WorldClient with HTTP;
	Fri, 22 Aug 2003 13:33:05 +0100
Date: Fri, 22 Aug 2003 13:33:05 +0100
From: "David Westley" <Dave@fragalot.com>
To: "SRC \(Unity\) public discussion" <unity-src@nongnu.org>
Subject: Re: [Unity-SRC] Server to server authentication
Message-ID: <WorldClient-F200308221333.AA33051722@fragalot.com>
X-Mailer: WorldClient 6.7.6
In-Reply-To: <200308212243.h7LMh6aW002105@relay.rwth-aachen.de>
References: <200308212243.h7LMh6aW002105@relay.rwth-aachen.de>
X-Authenticated-Sender: Dave@fragalot.com
X-MDRemoteIP: 10.0.0.5
X-Return-Path: Dave@fragalot.com
X-MDaemon-Deliver-To: unity-src@nongnu.org
X-BeenThere: unity-src@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: "SRC \(Unity\) public discussion" <unity-src@nongnu.org>
List-Id: SRC (Unity) public discussion  <unity-src.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/unity-src>,
	<mailto:unity-src-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/unity-src>
List-Post: <mailto:unity-src@nongnu.org>
List-Help: <mailto:unity-src-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/unity-src>,
	<mailto:unity-src-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Aug 2003 15:56:52 -0000

As a side note...

The software could generate self-signed certificates for testing purposes, 
small networks or personal servers but if they want their server/network to be 
able to share users/channels/groups/etc... with other networks then they'll 
need server certificates signed by a network certificate which would have to 
have been signed by us.

Nutty idea? maybe!


Dave




From MAILER-DAEMON Sat Aug 23 13:48:30 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19qcUW-0005iy-IP
	for mharc-unity-src@gnu.org; Sat, 23 Aug 2003 13:47:56 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19WzFP-0002cJ-2K
	for unity-src@nongnu.org; Mon, 30 Jun 2003 10:03:11 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19Wz9x-0006lX-U5
	for unity-src@nongnu.org; Mon, 30 Jun 2003 09:57:39 -0400
Received: from fly.symlynx.com ([213.73.91.20])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19Wz5r-0004wS-5K
	for unity-src@nongnu.org; Mon, 30 Jun 2003 09:53:19 -0400
Received: (from lynx@localhost)
	by fly.symlynX.com (8.11.6/8.11.6) id h5UDq6306415;
	Mon, 30 Jun 2003 15:52:06 +0200
Message-Id: <200306301352.h5UDq6306415@fly.symlynX.com>
To: jan.krueger@rwth-aachen.de
From: lynx@muve.to.psyc.pages.de
X-Image-URL: http://mp3.pages.de/lynX.jpg
X-Mailer: ELM [version 2.4ME+ PL60 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by fly.symlynX.com id
	h5UDq6306415
X-Mailman-Approved-At: Sat, 23 Aug 2003 13:47:54 -0400
Cc: psyc-devel@symlynx.com, unity-src@nongnu.org, you@awbsworld.de
Subject: [Unity-SRC] muve to psyc! :)
X-BeenThere: unity-src@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: "SRC \(Unity\) public discussion" <unity-src@nongnu.org>
List-Id: SRC (Unity) public discussion  <unity-src.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/unity-src>,
	<mailto:unity-src-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/unity-src>
List-Post: <mailto:unity-src@nongnu.org>
List-Help: <mailto:unity-src-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/unity-src>,
	<mailto:unity-src-request@nongnu.org?subject=subscribe>
Date: Mon, 30 Jun 2003 14:03:18 -0000
X-Original-Date: Mon, 30 Jun 2003 15:52:06 +0200 (CEST)
X-List-Received-Date: Mon, 30 Jun 2003 14:03:18 -0000

hey young hackers.. habe gerade euer src/unity projekt gesehen..

[hello mr. dutchman, i assume your knowledge of german is sufficient
for me to write in german.. ok? consider it a compliment ;)]

tja aachen aachen.. hatte schon einmal eine wichtige rolle. im
jahre 1990 setzten BuGless und ich uns im rahmen der relay party
zusammen und kauten die probleme von IRC und die l=F6sungsans=E4tze
von PSYC durch (auch wenn ich damals es noch nicht so nannte..)

es ist sicherlich sch=E4ndlich dass 13 jahre vergangen sind und jetzt
erst PSYC 1.0 kurz vor der release steht, aber es ist wirklich wahr -
PSYC ist *nicht* eingeschlafen wie jast auf seiner page vermutet.

auch sch=F6n dass viele konzepte aus PSYC sich auch in jasts summary
wiederfinden - nun w=FCrde ich vorschlagen bevor ich ebenfalls soviel
zeit verbringt eure pl=E4ne zu perfektionieren oder halbgare pl=E4ne
realisiert, macht doch bei PSYC mit!

wechselt einfach mit nem handels=FCblichen irc-client auf
/server ve.symlynx.com und kommt in den #PSYC raum. oder
benutzt telnet/webchat/psyc-client/java/flash was euch beliebt.
dann k=F6nnt ihr euch dort mit den psyc-entwicklern unterhalten -
f=FCr die unhackbare r=E4ume, nachrichten in abwesenheit und mail
notification im chat schon normalit=E4t sind. PSYC ist backward
compatible zu IRC clients, f=FChlt sich aber sehr anders an.

http://psyc.pages.de/		<-- the technology
http://muve.pages.de/muve	<-- the implementation
http://brain.symlynx.com/	<-- the demo access point
http://help.pages.de/		<-- user manual

--=20
	<psyc://lynX@symlynX.com>	    "auf worte folgen daten"
	<http://symlynX.com>     network chat technology since 1988

fippo m=FCmmelt: Man sollte die Telekom mit Drogen handeln lassen. Die w=FC=
rden auch diesen Markt innerhalb von 5 Jahren ruinieren und wir h=E4tten =
nirgends mehr Drogenprobleme...



From MAILER-DAEMON Sat Aug 23 13:48:56 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19qcV0-0006wS-Ug
	for mharc-unity-src@gnu.org; Sat, 23 Aug 2003 13:48:26 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19qanz-0008CG-J1
	for unity-src@nongnu.org; Sat, 23 Aug 2003 11:59:55 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19qamU-0005RM-2M
	for unity-src@nongnu.org; Sat, 23 Aug 2003 11:58:53 -0400
Received: from [213.133.99.5] (helo=teh.mooo.com)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19qaln-0003T4-5L
	for unity-src@nongnu.org; Sat, 23 Aug 2003 11:57:39 -0400
Received: from localhost (localhost [127.0.0.1]) (uid 33)
	by teh.mooo.com with local; Sat, 23 Aug 2003 16:07:22 +0200
Received: from 213.116.148.176 (SquirrelMail authenticated user raz)
	by teh.mooo.com with HTTP; Sat, 23 Aug 2003 16:07:22 +0200 (CEST)
Message-ID: <1293.213.116.148.176.1061647642.squirrel@teh.mooo.com>
Date: Sat, 23 Aug 2003 16:07:22 +0200 (CEST)
Subject: Re: [Unity-SRC] Server to server authentication
From: raz@teh.mooo.com
To: unity-src@nongnu.org
In-Reply-To: <200308212243.h7LMh6aW002105@relay.rwth-aachen.de>
References: <200308212243.h7LMh6aW002105@relay.rwth-aachen.de>
X-Priority: 3
Importance: Normal
X-MSMail-Priority: Normal
X-Mailer: SquirrelMail (version 1.2.6)
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mime-Autoconverted: from 8bit to quoted-printable by courier 0.37.3
X-Mailman-Approved-At: Sat, 23 Aug 2003 13:47:46 -0400
X-BeenThere: unity-src@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: "SRC \(Unity\) public discussion" <unity-src@nongnu.org>
List-Id: SRC (Unity) public discussion  <unity-src.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/unity-src>,
	<mailto:unity-src-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/unity-src>
List-Post: <mailto:unity-src@nongnu.org>
List-Help: <mailto:unity-src-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/unity-src>,
	<mailto:unity-src-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Aug 2003 16:00:01 -0000

I'd say host-based. Point is that a server -has- to have a PTR record, n=
ot
everyone's got the ability to get one. This'll probably filter out some
noobs, too.
I've got quite a bit of 'real life issues' and stuff, chances are I leav=
e
Rotterdam and get back to my parents so I'll be without internet access
for a while, although that'll probably be alright.
Chris

> Hi everyone,
> long time no see... since I'm currently stuck at this particular part
> of the protocol specification, I want to know your opinion on it.
>
> The more decentralised structure of the network brings us to the
> question of the credibility of servers. IRC servers authenticate each
> other by predefined linking passwords and IP addresses. However, we ar=
e
> not going to have a global database of all SRC servers along with thei=
r
> connection passwords (which would be stupid anyway since anyone could
> potentionally read out another server's password and assume its
> identity).
>
> So I came up with two solutions: host-based authentication and SSL
> certification.
>
> host-based:
>  when a server connects to another, the reverse DNS entry is checked
>  against the A record for the reverse hostname and if they match, the
>  server is authenticated by that name.
>  Drawback: servers cannot use two different hostnames at the same time=
.
>
> SSL:
>  when a server connects to another, its SSL certificate is made sure t=
o
>  have been signed by the "SRC Root CA". The certificate would contain =
a
>  list of hostnames of the server.
>  Drawback: either all certifications have to come from a central
>  place(us,  for example), or server admins have to maintain an
>  up-to-date list of  trusted CAs.
>
> Basically we could allow both at the same time; host-based is cheap an=
d
> easy and no major thinking needs to be involved, SSL does need
> thinking, and is much more work for either "the SRC group" or the
> server admins.
>
> Do you have another suggestion or an addition? I'd love to hear it.
>
> --
> regards,                        |     http://arc.pasp.de
> Jan Kr=FCger                      | ()  ascii ribbon campaign
> Student, RWTH Aachen, Germany   | /\  - against html mail
> http://www.jast.net.tc/         |     - against microsoft attachments






From MAILER-DAEMON Sat Aug 23 18:28:13 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19qgrY-0006fu-4U
	for mharc-unity-src@gnu.org; Sat, 23 Aug 2003 18:28:00 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19qgns-0004CP-QH
	for unity-src@nongnu.org; Sat, 23 Aug 2003 18:24:12 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19qgmr-00023h-Ms
	for unity-src@nongnu.org; Sat, 23 Aug 2003 18:23:41 -0400
Received: from [213.133.99.5] (helo=teh.mooo.com)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19qgmb-0001LU-QV
	for unity-src@nongnu.org; Sat, 23 Aug 2003 18:22:53 -0400
Received: from neuron.gotdns.org (p508DABFB.dip.t-dialin.net
	[::ffff:80.141.171.251])
	(IDENT: jast, AUTH: LOGIN jast, TLS: TLSv1/SSLv3, 168bits, DES-CBC3-SHA)
	by teh.mooo.com with esmtp; Sun, 24 Aug 2003 00:22:50 +0200
Date: Sun, 24 Aug 2003 00:23:05 +0200
From: Jan Krueger <jast@srcd.de>
To: "SRC (Unity) public discussion" <unity-src@nongnu.org>
Subject: Re: [Unity-SRC] Server to server authentication
In-Reply-To: <WorldClient-F200308221329.AA29131721@fragalot.com>
References: <200308212243.h7LMh6aW002105@relay.rwth-aachen.de>
	<WorldClient-F200308221329.AA29131721@fragalot.com>
Organization: Shared Server Project
X-Mailer: Sylpheed version 0.9.0claws (GTK+ 1.2.10; i686-pc-linux-gnu)
X-Entropy: =?ISO-8859-1?Q?XWJJ"D$)(XJ")=A7/(ts4j978xq2?=
Mime-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature";
	micalg=pgp-sha1; boundary="=_teh.mooo.com-2820-1061677371-0001-2"
Message-ID: <courier.3F47E93A.00000B04@teh.mooo.com>
X-BeenThere: unity-src@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: "SRC \(Unity\) public discussion" <unity-src@nongnu.org>
List-Id: SRC (Unity) public discussion  <unity-src.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/unity-src>,
	<mailto:unity-src-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/unity-src>
List-Post: <mailto:unity-src@nongnu.org>
List-Help: <mailto:unity-src-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/unity-src>,
	<mailto:unity-src-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Aug 2003 22:27:55 -0000

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_teh.mooo.com-2820-1061677371-0001-2
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi,

> What if we go with the SSL option but old style networks (can't remember
> what they are going to be called in SRC) could apply for a network
> Certificate from the SRC Root CA then they can generate Certificates for
> their servers, that way we would take the load off of us generating
> Certificates for everyone?
That would really eliminate the huge advantage SRC has over IRC--the
possibility of global communication.

Supposedly, this would lead again to small networks with some servers each,
but since all of those only have a certificate of their "network",
communication with other servers becomes impossible because their certificate
isn't trusted.

Anyway, to stay with the SSL idea, we could appoint several certificate
authorities and include all of their certificates in software releases, but
that's still not too good. We'd need some major infrastructure in the
background to provide access to all trusted certificates to server
administrators. Additionally, this would make it really easy to construct
proprietary SRC networks for commercial purposes (which can't really be
avoided anyway, but do we want to make it that easy for those people?).

As you can see, many things need to be considered. Perhaps if we do not use
SSL but rather something similar like OpenPGP signatures, we could abuse their
facilities for the distribution of keys and even the "web of trust" mechanism
(servers completely trust our certification key and less complete trust is
automatically applied to all keys directly signed by ours, or something like
that).
If we decided to use a web of trust like mechanism, more theoretical efforts
would have to go into this at some point. Also, should we agree to use PGP
over SSL, we could stop thinking about supporting SSL at all.

There's still the alternative: don't bother about certificates or signatures
and just go by reverse DNS hostnames (which should provide a mildly secure
authentication too), or support both so getting a server into the network
isn't too hard.

> If this sounds really stupid to anyone then just slap me! :)
If you don't stop apologising for suggesting things, I will. :P

Jan

PS. Hope this message isn't going to turn up twice, I had to re-send it using
another mail server.

--=_teh.mooo.com-2820-1061677371-0001-2
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/R+lNWfPf43hgPWgRAva8AJ9H06+rA2ZpdPm7BAAtGv0KYpK2aACfYjA5
VscGAseDGlG1F/EcHHo/pJA=
=lY36
-----END PGP SIGNATURE-----

--=_teh.mooo.com-2820-1061677371-0001-2--



From MAILER-DAEMON Sat Aug 23 19:58:25 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19qiGc-0005us-UH
	for mharc-unity-src@gnu.org; Sat, 23 Aug 2003 19:57:58 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19qiFp-0004qA-Cm
	for unity-src@nongnu.org; Sat, 23 Aug 2003 19:57:09 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19qiBe-0002P3-VV
	for unity-src@nongnu.org; Sat, 23 Aug 2003 19:53:23 -0400
Received: from [213.133.99.5] (helo=teh.mooo.com)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19qiA5-0001tE-Df
	for unity-src@nongnu.org; Sat, 23 Aug 2003 19:51:13 -0400
Received: from neuron.gotdns.org (p508DABFB.dip.t-dialin.net
	[::ffff:80.141.171.251])
	(IDENT: jast, AUTH: LOGIN jast, TLS: TLSv1/SSLv3, 168bits, DES-CBC3-SHA)
	by teh.mooo.com with esmtp; Sun, 24 Aug 2003 01:11:09 +0200
Date: Sun, 24 Aug 2003 01:11:25 +0200
From: Jan Krueger <jast@srcd.de>
To: "SRC (Unity) public discussion" <unity-src@nongnu.org>
Subject: Re: [Unity-SRC] Server to server authentication
In-Reply-To: <1293.213.116.148.176.1061647642.squirrel@teh.mooo.com>
References: <200308212243.h7LMh6aW002105@relay.rwth-aachen.de>
	<1293.213.116.148.176.1061647642.squirrel@teh.mooo.com>
Organization: Shared Server Project
X-Mailer: Sylpheed version 0.9.0claws (GTK+ 1.2.10; i686-pc-linux-gnu)
X-Entropy: =?ISO-8859-1?Q?XWJJ"D$)(XJ")=A7/(ts4j978xq2?=
Mime-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature";
	micalg=pgp-sha1; boundary="=_teh.mooo.com-3475-1061680271-0001-2"
Message-ID: <courier.3F47F48D.00000D93@teh.mooo.com>
X-BeenThere: unity-src@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: "SRC \(Unity\) public discussion" <unity-src@nongnu.org>
List-Id: SRC (Unity) public discussion  <unity-src.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/unity-src>,
	<mailto:unity-src-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/unity-src>
List-Post: <mailto:unity-src@nongnu.org>
List-Help: <mailto:unity-src-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/unity-src>,
	<mailto:unity-src-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Aug 2003 23:57:56 -0000

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_teh.mooo.com-3475-1061680271-0001-2
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

> I'd say host-based. Point is that a server -has- to have a PTR record, not
> everyone's got the ability to get one. This'll probably filter out some
> noobs, too.
Generally I'm all for it, but it would make creating virtual SRC servers
impossible. This might cut down on DNS spam like we know it from IRC but...
ah, hell. Do we want signatures for something else anyway? ;)

Jan

--=_teh.mooo.com-3475-1061680271-0001-2
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/R/SgWfPf43hgPWgRAtkVAJ9XiJ4lMMfjkdInuo+fXuFQ/enCygCfW92v
DTJYfeefMQA/Sf+jKxTyEVA=
=bHp8
-----END PGP SIGNATURE-----

--=_teh.mooo.com-3475-1061680271-0001-2--



From MAILER-DAEMON Sun Aug 24 07:11:15 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19qsdN-0006LE-Ah
	for mharc-unity-src@gnu.org; Sun, 24 Aug 2003 07:02:09 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19qnad-0001sh-D8
	for unity-src@nongnu.org; Sun, 24 Aug 2003 01:38:59 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19qna0-0001QJ-Af
	for unity-src@nongnu.org; Sun, 24 Aug 2003 01:38:52 -0400
Received: from [134.130.3.130] (helo=ms-dienst.rz.rwth-aachen.de)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19qnZz-0001NI-UL
	for unity-src@nongnu.org; Sun, 24 Aug 2003 01:38:20 -0400
Received: from r220-1 (r220-1.rz.RWTH-Aachen.DE [134.130.3.31])
	by ms-dienst.rz.rwth-aachen.de
	(iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003))
	with ESMTP id <0HK200DR3KKKUU@ms-dienst.rz.rwth-aachen.de> for
	unity-src@nongnu.org; Sat, 23 Aug 2003 13:14:44 +0200 (MEST)
Received: from relay.RWTH-Aachen.DE ([134.130.3.1])
	by r220-1 (MailMonitor for SMTP v1.2.2 ) ; Sat,
	23 Aug 2003 13:14:43 +0200 (MEST)
Received: from neuron.gotdns.org
	(jast@p508DABFB.dip.t-dialin.net [80.141.171.251])
	by relay.rwth-aachen.de (8.12.9/8.12.7-1) with SMTP id
	h7NBEgaW014858	for
	<unity-src@nongnu.org>; Sat, 23 Aug 2003 13:14:43 +0200 (MEST)
Date: Sat, 23 Aug 2003 13:14:58 +0200
From: Jan Krueger <jan.krueger@rwth-aachen.de>
Subject: Re: [Unity-SRC] Server to server authentication
In-reply-to: <WorldClient-F200308221329.AA29131721@fragalot.com>
To: "SRC (Unity) public discussion" <unity-src@nongnu.org>
Message-id: <200308231114.h7NBEgaW014858@relay.rwth-aachen.de>
MIME-version: 1.0
X-Mailer: Sylpheed version 0.9.0claws (GTK+ 1.2.10; i686-pc-linux-gnu)
Content-type: multipart/signed; boundary="=.UHBUAj9r?nIRm6"; micalg=pgp-sha1; 
	protocol="application/pgp-signature"
X-Entropy: provided by this line
References: <200308212243.h7LMh6aW002105@relay.rwth-aachen.de>
	<WorldClient-F200308221329.AA29131721@fragalot.com>
X-Mailman-Approved-At: Sun, 24 Aug 2003 07:01:47 -0400
X-BeenThere: unity-src@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: "SRC \(Unity\) public discussion" <unity-src@nongnu.org>
List-Id: SRC (Unity) public discussion  <unity-src.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/unity-src>,
	<mailto:unity-src-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/unity-src>
List-Post: <mailto:unity-src@nongnu.org>
List-Help: <mailto:unity-src-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/unity-src>,
	<mailto:unity-src-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Aug 2003 05:39:00 -0000

--=.UHBUAj9r?nIRm6
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi,

> What if we go with the SSL option but old style networks (can't remember
> what they are going to be called in SRC) could apply for a network
> Certificate from the SRC Root CA then they can generate Certificates for
> their servers, that way we would take the load off of us generating
> Certificates for everyone?
That would really eliminate the huge advantage SRC has over IRC--the
possibility of global communication.

Supposedly, this would lead again to small networks with some servers each,
but since all of those only have a certificate of their "network",
communication with other servers becomes impossible because their certificate
isn't trusted.

Anyway, to stay with the SSL idea, we could appoint several certificate
authorities and include all of their certificates in software releases, but
that's still not too good. We'd need some major infrastructure in the
background to provide access to all trusted certificates to server
administrators. Additionally, this would make it really easy to construct
proprietary SRC networks for commercial purposes (which can't really be
avoided anyway, but do we want to make it that easy for those people?).

As you can see, many things need to be considered. Perhaps if we do not use
SSL but rather something similar like OpenPGP signatures, we could abuse their
facilities for the distribution of keys and even the "web of trust" mechanism
(servers completely trust our certification key and less complete trust is
automatically applied to all keys directly signed by ours, or something like
that).
If we decided to use a web of trust like mechanism, more theoretical efforts
would have to go into this at some point. Also, should we agree to use PGP
over SSL, we could stop thinking about supporting SSL at all.

There's still the alternative: don't bother about certificates or signatures
and just go by reverse DNS hostnames (which should provide a mildly secure
authentication too), or support both so getting a server into the network
isn't too hard.

> If this sounds really stupid to anyone then just slap me! :)
If you don't stop apologising for suggesting things, I will. :P

Jan

--=.UHBUAj9r?nIRm6
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/R0y3WfPf43hgPWgRApq3AJsFBSSFaacQqvW1ygM6ayjlLs/ujACfRC2X
ckTa7MumSUZmM2EPvzSrM0g=
=upL0
-----END PGP SIGNATURE-----

--=.UHBUAj9r?nIRm6--




