A Windows Vista forum. Vista Banter

Welcome to Vista Banter.

You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!

If you have any problems with the registration process or your account login, please contact contact support.

Go Back   Home » Vista Banter forum » Microsoft Windows Vista » Installation and Setup of Vista
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Installation and Setup of Vista Installation problems and questions using Windows Vista. (microsoft.public.windows.vista.installation_setup)

Trusted Installer



 
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old November 21st 07, 08:46 PM posted to microsoft.public.windows.vista.installation_setup
MikeV06
external usenet poster
 
Posts: 8
Default Trusted Installer

I looked at Users & Groups and do not find a user or group named
TrustedInstaller. However, that user is listed as owner of the C:\ drive.
Do I need to add a user or something?

Thanks.

Mike
  #2 (permalink)  
Old November 29th 07, 03:57 AM posted to microsoft.public.windows.vista.installation_setup
Darrell Gorter[MSFT]
external usenet poster
 
Posts: 685
Default Trusted Installer

Hello Mike,

This is part of the new ACLS to help improve security in Windows Vista

From this link below: I am posting a couple of paragraphs that talk about
Trusted Installer:

http://www.microsoft.com/technet/tec...L/default.aspx

Trusted Installer The Trusted Installer is actually a service, not a user,
even though you see permissions granted to it all over the file system.
Service hardening allows each service to be treated as a full-fledged
security principal that can be assigned permissions just like any other
user. For an overview of this feature, see the January 2007 issue of
TechNet Magazine. The book Windows Vista Security (Grimes and Johansson,
Wiley Press, 2007) explores service hardening in detail, including how it
is leveraged by other features, such as the firewall and IPsec.

Trusted Installer In Windows Vista, most of the OS files are owned by the
TrustedInstaller SID, and only that SID has full control over them. This is
part of the system integrity work that went into Windows Vista, and is
meant specifically to prevent a process that is running as an administrator
or Local System from automatically replacing the files. In order to delete
an operating system file, you thus need to take ownership of the file and
then add an ACE on it that lets you delete it. This provides a thin layer
of protection against a process that is running as LocalSystem and has a
System integrity label; a process that has lower integrity is not supposed
to be able to elevate itself to change ownership. Some services, for
instance, can run with medium integrity, even though they are running as
Local System. Such services cannot replace system files so an exploit that
takes over one of them canít replace operating system files, making it a
bit harder to install a rootkit or other malware on the system. It also
becomes more difficult for system administrators who are offended by the
mere presence of some system binary to remove that binary.

Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
| From: MikeV06
| Subject: Trusted Installer
| User-Agent: 40tude_Dialog/2.0.15.1
| MIME-Version: 1.0
| Content-Type: text/plain; charset="us-ascii"
| Content-Transfer-Encoding: 7bit
| Organization: None
| Date: Wed, 21 Nov 2007 15:46:38 -0600
| Message-ID:
| Archive: yes
| Newsgroups: microsoft.public.windows.vista.installation_setup
| NNTP-Posting-Host: r74-194-81-60.htspcmta01.hspvar.lr.dh.suddenlink.net
74.194.81.60
| Lines: 1
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP03.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.vista.installation_setup: 29474
| X-Tomcat-NG: microsoft.public.windows.vista.installation_setup
|
| I looked at Users & Groups and do not find a user or group named
| TrustedInstaller. However, that user is listed as owner of the C:\ drive.
| Do I need to add a user or something?
|
| Thanks.
|
| Mike
|

  #3 (permalink)  
Old December 7th 07, 02:24 PM posted to microsoft.public.windows.vista.installation_setup
MikeV06
external usenet poster
 
Posts: 8
Default Trusted Installer

Thank you for your post. The comments and the link are very useful.

Happy holidays.

Mike

On Thu, 29 Nov 2007 04:57:45 GMT, "Darrell Gorter[MSFT]" wrote:

Hello Mike,

This is part of the new ACLS to help improve security in Windows Vista

From this link below: I am posting a couple of paragraphs that talk about
Trusted Installer:

http://www.microsoft.com/technet/tec...L/default.aspx

Trusted Installer The Trusted Installer is actually a service, not a user,
even though you see permissions granted to it all over the file system.
Service hardening allows each service to be treated as a full-fledged
security principal that can be assigned permissions just like any other
user. For an overview of this feature, see the January 2007 issue of
TechNet Magazine. The book Windows Vista Security (Grimes and Johansson,
Wiley Press, 2007) explores service hardening in detail, including how it
is leveraged by other features, such as the firewall and IPsec.

Trusted Installer In Windows Vista, most of the OS files are owned by the
TrustedInstaller SID, and only that SID has full control over them. This is
part of the system integrity work that went into Windows Vista, and is
meant specifically to prevent a process that is running as an administrator
or Local System from automatically replacing the files. In order to delete
an operating system file, you thus need to take ownership of the file and
then add an ACE on it that lets you delete it. This provides a thin layer
of protection against a process that is running as LocalSystem and has a
System integrity label; a process that has lower integrity is not supposed
to be able to elevate itself to change ownership. Some services, for
instance, can run with medium integrity, even though they are running as
Local System. Such services cannot replace system files so an exploit that
takes over one of them canít replace operating system files, making it a
bit harder to install a rootkit or other malware on the system. It also
becomes more difficult for system administrators who are offended by the
mere presence of some system binary to remove that binary.

Thanks,
Darrell Gorter[MSFT]

  #4 (permalink)  
Old June 20th 13, 09:08 AM posted to microsoft.public.windows.vista.installation_setup
[email protected]
external usenet poster
 
Posts: 1
Default Trusted Installer

Hello Darrell,

I know this post is very old. But still, want to ask you this. If I wanted to add a registry that has TrustedInstaller as ownership, I wanted to change the ownership to Administrator first, only then I can add it. But do I have a provision of doing this job in command prompt.?? Or do I have any executables to achieve this. I wanted to do the job only in command prompt.

Thanks,
Badhri
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT. The time now is 11:57 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.Search Engine Optimization by vBSEO 3.0.0 RC6
Copyright ©2004-2018 Vista Banter.
The comments are property of their posters.