head	1.7;
access;
symbols
	RELEASE_6_2_0:1.6
	RELEASE_6_1_0:1.6
	RELEASE_5_5_0:1.6
	RELEASE_6_0_0:1.6
	RELEASE_5_4_0:1.6
	RELEASE_4_11_0:1.6
	RELEASE_5_3_0:1.6
	RELEASE_4_10_0:1.6
	RELEASE_5_2_1:1.6
	RELEASE_5_2_0:1.6
	RELEASE_4_9_0:1.6
	RELEASE_5_1_0:1.6
	RELEASE_4_8_0:1.6
	RELEASE_5_0_0:1.6
	RELEASE_4_7_0:1.6
	RELEASE_4_6_2:1.6
	RELEASE_4_6_1:1.6
	RELEASE_4_6_0:1.6
	RELEASE_5_0_DP1:1.4
	RELEASE_4_5_0:1.1
	RELEASE_4_4_0:1.1;
locks; strict;
comment	@# @;


1.7
date	2006.12.12.16.38.12;	author vd;	state dead;
branches;
next	1.6;

1.6
date	2002.05.23.22.25.33;	author mbr;	state Exp;
branches;
next	1.5;

1.5
date	2002.05.16.10.59.57;	author mbr;	state Exp;
branches;
next	1.4;

1.4
date	2002.02.13.21.40.08;	author mbr;	state Exp;
branches;
next	1.3;

1.3
date	2002.02.05.16.18.42;	author mbr;	state Exp;
branches;
next	1.2;

1.2
date	2002.02.03.21.59.27;	author mbr;	state Exp;
branches;
next	1.1;

1.1
date	2001.08.31.11.42.15;	author jedgar;	state Exp;
branches;
next	;


desc
@@


1.7
log
@Remove expired www/frontpage and all frontpage ports:

2006-12-01 www/frontpage: Microsoft Frontpage Extensions have reached their End-of-Life

portuguese/frontpage-pt_BR
www/frontpage-ar
www/frontpage-de
www/frontpage-es
www/frontpage-fr
www/frontpage-he
www/frontpage-it
www/frontpage-ja
www/frontpage-ko
www/frontpage-nl
www/frontpage-sv
www/frontpage-th
www/frontpage-zh
www/mod_frontpage
www/mod_frontpage-rtr
www/mod_frontpage2-rtr
@
text
@************************************************************************

1.)

Check your httpd.conf, if you have included a ResourceConfig and
AccessConfig. If you do not have these files, you'll have to add
these lines to make frontpage extensions working properly. These
lines are commented out in a default config, so you'll have to
activate them again. If you have some real ResourceConfig and
AccessConfig, you can skip this part.

ResourceConfig /dev/null
AccessConfig /dev/null


2.)

You'll also need to change AllowOverride under
<Directory "%%PREFIX%%/www/data"> ( or the place where you
moved your webservers ) from None to at least:

AllowOverride AuthConfig Limit Indexes Options

Don't use "AllowOverride All" if you have a server environment
with customers, since this can be a security risk If you use
this, they can enable mod_php4 etc. themself with .htaccess files.


3.)

You can turn off/on the extensions and the frontpage administration
per site in httpd.conf and per virtual server. FrontPageAdminDisable
is the default if no option is given.

FrontPageEnable         # Enable FP Extensions Client publish
FrontPageDisable        # Disable FP Extensions Client publish
FrontPageAdminEnable    # Enable FP Extensions Admin web site
FrontPageAdminDisable   # Disable FP Extensions Admin web site

If no key word options are present in the httpd.conf file the default of
FrontPageDisable and FrontPageAdminDisable is used resulting in a working
Apache environment where the complete frontpage environment is disabled.


4.)

After you have made these changes, you'll have to execute:

%%PREFIX%%/frontpage/version5.0/fp_install.sh to build the base
apache/frontpage web site and to setup frontpage users and admins.
You can also run this to add virtual hosts to the apache/frontpage
system.


5.)

If you have installed the port in another PREFIX than "/usr/local"
you have to create a symlink. Microsoft has hardcoded the local
path in their binarys. If you do not use fp_install.sh, you have
to create the link manually:

ln -s %%PREFIX%%/frontpage /usr/local/frontpage

************************************************************************
@


1.6
log
@Add better explanations. Ideas from barbish@@a1poweruser.com
@
text
@@


1.5
log
@Add a note about the hardcoded /usr/local in the frontpage binaries.
@
text
@d3 2
d7 4
a10 1
these lines to make frontpage extensions working properly:
d16 2
d19 1
a19 1
<Directory "/usr/local/www/data"> ( or the place where you
d24 6
d35 4
a38 4
FrontPageEnable		# Enable Frontpage Extensions
FrontPageDisable	# Disable Frontpage Extensions
FrontPageAdminEnable	# Enable Frontpage Extensions fpadmcgi.exe
FrontPageAdminDisable	# Disable Frontpage Extensions fpadmcgi.exe
d40 6
d49 5
a53 1
%%PREFIX%%/frontpage/version5.0/fp_install.sh
d55 1
@


1.4
log
@Add some notes about http.conf and what the user has to do
after installation.

Noted by:	Scot W. Hetzel <hetzels@@westbend.net>
@
text
@d30 9
a38 1
/usr/local/frontpage/version5.0/fp_install.sh
@


1.3
log
@Sigh. Commit the update. I hope I will not find more security issues.
@
text
@d3 15
d26 5
@


1.2
log
@Upgrade to version 1.6 which I just have finished today.

Reviewed by:		some frontpage users
@
text
@d3 3
a5 4
mod_frontpage improved has been installed. You can turn off/on the
extensions and the frontpage administration per site in httpd.conf
and per virtual server. FrontPageAdminDisable is the default if no
option is given.
@


1.1
log
@Add mod_frontpage, a modular version of FrontPage extentions.

PR:		29202
Submitted by:	Martin Blapp <mb@@imp.ch>
@
text
@d3 4
a6 4
The BSDI FrontPage Extentions require that libcrypt.* be linked to the
libdescrypt.* libraries.  The fpsrvadm.exe program can only create DES
passwords, but the Apache server is unable to use them when libcrypt.*
are linked to the libscrypt.* libraries.
d8 4
a11 3
A new apache.sh.sample has been installed. Please replace your own
apache.sh with this script. The frontpage suid key generation is
needed by mod_frontpage. Without it it doesn't work.
@

