FP Publishing Security Problems

J

JasonG

Hey all

I have a problem....I have a website that I am hosting myself on my own web server at home. I have been updating it through VNC and sometimes through my FTP site. This took quite a while, so I figured, why not use the Publish Web option in FrontPage
My problem is: it didnt ask for a single password or anything. I have published various other sites through my work with FrontPage, and everytime it would prompt for a password. This is a serious problem because anyone can publish to my site! I just had someone else try it on their computer, and they successfully published. I checked my local securities and there arent any obvious problems screaming "ANYONE CAN PUBLISH!" at me. For all of the C drive, I have only the local admins, and the groups: NETWORK, SERVICE, and SYSTEM set up with permissions
The site is hosted through IIS 5.0. Are there known security problems with that? Or is it a local permissions problem? Please help

Thanks
JasonG
 
K

Kevin Spencer

You had better get with the Network Admin for your site. Apparently, they've
left it wide open. This in not a bug or flaw in FrontPage or IIS. It's a
mistake by a network Administrator.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

JasonG said:
Hey all,

I have a problem....I have a website that I am hosting myself on my
Click to expand...
own web server at home. I have been updating it through VNC and sometimes
through my FTP site. This took quite a while, so I figured, why not use the
Publish Web option in FrontPage?
My problem is: it didnt ask for a single password or anything. I have
Click to expand...
published various other sites through my work with FrontPage, and everytime
it would prompt for a password. This is a serious problem because anyone
can publish to my site! I just had someone else try it on their computer,
and they successfully published. I checked my local securities and there
arent any obvious problems screaming "ANYONE CAN PUBLISH!" at me. For all
of the C drive, I have only the local admins, and the groups: NETWORK,
SERVICE, and SYSTEM set up with permissions.
The site is hosted through IIS 5.0. Are there known security problems
Click to expand...
with that? Or is it a local permissions problem? Please help!
 
J

JasonG

I am the site/network admin! Do you know how to close
this up? I'm pretty new to this.

Thanks
 
J

Jim Buyens

Try this:

1. Open your remote site in FrontPage.
2. Choose Server from the Tools menu,and then Permissions.
3. Configure the security you want.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------



-----Original Message-----
Hey all,

I have a problem....I have a website that I am
Click to expand...
hosting myself on my own web server at home. I have been
updating it through VNC and sometimes through my FTP
site. This took quite a while, so I figured, why not use
the Publish Web option in FrontPage?
My problem is: it didnt ask for a single password or
Click to expand...
anything. I have published various other sites through my
work with FrontPage, and everytime it would prompt for a
password. This is a serious problem because anyone can
publish to my site! I just had someone else try it on
their computer, and they successfully published. I
checked my local securities and there arent any obvious
problems screaming "ANYONE CAN PUBLISH!" at me. For all
of the C drive, I have only the local admins, and the
groups: NETWORK, SERVICE, and SYSTEM set up with
permissions.
The site is hosted through IIS 5.0. Are there known
Click to expand...
security problems with that? Or is it a local permissions
problem? Please help!
 
Top