restricting hyper links

  • Thread starter Thread starter Dave-o
  • Start date Start date
D

Dave-o

hi guys,
i am having a problem with office hyperlinks circumventing group
policy on my network.Heres the scenario :

1.User on locked down work station fires up frontpage 2002 and creates
a hyperlink to a network folder.
2.Now the user clicks on this hyper link and viola!A windows explorer
shell opens and they can browse network neighborhood and see machine
names etc as well as the entire folder structure above the linked to
folder.All machines are running win2k.

Now in a normal LAN situation this probably isnt a problem but on this
network a good proportion of the users are considered 'hostile' and
use this method to gather intelligence and probe the network.In the
office Xp ADM's that come in the Office Resource Kit i can stop
hyperlinks in word and excel but obviously i cant stop ALL hyperlinks
in frontpage.Question is,can i limit hyperlinks to ONLY address's
starting with http:// ?
I have trashed azround but cant see any way to do this ...yet.
Thanks in advance.
 
-----Original Message-----
hi guys,
i am having a problem with office hyperlinks
circumventing group policy on my network.Heres the
scenario :

1.User on locked down work station fires up frontpage
2002 and creates a hyperlink to a network folder.
2.Now the user clicks on this hyper link and viola!A
windows explorer shell opens and they can browse network
neighborhood and see machine names etc as well as the
entire folder structure above the linked to
folder.All machines are running win2k.

Now in a normal LAN situation this probably isnt a
problem but on this network a good proportion of the
users are considered 'hostile' and use this method to
gather intelligence and probe the network.In the
office Xp ADM's that come in the Office Resource Kit
i can stop hyperlinks in word and excel but obviously i
cant stop ALL hyperlinks in frontpage.Question is,can i
limit hyperlinks to ONLY address's
starting with http:// ?
I have trashed azround but cant see any way to do
this ...yet.
Click to expand...

First, it seems that you need to take a serious look at
your sharename and file system permissions. Keep people
out at the server, and not at the workstation. Because
the "hostiles" have physical access to their workstations
and network connections, anything can (and probably will)
happen there.

Another approach would be to get rid of your sharenames,
install IIS, and let the "hostiles" access the files by
HTTP. You could set up security on FrontPage Webs so only
the people you want can update them.

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