Secure Portal Authentication
I am trying to create a portal using IIS/MSSQL/PERL... I can capture user input, query user names, and verify passwords. I need to know the best way to make sure the person has authenticated and is allowed to view the restricted content. When people authenticate is there a way pass a variable, and if the variable isn't set redirect them back to the authentication page? Also, need to make sure its secure, dont want to have something in a cookie or a hidden field that could be changed to grant themselves access. Thanks in advance for the responses! Chico -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/ http://learn.perl.org/first-response
Portal
I want to make a portal with password protected pages and directories using PERL (not IIS or Apache directory permissions). What is the best way to go about this? Keeping state and passing variables within the code? I have read tons of things on the net about making Forms and scripts with PERL, but nothing about actually creating a web application/portal... -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/ http://learn.perl.org/first-response
'medium' reg exp greediness?
hello folks, I'm trying to do a 'medium' greediness regular expression. Here's what I mean. I need to grab all of the DW_TAG_TI_reserved stuff and kill it (italics below) die id='0x157' tagDW_TAG_TI_assign_register/tag attribute typeDW_AT_location/type value blockDW_OP_reg0/block /value /attribute /die die id='0x8903' tagDW_TAG_TI_reserved_1/tag attribute typeDW_AT_name/type value stringC:\DOCUME~1\A0741153\LOCALS~1\Temp\TI1564:L2:2:1088629783/string /value /attribute die id='0x8951' tagDW_TAG_TI_reserved_2/tag attribute typeDW_AT_low_pc/type value addr0x1b84/addr /value /attribute /die /die die id='0x130' tagDW_TAG_variable/tag attribute typeDW_AT_name/type value stringTSK_thingyIneedToKeepThis/string /value /attribute /die I did the following for killing DW_TAG_TI_assign_register. $all_lines =~ s/die id\S*\s*tagDW_TAG_TI_assign_register.*?\/die//sg; That worked fine. But the DW_TAG_TI_reserved stuff is nested. I need medium greediness ie .* (where . also matches newline via /s) without a ? would go too far ie it would grab everything up until last /die which is too muchkills stuff I need to keep. But .*? is too lazy...it doesnt handle the nesting ie only kills up until the first /die. To further complicate life, I cant guarentee the level of nesting. Any ideas on how best to reg exp this? Or do I just need to improve/narrow my search string. Many thanks indeed. cheers, Alan - How low will we go? Check out Yahoo! Messengers low PC-to-Phone call rates.
Re: Replying to the perl list (was Re: problem with whitespace not splitting on split.)
Rance == Rance Hall [EMAIL PROTECTED] writes: Rance All of my other lists behave in the reverse, if you reply, it goes to Rance the list, if you reply all, a second copy goes to the individual. Oh geez. Here we go again. Please read http://www.unicom.com/pw/reply-to-harmful.html. And understand that *no* list managed at lists.perl.org will *ever* have reply-to set. Thank goodness. :) Your other lists coddle to the beginners who can't operate their mail client, at the expense of experts who *can*. Let's not hobble the experts, or the experts will go away. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 merlyn@stonehenge.com URL:http://www.stonehenge.com/merlyn/ Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training! -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/ http://learn.perl.org/first-response
RE: Replying to the perl list (was Re: problem with whitespace not splitting on split.)
Randal L. Schwartz wrote: : Oh geez. Here we go again. : : Please read http://www.unicom.com/pw/reply-to-harmful.html. : And understand that *no* list managed at lists.perl.org will : *ever* have reply-to set. Thank goodness. :) : : Your other lists coddle to the beginners who can't operate their : mail client, at the expense of experts who *can*. Let's not : hobble the experts, or the experts will go away. In practice, I use two types of replies. One to all the list recipients and one to only the author of this particular message. It's silly to send the message to the entire list and send a duplicate to the author. (He already has a copy because he is a member of the list.) PBML on Yahoo Groups uses munged Reply-To addresses. I have contributed to that list for about 6 years. I understand that it will never change this option. Thank goodness. I like not having to use reply to all and then delete addresses like I do on the list.perl.org lists. I am willing to give up my freedom in exchange for a sane reply choice. What we probably need is unmunged Reply-To addresses and mail clients which allow custom reply choices. Then the experts and we young whipper snappers can both be happy. :) HTH, Charles K. Clarkson -- Mobile Homes Specialist 254 968-8328 -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/ http://learn.perl.org/first-response
Re: Replying to the perl list (was Re: problem with whitespace not splitting on split.)
On Sat, 2006-29-04 at 07:47 -0700, Randal L. Schwartz wrote: Rance == Rance Hall [EMAIL PROTECTED] writes: Rance All of my other lists behave in the reverse, if you reply, it goes to Rance the list, if you reply all, a second copy goes to the individual. Oh geez. Here we go again. Please read http://www.unicom.com/pw/reply-to-harmful.html. And understand that *no* list managed at lists.perl.org will *ever* have reply-to set. Thank goodness. :) Your other lists coddle to the beginners who can't operate their mail client, at the expense of experts who *can*. Let's not hobble the experts, or the experts will go away. If you want us to use Reply to All then stop sending those iterating automatic replies that says you are too busy to answer your mail and will get to it later. In fact, stop sending all automatic replies. I don't care if you're on vacation and won't respond for three weeks; if it was important I would have phoned. If it's e-mail, it's not that important. Please, no more automatic replies. -- __END__ Just my 0.0002 million dollars worth, --- Shawn For the things we have to learn before we can do them, we learn by doing them. Aristotle * Perl tutorials at http://perlmonks.org/?node=Tutorials * A searchable perldoc is at http://perldoc.perl.org/ -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/ http://learn.perl.org/first-response
RE: Replying to the perl list (was Re: problem with whitespace notsplitting on split.)
-Original Message- From: Randal L. Schwartz [mailto:[EMAIL PROTECTED] Your other lists coddle to the beginners who can't operate their mail client, at the expense of experts who *can*. Let's not hobble the experts, or the experts will go away. I thought this was a beginners list? -r Russell J. Foster Systems Management Consultant [EMAIL PROTECTED] 630.885.0147 cell 815.550.1376 efax -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/ http://learn.perl.org/first-response
Re: Replying to the perl list (was Re: problem with whitespace not splitting on split.)
In practice, I use two types of replies. One to all the list recipients and one to only the author of this particular message. It's silly to send the message to the entire list and send a duplicate to the author. (He already has a copy because he is a member of the list.) I do agree that. But if you use gmail,you could avoid to receive multi-duplication messages since gmail use the threads for talking-session.It's really good for mailing list.:) -- 网易无线事业部邮件组 彭勇华 Jeff Peng Email: [EMAIL PROTECTED] Email: [EMAIL PROTECTED]
Re: Replying to the perl list
Charles K. Clarkson schreef: What we probably need is unmunged Reply-To addresses and mail clients which allow custom reply choices. At last. Please also set up your mail client to remove the / (was:.*)$/ out of the Subject, when replying. -- Affijn, Ruud Gewoon is een tijger. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/ http://learn.perl.org/first-response
'Tie::StdScalar' - perl tells me it can't find it
i'm try to use 'Tie::StdScalar' but perl tells me it can't find it. I've pushed '/usr/share/perl/5.8.7' onto @INC. the error is: Can't locate Tie/StdScalar.pm in @INC in '/usr/share/perl/5.8.7/Tie/Scalar.pm' there is 'package Tie::StdScalar' etc. thanks, tom arnall north spit, ca -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/ http://learn.perl.org/first-response
Re: 'Tie::StdScalar' - perl tells me it can't find it
On Sat, 2006-29-04 at 10:28 -0700, tom arnall wrote: i'm try to use 'Tie::StdScalar' but perl tells me it can't find it. I've pushed '/usr/share/perl/5.8.7' onto @INC. the error is: Can't locate Tie/StdScalar.pm in @INC in '/usr/share/perl/5.8.7/Tie/Scalar.pm' there is 'package Tie::StdScalar' etc. thanks, tom arnall north spit, ca Is the module Tie::Scalar? See `perldoc Tie::Scalar` for details. -- __END__ Just my 0.0002 million dollars worth, --- Shawn For the things we have to learn before we can do them, we learn by doing them. Aristotle * Perl tutorials at http://perlmonks.org/?node=Tutorials * A searchable perldoc is at http://perldoc.perl.org/ -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/ http://learn.perl.org/first-response
Re: Replying to the perl list (was Re: problem with whitespace notsplitting on split.)
On Sat, Apr 29, 2006 at 11:28:26AM -0500, Russ Foster wrote: -Original Message- From: Randal L. Schwartz [mailto:[EMAIL PROTECTED] Your other lists coddle to the beginners who can't operate their mail client, at the expense of experts who *can*. Let's not hobble the experts, or the experts will go away. I thought this was a beginners list? He has a point, in that the experts are here to answer questions for the beginners, and are an important contributing influence to the beginners' list. I'm in the abnormal position of being pretty darned good at some things and a rank neophyte at others, so I try to share a little of what I know and soak up knowledge offered by people like Randal, Tom, et alii: among other things, they tend to provide a check on the help the rest of us offer each other so that when we give advice that has some negative consequences of which we're not fully cognizant at the time they can set us straight. I'd rather not see them chased off. On the other hand, you too have a point: I rather suspect that there've probably been a handful of beginners chased off over time by the odd manner in which the list behaves (in comparison with many other lists). That's not really an optimal situation, either. There's gotta be a simple solution out there somewhere that allows a more-convenient (for those used to being able to simply reply to a list) means of interacting with the list without forcing them to A) change email clients and B) become expert operators of the new clients just to be able to get help while still keeping things tidy in the minds of those who prefer proper list handling. I'm not going to make the mistake of dividing those two groups directly between experts and beginners, though. I tend to think that, in the world of Perl, the experts are probably as likely to fall into either camp in terms of their list behavior expectations as they are to fall into the other, though it's true that beginners are far more likely to end up sympathizing more with the just reply, darnit preference, I'd guess. I entertain hopes of some day being an all-around expert in Perl myself, but while I sympathize with some of what I assume is the reasoning Mr. Schwartz uses to justify and inform his preference, I suspect it will be a very long time indeed before I actually prefer a situation that will at least occasionally produce errors in email targeting on my part, even if only because I'm moving my email operations from one system to another and thus have to reconfigure sending preferences. I also, of course, have some sympathy for those whose email clients aren't as configurable as, say, Mutt. I've rambled enough on that subject for the nonce. (Ironically, I almost sent that to only one person, rather than the list. Whoops. I still haven't gotten around to messing with my MUA's configuration to solve this little issue on my end.) -- Chad Perrin [ CCD CopyWrite | http://ccd.apotheon.org ] This sig for rent: a Signify v1.14 production from http://www.debian.org/ -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/ http://learn.perl.org/first-response
Re: Replying to the perl list
On Sat, 2006-29-04 at 11:52 -0600, Chad Perrin wrote: There's gotta be a simple solution out there somewhere that allows a more-convenient (for those used to being able to simply reply to a list) means of interacting with the list without forcing them to A) change email clients and B) become expert operators of the new clients just to be able to get help while still keeping things tidy in the minds of those who prefer proper list handling. The problem is that an email has up to four groups to reply to: From:, Reply-To:, To:, and Cc: That's 15 combinations. Two options, Reply and Reply to All, just ain't enough. It would be nice if my email application allowed me to set what combination a Reply was actually sent to. And while you're at it, make it depend on what folder I'm in. After all, we already have message filters to sort the mail into folders. Why can't I create rules for my replies? -- __END__ Just my 0.0002 million dollars worth, --- Shawn For the things we have to learn before we can do them, we learn by doing them. Aristotle * Perl tutorials at http://perlmonks.org/?node=Tutorials * A searchable perldoc is at http://perldoc.perl.org/ -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/ http://learn.perl.org/first-response
Re: Replying to the perl list
On Sat, Apr 29, 2006 at 02:36:09PM -0400, Mr. Shawn H. Corey wrote: On Sat, 2006-29-04 at 11:52 -0600, Chad Perrin wrote: There's gotta be a simple solution out there somewhere that allows a more-convenient (for those used to being able to simply reply to a list) means of interacting with the list without forcing them to A) change email clients and B) become expert operators of the new clients just to be able to get help while still keeping things tidy in the minds of those who prefer proper list handling. The problem is that an email has up to four groups to reply to: From:, Reply-To:, To:, and Cc: That's 15 combinations. Two options, Reply and Reply to All, just ain't enough. It would be nice if my email application allowed me to set what combination a Reply was actually sent to. And while you're at it, make it depend on what folder I'm in. After all, we already have message filters to sort the mail into folders. Why can't I create rules for my replies? You forgot about list-reply. There are probably others, too, but I didn't sleep much and am not willing to exercise my brain unnecessarily at the moment. -- Chad Perrin [ CCD CopyWrite | http://ccd.apotheon.org ] Ben Franklin: As we enjoy great Advantages from the Inventions of others we should be glad of an Opportunity to serve others by any Invention of ours, and this we should do freely and generously. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/ http://learn.perl.org/first-response
RE: Replying to the perl list
Russ Foster wrote: : I thought this was a beginners list? It's a Perl beginner's list not an email beginner's list. If I choose to find answers to my problem in an encyclopedia I would first learn the correct method to use the encyclopedia then I would be able to use that resource correctly. The same is true of a technical email list. If I choose to use a technical email list for answers I would first read up on the etiquette for using that list then I would be able to use that resource correctly. HTH, Charles K. Clarkson -- Mobile Homes Specialist 254 968-8328 -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/ http://learn.perl.org/first-response
Re: 'medium' reg exp greediness?
On 4/29/06, Alan Campbell [EMAIL PROTECTED] wrote:
hello folks,
I'm trying to do a 'medium' greediness regular expression. Here's what I
mean. I need to grab all of the DW_TAG_TI_reserved stuff and kill it (italics
below)
die id='0x157'
tagDW_TAG_TI_assign_register/tag
attribute
typeDW_AT_location/type
value
blockDW_OP_reg0/block
/value
/attribute
/die
[snip]
A couple of thoughts: If you read this list regularly, you already
know the advice you're going to get: there are hundreds of xml modules
on CPAN. Use them! Don't reinvent the wheel.
If you really insist on doing this by hand, we need to see more code.
How are you approaching this? On the surface, it looks pretty simple:
{
$lf = \n;
local $/ = /die . $lf;
whlie () {
print unless /DW_TAG_TI_reserved/;
}
}
Your question, though, leads me to think there's more going on.
So let me just reiterate my original advice again: use a mudule.
HTH,
-- jay
--
This email and attachment(s): [ ] blogable; [ x ] ask first; [ ]
private and confidential
daggerquill [at] gmail [dot] com
http://www.tuaw.com http://www.dpguru.com http://www.engatiki.org
values of β will give rise to dom!
