Re: Implementing security in CGI

2000-04-24 Thread dreamwvr
hi, actually in order for this flaw to work one must have both enabled on the browser.. was just giving people a heads up since the topic was cookies.. and no IMHO cookies are not required to obtain good info.. On Mon, 24 Apr 2000, Matt Sergeant wrote: > On Mon, 24 Apr 2000, Marc Slemko wrote:

Re: Implementing security in CGI

2000-04-24 Thread Matt Sergeant
On Mon, 24 Apr 2000, dreamwvr wrote: > usally nothing but now everything as per bugtraq advisory.. what this means is > javascript code is inserted into a cookie that is living on a client and > executed there.. they can therefore read your bookmarks and so on.. I shudder at the thought of all t

Re: Implementing security in CGI

2000-04-24 Thread Matt Sergeant
On Mon, 24 Apr 2000, Marc Slemko wrote: > Don't go holding slashdot up as a great example. They is a perfect > example of what not to do. Last I checked, and this is probably still > true, anyone could make a post that, when read, stole the password of the > user reading it if they were logged

Re: Implementing security in CGI

2000-04-24 Thread Marc Slemko
On Mon, 24 Apr 2000, Matt Sergeant wrote: > On Sat, 22 Apr 2000, dreamwvr wrote: > > > hi, > >most likely you will want to shut down cookies and use another method as per > > advisories that currently there is a problem with javascript and cookies when > > both enabled. b.t.w. exploder has

Re: Implementing security in CGI

2000-04-24 Thread dreamwvr
On Mon, 24 Apr 2000, Vivek Khera wrote: > > "d" == dreamwvr <[EMAIL PROTECTED]> writes: > > d> to have cookies are a problem these days. besides most clueful > d> users these days have cookies turned off.. > > According to what survey? I'd like to see some real numbers before > abandoning

Re: Implementing security in CGI

2000-04-24 Thread Matt Sergeant
On Sat, 22 Apr 2000, dreamwvr wrote: > hi, >most likely you will want to shut down cookies and use another method as per > advisories that currently there is a problem with javascript and cookies when > both enabled. b.t.w. exploder has simular problems so since javascript is nice > to have

Re: Implementing security in CGI

2000-04-24 Thread Vivek Khera
> "d" == dreamwvr <[EMAIL PROTECTED]> writes: d> to have cookies are a problem these days. besides most clueful d> users these days have cookies turned off.. According to what survey? I'd like to see some real numbers before abandoning a very useful technique. "I heard it on TV so it must

Re: Implementing security in CGI

2000-04-24 Thread Kee Hinckley
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At 2:28 PM -0600 4/22/00, dreamwvr wrote: >to have cookies are a problem these days. besides most clueful users >these days >have cookies turned off.. The percentage of "clueful" users is extremely small. Furthermore, since the vast majority of co

Re: Implementing security in CGI

2000-04-24 Thread Roger Espel Llima
On Sat, Apr 22, 2000 at 02:28:44PM -0600, dreamwvr wrote: > hi, most likely you will want to shut down cookies and use another > method as per advisories that currently there is a problem with > javascript and cookies when both enabled. b.t.w. exploder has simular > problems so since javascript is

Re: Implementing security in CGI

2000-04-22 Thread Gunther Birznieks
At 09:42 AM 4/22/00 -0500, Michael Schout wrote: >On Thu, Apr 20, 2000 at 12:15:16PM -0400, DeWitt Clinton wrote: > > The secure session has the following properties: > > > > *) The user is able to initiate a secure session by providing proper > > credentials (i.e., a username and password pair) v

Re: Implementing security in CGI

2000-04-22 Thread dreamwvr
hi, most likely you will want to shut down cookies and use another method as per advisories that currently there is a problem with javascript and cookies when both enabled. b.t.w. exploder has simular problems so since javascript is nice to have cookies are a problem these days. besides most

Re: Implementing security in CGI

2000-04-22 Thread Michael Schout
On Thu, Apr 20, 2000 at 12:15:16PM -0400, DeWitt Clinton wrote: > The secure session has the following properties: > > *) The user is able to initiate a secure session by providing proper > credentials (i.e., a username and password pair) via a login process. > > *) The user is able to terminate

Re: Implementing security in CGI

2000-04-22 Thread Matt Carothers
On Fri, 21 Apr 2000, Gunther Birznieks wrote: > At 01:44 PM 4/20/00 -0500, Matt Carothers wrote: > > >Another big win is that the secure token can persist across multiple > >servers. > > What would prevent the token from being across multiple servers otherwise? It's beneficial when compared

Re: Implementing security in CGI

2000-04-21 Thread Gunther Birznieks
At 01:44 PM 4/20/00 -0500, Matt Carothers wrote: >On Thu, 20 Apr 2000, DeWitt Clinton wrote: > > > 5) The secure token is associated on the server side (preferably on > > another tier, such as a database) with the user identification token. > > Additionally, to support secure session timeouts, t

Re: Implementing security in CGI

2000-04-20 Thread Matt Carothers
On Thu, 20 Apr 2000, DeWitt Clinton wrote: > 5) The secure token is associated on the server side (preferably on > another tier, such as a database) with the user identification token. > Additionally, to support secure session timeouts, the current time > must be recorded. An easy way to imple

Re: Implementing security in CGI

2000-04-20 Thread DeWitt Clinton
Hi, Interesting thread and interesting question. It makes sense to start with the requirements for what it means to implement those secure features. My requirements have an obvious e-commerce bias, and should probably be heavily reviewed by anyone thinking of using this design for onli

Re: Implementing security in CGI

2000-04-20 Thread Jeff Beard
At 05:36 PM 4/20/00, Differentiated Software Solutions Pvt. Ltd. wrote: >a) [...] then do we have a >security hole? Is not the user assuming that by killing the browser we are >exiting the system !! Yes there is a security risk. HTTP is an insecure protocol. You can use the ideas that have been

Re: Implementing security in CGI

2000-04-20 Thread Jeff Beard
At 04:27 PM 4/20/00, Gunther Birznieks wrote: >Yeah it works on all the clients, but it's a pain in the ass to do >relative URLs when manipulating PATH_INFO. So it's not necessarily >trivial to program and maintain unless you pass everything through a >monolithic CGI. > >Of course, on Apache i

Re: Implementing security in CGI

2000-04-20 Thread Differentiated Software Solutions Pvt. Ltd.
or any of these modules under plain vanilla CGI. Will this work ?? Thanks for the inputs. They have been invaluable. Murali -Original Message- From: Gunther Birznieks <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: 20 April 2000 18:19 Subject: Re: Implement

Re: Implementing security in CGI

2000-04-20 Thread Gunther Birznieks
OTECTED] <[EMAIL PROTECTED]> >Date: 20 April 2000 10:55 >Subject: Re: Implementing security in CGI > > > >This is a question for comp.infosystems.www.authoring.cgi. > > > >But since I'm here... > > > >I would check for the cookie every time a request is made

Re: Implementing security in CGI

2000-04-20 Thread Gunther Birznieks
Yeah it works on all the clients, but it's a pain in the ass to do relative URLs when manipulating PATH_INFO. So it's not necessarily trivial to program and maintain unless you pass everything through a monolithic CGI. Of course, on Apache it may be easier by using mod_rewrite to manipulate t

Re: Implementing security in CGI

2000-04-20 Thread Manfred Dehnkamp
Hy, why do you use cookie's ??? A lot of people hate them. I think a much better Idea is to put your sessionID in the PathInfo of every requested URI. So after the login your CGI generates a SessionID. Lets say your CGI has the URI http://domain/mycgi. After the login the cgi's output is just a re

Re: Implementing security in CGI

2000-04-19 Thread Differentiated Software Solutions Pvt. Ltd.
CTED]>; [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: 20 April 2000 10:55 Subject: Re: Implementing security in CGI >This is a question for comp.infosystems.www.authoring.cgi. > >But since I'm here... > >I would check for the cookie every time a request is made. If you us

Re: Implementing security in CGI

2000-04-19 Thread Adi
Murali, Yes I have a site that uses the exact mechanism that you state. As Jeff said though, you should have an "auto-logout" feature. I implemented this as a cron job that runs every 30 minutes and checks each session for the last time it has been accessed. I'm sure there are other ways to au

Re: Implementing security in CGI

2000-04-19 Thread Jeff Beard
? Please help. > >Thanks, > >Murali > >-Original Message----- >From: Gunther Birznieks <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> >Date: 19 April 2000 18:44 >Subject: Re: Implementing security in CGI > > > >Apache::Sessi

Re: Implementing security in CGI

2000-04-19 Thread Differentiated Software Solutions Pvt. Ltd.
ookie with the session-id does not exist. Am I right ??? Please help. Thanks, Murali -Original Message- From: Gunther Birznieks <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: 19 April 2000 18:44 Subject: Re: Implementing security in CGI >Apache::Sess

Re: Implementing security in CGI

2000-04-19 Thread Gunther Birznieks
Apache::Session could be useful. But the session key that is generated is arguable not necessarily the most secure that it could be. But it is pretty good. I'm probably opening up a can of worms by saying this. The MD5 hash itself is relatively secure as hashes go (although SHA hash space cou

Re: Implementing security in CGI

2000-04-19 Thread Francesc Guasch
"Differentiated Software Solutions Pvt. Ltd." wrote: > > > Would Apache::Session be useful for this ?? > Yes, it was very easy for me to use HTML::Mason and Apache::Session. -- - frankie -

Implementing security in CGI

2000-04-19 Thread Differentiated Software Solutions Pvt. Ltd.
Hi, We are having a site which is programmed with perl/CGI. To enter the site we have a login and password. After which some reports are displayed. I know that using cookies it is possible to secure the site. Can somebody guide me on how to design and implement a cookie based security. Sites and