hi
( 06.06.01 22:48 -0400 ) Chris Devers:
Plan for growth. You'll be glad you did, someday.
or, it will just go on that huge pile of great code that never got
deployed.
--
\js oblique strategy: make a sudden, destructive unpredictable action;
incorporate
On 1 Jun 2006, [EMAIL PROTECTED] wrote:
Let me clarify a bit more what I need to do. We want to use $USER
to verify a valid user before running the program, so this is very
unlikely go on the web or have a web interface.
You can tie web-based authentication to an external user database
From: Ted Zlatanov [EMAIL PROTECTED]
Date: Fri, 02 Jun 2006 10:22:25 -0400
On 1 Jun 2006, [EMAIL PROTECTED] wrote:
Let me clarify a bit more what I need to do. We want to use $USER
to verify a valid user before running the program, so this is very
unlikely go on the web or
On 2 Jun 2006, [EMAIL PROTECTED] wrote:
The key is to let somebody else do as much of the authentication
implementation as possible, as it's tricky and time-consuming to get
right.
The Unix login process can be subverted by sudo (not to mention that
$USER can be set to anything, as
From: Ted Zlatanov [EMAIL PROTECTED]
Date: Fri, 02 Jun 2006 14:41:48 -0400
On 2 Jun 2006, [EMAIL PROTECTED] wrote:
The Unix login process can be subverted by sudo (not to mention that
$USER can be set to anything, as others pointed out). You should
always request a
Thanks to those who have answered. Let me clarify a bit more what I
need to do. We want to use $USER to verify a valid user before running
the program, so this is very unlikely go on the web or have a web
interface. If a teaching assistant's personal account is compromised,
we're really in
Why not use a console-based spreadsheet?
It sounds like a lot of this could be done with shell scripts
(grep for users to show, etc.)
--
H4sICNoBwDoAA3NpZwA9jbsNwDAIRHumuC4NklvXTOD0KSJEnwU8fHz4Q8M9i3sGzkS7BBrm
OkCTwsycb4S3DloZuMIYeXpLFqw5LaMhXC2ymhreVXNWMw9YGuAYdfmAbwomoPSyFJuFn2x8
I am going to second the suggestion to write an upload feature from a
spreadsheet. You're not going to invent a better UI, and it is going
to take you a lot more work. Plus there is no security issue here -
anyone can do anything they want with the spreadsheet but they can
only enter it into
Date: Thu, 1 Jun 2006 20:22:27 -0400 (EDT)
From: Janet Marie Jackson
Subject: Re: [Boston.pm] Perl Curses clarification
Thanks to those who have answered. Let me clarify a bit more what I
need to do. We want to use $USER to verify a valid user before running
the program, so
From: Janet Marie Jackson [EMAIL PROTECTED]
Date: Thu, 1 Jun 2006 20:22:27 -0400 (EDT)
Thanks to those who have answered. Let me clarify a bit more what I
need to do. We want to use $USER to verify a valid user before running
the program, so this is very unlikely go on the
On Thu, 1 Jun 2006, Bob Rogers wrote:
Please note that this does not preclude using an SQL database. [...]
Of if you're hell-bent on CSV, at least use DBD::CSV and write your
application as if there's a real database engine on the other side.
That way, when you come around and realize that a
11 matches
Mail list logo
