apache localhost cookies
In short, I'm using a perl script to set a cookie, and Netscape Navigator isn't seeing it. It sets cookies o.k. on a '.com' webserver, but not on my localhost. I'm running RedHat 7.2 with apache installed. Viewing http://localhost in Netscape works, as does running scripts at http://localhost/cgi-bin/script.cgi I'm using a perl script (use CGI) to send a cookie. Netscape Navigator is set to accept all cookies, but after viewing the script that sets the cookie, testing for cookies is negative. In the script, the cookie domain is set to .localhost the cookie path is set to /cgi-bin the cookie expires is set to +15m name and value are set. When I run the perl script from the command line, the header that's printed appears o.k. I can't find any applicable info in the apache FAQ, so any pointers would be much appreciated. Thank-you, Carl Franks -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Unfriendly messages from people who should know better
The reason I was first attracted to this list was because of an article, announcing its launch (and that of the perl beginners list), in which the general theme was that for too long, newcomers to Perl had been subjected to RTFM in response to pleas for help. The lists were being set up to provide a friendly and inviting atmosphere in which to get and give help. In fact, in the FAQ for this list we have: 2.1 - What is the list for? A list for beginning Perl programmers to ask questions in a friendly atmosphere. 2.3 - Are there any rules? Yes. As with most communities, there are rules. Not many, and ones that shouldn't need to be mentioned, but they are. * Be nice * No flaming * Have fun and 2.6 - Is there anything I should keep in mind while answering? We don't want to see 'RTFM'. That isn't very helpful. Instead, guide the beginner to the place in the FM they should R :) I find it disturbing to see these guidelines being ignored by people who should know better - people who have a lot of respect within the Perl community. Such messages as (excerpted): Bleh! why does this program keep getting brought up? PLEASE STOP RECOMMENDING THIS PROGRAM. PLEASE POINT PEOPLE TO THE FAQ WHICH DETAILS THIS. and So, you're making money using a product that thousands have contributed to, providing the source code so that hundreds of others can adapt it and fix it as they see fit, and yet you want to squander that by locking up *your* application? require 'standard/open_source_is_good-speech.pl'; Don't expect much help *here*. This kind of ill-tempered response does this list (nor the respondent) no favors at all. Regards, Graham Gudgin -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unfriendly messages from people who should know better
Graham == Graham Gudgin [EMAIL PROTECTED] writes: Graham I find it disturbing to see these guidelines being ignored by people Graham who should know better - people who have a lot of respect within the Graham Perl community. Such messages as (excerpted): If you had something to say to me, say it to me. And for the record, none of the list monitors thwapped my wrists on either of these, although they have done so in the past with other messages. Which suggests that you do not have the support of the list monitors on these two particular messages. Just thought you'd like to know. I have three hot buttons on this list (and any public forum): ripping people off with scams (like perl2exe), commercializing and hoarding products derived from open software (like what the poster was doing), and introducing security errors. I will raise *all* the flags I can when anything like that happens. I will not be nice. Being nice lets some people off the hook for these things that I hold sacred. If you don't want to see messages from me about those issues, better filter me now. Of course, you'll lose the 98 messages you want to see, because of the two messages you don't want to see because they aren't nicey nice. Sorry about that, but that'd be your choice. Maybe I'm just in my grumbly mood this week. It's very likely... I've just wasted two days trying to figure out why my main laptop is randomly losing data under stress, and trying to get the backup laptop reconfigured to accept my backups, and it's giving me huge grief. Not to mention the recent court decision (http://groups.yahoo.com/group/fors-announce/message/20) which makes me a felon for life. Yeah, I suppose getting that during the holidays might make one a bit grouchy. But I stand by what I said, especially on these issues. perl2exe sucks. Trying to hide software written in Perl from your customers sucks. And having that message out there is important to me. Some people here will cheer me on for holding the banner so high on those, no matter what the method. Others will find my manner offensive about it, and still others will even disagree with both the manner and the goal. Oh well, this is life. Just another Perl hacker, -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 [EMAIL PROTECTED] 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]
Weekly list FAQ posting
NAME beginners-faq - FAQ for the beginners-cgi mailing list 1 - Administriva 1.1 - I'm not subscribed - how do I subscribe? Send mail to [EMAIL PROTECTED] You can also specify your subscription email address by sending email to (assuming [EMAIL PROTECTED] is your email address): [EMAIL PROTECTED]. 1.2 - How do I unsubscribe? Now, why would you want to do that? Send mail to [EMAIL PROTECTED], and wait for a response. Once you reply to the response, you'll be unsubscribed. If that doesn't work, find the email address which you are subscribed from and send an email like the following (let's assume your email is [EMAIL PROTECTED]): [EMAIL PROTECTED] 1.3 - There is too much traffic on this list. Is there a digest? Yes. To subscribe to the digest version of this list send an email to: [EMAIL PROTECTED] To unsubscribe from the digest, send an email to: [EMAIL PROTECTED] 1.4 - Is there an archive on the web? Yes, there is. It is located at: http://archive.develooper.com/beginners-cgi%40perl.org/ 1.5 - How can I get this FAQ? This document will be emailed to the list once a month, and will be available online in the archives, and at http://beginners.perl.org/ 1.6 - I don't see something in the FAQ, how can I make a suggestion? Send an email to [EMAIL PROTECTED] with your suggestion. 1.7 - Is there a supporting website for this list? Yes, there is. It is located at: http://beginners.perl.org/ 1.8 - Who owns this list? Who do I complain to? Casey West owns the beginners-cgi list. You can contact him at [EMAIL PROTECTED] 1.9 - Who currently maintains the FAQ? Kevin Meltzer, who can be reached at the email address (for FAQ suggestions only) in question 1.6 1.10 - Who will maintain peace and flow on the list? Casey West, Kevin Meltzer and Ask Bjoern Hansen currently carry large, yet padded, clue-sticks to maintain peace and order on the list. If you are privately emailed by one of these folks for flaming, being off-topic, etc... please listen to what they say. If you see a message sent to the list by one of these people saying that a thread is closed, do not continue to post to the list on that thread! If you do, you will not only meet face to face with a XQJ-37 nuclear powered pansexual roto-plooker, but you may also be taken off of the list. These people simply want to make sure the list stays topical, and above-all, useful to Perl/CGI beginners. 1.11 - When was this FAQ last updated? Sept 07, 2001 2 - Questions about the 'beginners-cgi' list. 2.1 - What is the list for? A list for beginning Perl programmers to ask questions in a friendly atmosphere. The topic of the list is, of course, CGI with Perl. 2.2 - What is this list _not_ for? * SPAM * Homework * Solicitation * Things that aren't Perl related * Non Perl/CGI questions or issues * Lemurs 2.3 - Are there any rules? Yes. As with most communities, there are rules. Not many, and ones that shouldn't need to be mentioned, but they are. * Be nice * No flaming * Have fun 2.4 - What topics are allowed on this list? Basically, if it has to do with Perl/CGI , then it is allowed. If your question has nothing at all to do with Perl/CGI, it will likely be ignored. 2.5 - I want to help, what should I do? Subscribe to the list! If you see a question which you can give an idiomatic and Good answer to, answer away! If you do not know the answer, wait for someone to answer, and learn a little. 2.6 - Is there anything I should keep in mind while answering? We don't want to see 'RTFM'. That isn't very helpful. Instead, guide the beginner to the place in the FM they should R :) 2.7 - I don't want to post a question if it is in an FAQ. Where should I look first? Look in the FAQ! Get acquainted with the 'perldoc' utility, and use it. It can save everyone time if you look in the Perl FAQs first, instead of having a list of people refer you to the Perl FAQs :) You can learn about 'perldoc' by typing: `perldoc perldoc' At your command prompt. You can also view documentation online at: http://www.perldoc.com and http://www.perl.com 3 - Other Resources 3.1 - What other websites may be useful to a beginner ? * Perl Home Page - http://www.perl.com * PerlMonks - http://www.perlmonks.org * Perldoc - http://www.perldoc.com * Perl Archives - http://www.perlarchives.com 3.2 - What resources may be harmful to a beginner? Beware of Perl4-like code-- You might find some script archives and unauthorized mirrors with old Perl4 versions of Selena Sol and Matt Wright scripts. Don't use those scripts. They are outdated and may even in some cases contain bugs or security problems since many may not have been updated in
Re: Unfriendly messages from people who should know better
I'm going to have to agree with Randal, here. Maybe I can chime in with a less acidic tone. If you don't want people to see your code, don't write it in a scripting language. Buy a commercial C compiler and write commercial grade code. Perl is a marvelous language for writing public domain code that just works well. As a beneficiary of the contributions to Perl, you should have some modicum of respect for the community. It's completely the wrong platform for writing secret proprietary code to distribute for profit. And there is no reason to. Other languages are intended for such purposes and do it better. But I stand by what I said, especially on these issues. perl2exe sucks. Trying to hide software written in Perl from your customers sucks. And having that message out there is important to me. Some people here will cheer me on for holding the banner so high on those, no matter what the method. Others will find my manner offensive about it, and still others will even disagree with both the manner and the goal. Oh well, this is life. _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Perl Compiler
I still say that Perl is not the language of choice for hiding code. Why not package the secret security risk code in a compiled C module of some sort? Then you can develop the rest of the code in Perl. - Original Message - From: Barrie Heck [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, January 03, 2002 5:42 AM Subject: Re: Perl Compiler We fully respect the conditions of the GPL and in fact have contributed greatly ourselves towards the development of applications based on perl, as well as many others. This specific requirement is security related, where a user with any intelligence, could read the source and make use of a security issue created by using sudo. Regards Barrie - Original Message - From: Randal L. Schwartz [EMAIL PROTECTED] To: [EMAIL PROTECTED]; Barrie Heck [EMAIL PROTECTED] Sent: Thursday, January 03, 2002 3:19 AM Subject: Re: Perl Compiler Barrie == Barrie Heck [EMAIL PROTECTED] writes: Barrie Hi, does anyone know of a perl compiler? Have written some Barrie perl code for a product and would not like the source Barrie available. So, you're making money using a product that thousands have contributed to, providing the source code so that hundreds of others can adapt it and fix it as they see fit, and yet you want to squander that by locking up *your* application? require 'standard/open_source_is_good-speech.pl'; Don't expect much help *here*. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 [EMAIL PROTECTED] 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] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Perl Compiler
If you must use perl, one thing you might try (although it's not a perfect solution) is obfuscation. Many people (even those in the open source community!) have been trying to make it very difficult if not impossible for people to read their perl code for years. Check out the perlmonks for example. http://www.perlmonks.com/index.pl?node=Obfuscated%20Code or just search google for perl obfuscation. Granted the folks at perlmonks seem to just do it for fun, but it has its roots in solving the very problem you are faced with. Also, there's a program called RJs Perl Obfuscator which supposedly will automate the process for you, but I couldnt say if it's any good since i've never used it (also it's in Alpha release currently and hasnt been worked on for a while...). http://www.projectgrid.com/download.cgi?R+686 - might be worth a shot anyway. The best part of this is you can have fairly safe code and you dont have to worry about being yelled at by the open source fanatics. good luck jeremy - Original Message - From: Barrie Heck [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, January 03, 2002 6:42 AM Subject: Re: Perl Compiler We fully respect the conditions of the GPL and in fact have contributed greatly ourselves towards the development of applications based on perl, as well as many others. This specific requirement is security related, where a user with any intelligence, could read the source and make use of a security issue created by using sudo. Regards Barrie - Original Message - From: Randal L. Schwartz [EMAIL PROTECTED] To: [EMAIL PROTECTED]; Barrie Heck [EMAIL PROTECTED] Sent: Thursday, January 03, 2002 3:19 AM Subject: Re: Perl Compiler Barrie == Barrie Heck [EMAIL PROTECTED] writes: Barrie Hi, does anyone know of a perl compiler? Have written some Barrie perl code for a product and would not like the source Barrie available. So, you're making money using a product that thousands have contributed to, providing the source code so that hundreds of others can adapt it and fix it as they see fit, and yet you want to squander that by locking up *your* application? require 'standard/open_source_is_good-speech.pl'; Don't expect much help *here*. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 [EMAIL PROTECTED] 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] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Perl Compiler
At 02:27 PM 1/3/02 -0600, Jeremy Webster wrote: If you must use perl, one thing you might try (although it's not a perfect solution) is obfuscation. Jeremy, You reminded me of something I once ran into. When setting up the backend for a website a couple of years ago one of the things the owners had me do was install something in Perl but not under GPL. All the variable names were written in an ascii binary code, e.g. instead of saying my ($name, $value) = split /=/,$namevalue; the code would say my ($110100010101101110100111, $11101001010001010110) = split /=/,$01010011101001010110; It was pretty obnoxious and did the trick. I wouldn't want to try and hack at that thing w/o first writing something to map all those identifiers into something legible. I mean it just added that extra layer... you could certainly do it but you'd have to really want to. Wish I could remember the name of the product. Marty Website Creation Made SIMPL(tm) http://face2interface.com/Home/Demo.shtml WebSafe Color Picker -- http://face2interface.com/WebSafe -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Perl Compiler
On Thu, 3 Jan 2002, Barrie Heck wrote: We fully respect the conditions of the GPL and in fact have contributed greatly ourselves towards the development of applications based on perl, as well as many others. This specific requirement is security related, where a user with any intelligence, could read the source and make use of a security issue created by using sudo. Well, you have that same problem with every single shell script on the same box. If it's a security issue, then the use of sudo needs to be restricted. There really isn't a good way to hide code with Perl, unless you create intentionally obfuscated code when you deploy the software. -- Brett http://www.chapelperilous.net/ Bedfellows make strange politicians. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Refreshing a Guest Book type page
Hello, I don't have a working example, this is for a friend. He says he has a guest book set up on his site. All is fine with it. People submit their entry, it takes you to a view page (dynamic, from the Perl program) where it shows you all the entries. But he says when people refresh that page, it posts the same message AGAIN. And it will keep doing that over and over. What can he put in his Perl code to make it stop doing that? So when people refresh the screen, it doesn't post their message again? It sounds like it's just keeping their message stored in the program's memory and refreshing that page makes it post again, but I'm not really sure how to make it stop. Thanks in advance for any help. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
