Received: from icebox.venux.net (icebox.venux.net [216.120.166.10]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f49H8YA26026 for ; Wed, 9 May 2001 13:08:34 -0400 (EDT) (envelope-from mitch@venux.net) Received: from windows (net-216-93-124-123.hcv.com [216.93.124.123]) by icebox.venux.net (Postfix) with SMTP id EE4C826202; Wed, 9 May 2001 13:25:06 -0400 (EDT) Message-ID: <005e01c0d8aa$484d9da0$1251000a@windows> From: "Mitch Vincent" To: "Christian Marschalek" , "'Dan Wilson'" Cc: "[PHP] PostgreSQL" References: <000601c0d8a6$e42d03e0$0200a8c0@server> Subject: Re: RE: Sessions without cookies Date: Wed, 9 May 2001 13:05:43 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Archive-Number: 200105/41 X-Sequence-Number: 350 > > Why? If the user accepts the cookie, then they don't have a > > problem with it. If the user doesn't then it uses other > > functionality (URL re-writing). I don't see any problem with > > that. Leave it up to the user to decide how they want PHP to > > keep track of their session. > > Well because cookies are a security flaw, aren't day? Only if you make them one. :-) Cookies by in and of themselves are harmless. Just treat what ever you store in a cookie as if anyone could see it (because they probably can).. -Mitch