1 btokarchuk Aug 18, 2004 01:01
3 isaac Aug 18, 2004 17:47
What follows is a very insecure hack! It allows cookies set by b2evolution to be accessible by other websites, which could give away your username and password to another site.
However, if you're setting up the site on a local trusted intranet that is not accessible from the outside, then it's not a big deal.
Find this part of conf/_advanced.php:
$cookie_domain = ($basehost == 'localhost') ? '' : '.'. $basehost;
Change that to this:
$cookie_domain = ($basehost == 'MACHINE_NAME_GOES_HERE') ? '' : '.'. $basehost;
Then cookies will work fine. (Or, as Graham suggested, give it a machine name that is a fully-qualified tld name.)
4 btokarchuk Aug 19, 2004 02:25
Ok cool, that did it.
thanks,
I don't think giving it a qualified domain name is going to work since it's an internal machine. Or am i missing something about domain names?
ie if i called it linuxbox.com or some other registered domain name, the domain name would a) have to be registered and thus reach out to the name servers and then come back, through our totally blockaded firewall :) or b) i would have to hack everyones hosts file to point to the machine cuz their browsers would be trying to resolve the address outside of intranet... or is my understanding of things off??
Brent.
5 graham Aug 19, 2004 07:18
I've not used linux for several years, but I know that several people have set their domains to be domain.name - it doesn't have to be .com or whatever, the request will be sent to the webserver or proxy first, so it just has to be set up on the actual server the script is running on.
You just need to make sure the machine name is a fully qualified domian name.