RE: [cobalt-users] Frontpage + SSL

["admin" <admin@xxxxxxxxxxxxx>]

I think this info will help:

I'm getting a front page error when submitting forms.

One possible cause is that the way that Front Page creates it's
configuration files does not get the site's information correct, and
tries to use an incorrect value in form/mail scripts. It will be
necessary to log into the server via telnet to correct this, if this is
the problem in your case.


telnet into the server
use the su command to gain root access
change into the /usr/local/frontpage directory
You will see files in the format of www.domain.com:80.cnf, use your
preferred text editor and open the .cnf file to the afflicted site. Look
for SMTPhost, and verify that it is NOT set to localhost, it should have
the fully qualified name of the mail server for the site. Also the last
line of the .cnf file should read MailSender=siteadmin@xxxxxxxxxxxxxx
If SSL is also running on that site you will have to do one extra step.
Make a copy of the .cnf file for that site. Type: cp
www.domain.com:80.cnf www.domain.com:443.cnf

-----Original Message-----
From: admin [mailto:admin@xxxxxxxxxxxxx]
Sent: Tuesday, March 12, 2002 11:03 AM
To: admin@xxxxxxxxxxxxx
Subject: raq4 frontpage SSL error




-----Original Message-----
From: admin [mailto:admin@xxxxxxxxxxxxx]
Sent: Tuesday, March 12, 2002 10:47 AM
To: admin@xxxxxxxxxxxxx
Subject: raq4


RaQ4
I installed all the patches without errors.
Frontpage form works fine - will go to https confirmation page, data
loads to txt file, email is sent - all is well... but only when that
form is called from http. When form is called from https, I get the
following error...

  Cannot open "/usr/local/frontpage/we443.cnf": no such file or folder.

Now, I read the archives and found this gem... is this my fix? Seems
dated - since I have applied all the patches. Or, is there something
amiss with my patching? Thanks for all your help!

Mitch

>>>>>>>>>
[cobalt-users] RaQ3 SSL and FP2K
Will DeHaan will@xxxxxxxxxx
Wed, 05 Apr 2000 12:28:23 -0700

Forms can not be submitted securely unless the following file is
created:

  /usr/local/frontpage/we443.cnf

If you need this functionality now, and can't wait for a RaQ 3 OS Update
package (I don't know a release date for the next update), please telnet
or ssh to your RaQ 3.  Authenticate as 'admin'.  Type "su -" and
re-enter your admin password to gain root access.

Cut and paste the following commands to the shell prompt:

echo "vti_encoding:SR|utf8-nl" > /usr/local/frontpage/we443.cnf echo
"frontpageroot:/usr/local/frontpage/version4.0" \  >>
/usr/local/frontpage/we443.cnf echo
"serverconfig:/etc/httpd/conf/fpx.httpd.conf" \  >>
/usr/local/frontpage/we443.cnf echo "authoring:enabled" \  >>
/usr/local/frontpage/we443.cnf echo "servertype:apache" \  >>
/usr/local/frontpage/we443.cnf echo "SMTPHost: 127.0.0.1" \  >>
/usr/local/frontpage/we443.cnf exit echo " "

That's it!

Network Administrator		Email: admin@xxxxxxxxxxxxx
Beachlink			Phone: 252-261-0744 ext.202
3915 Welch St. P.O. Box 1528	Fax:   252-261-1365
Kitty Hawk, NC 27949



-----Original Message-----
From: cobalt-users-admin@xxxxxxxxxxxxxxx
[mailto:cobalt-users-admin@xxxxxxxxxxxxxxx] On Behalf Of Francisco
Sánchez
Sent: Saturday, March 16, 2002 8:13 AM
To: cobalt-users@xxxxxxxxxxxxxxx
Subject: [cobalt-users] Frontpage + SSL


Hi,

I have run the rpm -Va command in my RaQ4 server and have found that it
complaints because we443.cnf is missing.

I understand that this file would enable SSL authoring with Frontpage.

Well, I have searched through the list and found that we443.cnf can be
created with this:

echo "vti_encoding:SR|utf8-nl" > /usr/local/frontpage/we443.cnf echo
"frontpageroot:/usr/local/frontpage/version4.0" \  >>
/usr/local/frontpage/we443.cnf echo
"serverconfig:/etc/httpd/conf/fpx.httpd.conf" \  >>
/usr/local/frontpage/we443.cnf echo "authoring:enabled" \  >>
/usr/local/frontpage/we443.cnf echo "servertype:apache" \  >>
/usr/local/frontpage/we443.cnf echo "SMTPHost: 127.0.0.1" \  >>
/usr/local/frontpage/we443.cnf

I have done so and rmp -Va no longer complaints about it.  However, I am
unable to use SSL for authoring webs (of course the webs I am trying do
have an SSL cert.).

On the other hand, I have found that by renaming files in
/usr/local/frontpage like www.domain.com:80.cnf to
www.domain.com:443.cnf SSL authoring is enabled.

But, shouldn't this file (the one with www.domain.com:443.cnf) be
created automatically when enabling Frontpage extensions for a site?

Also, SInce I have several Frontpage webs with the same IP address, only
the main one accepts SSL authoring.  SHould there be any way to enable
SSL for the other sites?  I understand that only one site per IP can
have SSL in port 443, but my question is if there is any way to enable
the other sites in the same IP by using different ports for SSL.  Has
anyone achieved this?

Best regards,

Francisco Sánchez

_______________________________________________
cobalt-users mailing list
cobalt-users@xxxxxxxxxxxxxxx
To Subscribe or Unsubscribe, please go to:
http://list.cobalt.com/mailman/listinfo/cobalt-users