Project ActiveX controls shows as unsigned controls?

[Will]

I recently installed Project Server 2003 for a clinet. When first attaching
to the site from my system I was unable to fully load the page due to having
my "Unsigned ActiveX control" setting to disabled. Why would a Microsoft
product show up with unsigned ActiveX controls?

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...1f1be13ce9&dg=microsoft.public.project.server

 

[Mark Everett | PMP]

Will -

We work closely with Microsoft and asked them the same question. This
is the response:

"The controls are signed. However, The Pjprint11.dll isn't marked safe
for scripting. There's a big difference. What this means is that the
"Initialize and script ActiveX controls not marked as safe for
scripting" option needs to be set to enable or prompt. This is the way
it's been since RTM and there's no difference up to and through the
SP2a release."

There is more to the message but it reveals a potential exploit that I
don't want to post in a public forum.

Mark Everett
www.quantumpm.com

 

[Mark Everett | PMP]

Will -

We work closely with Microsoft and asked them the same question. This
is the response:

"The controls are signed. However, The Pjprint11.dll isn't marked safe
for scripting. There's a big difference. What this means is that the
"Initialize and script ActiveX controls not marked as safe for
scripting" option needs to be set to enable or prompt. This is the way
it's been since RTM and there's no difference up to and through the
SP2a release."

There is more to the message but it reveals a potential exploit that I
don't want to post in a public forum.

Mark Everett
www.quantumpm.com