Vista: more issues

  • Thread starter Thread starter Jack
  • Start date Start date
J

Jack

That does not make sense to me.
How about you?
Here is the scenario:
================
2 users:
user A standard user, UAC turned ON
user B administrator, UAC turned ON.

Logging as a user A
I can open registry (regedit) without any prompt and delete any key under
HKEY_CURRENT_USER
Logging as a user B (adminstrator):
As soon as I want to open the registry, UAC kicks in, asking ME for
permission to continue.

Does it mean that (UAC on behalf on Microsoft) considers an administrator to
be more stupid then a standard user???
Please tell me that it is not so.
Jack
 
Hi Jack,

That is as expected. The thing to understand is an administrator is running
as a LPU but some applications will request full rights for that user at
which time the administrator gets prompted to run the app using their full
permissions, not the LPU set.
When the LPU user goes to open regedit, that's it, they are running at thier
max permissions anyway. They will only see what their permission let them,
and are shouldn't to be able to modify anything under HKLM ebut they can
read many of the values there.

So the thing about UAC is it lets you run as a LPU even if a admin, but
applications can specify that you should be prompted to run as full
rights... those "full rights" are *your* full rights, not absolutes.
 
Jack said:
That does not make sense to me.
How about you?
Here is the scenario:
================
2 users:
user A standard user, UAC turned ON
user B administrator, UAC turned ON.

Logging as a user A
I can open registry (regedit) without any prompt and delete any key under
HKEY_CURRENT_USER
Logging as a user B (adminstrator):
As soon as I want to open the registry, UAC kicks in, asking ME for
permission to continue.

Does it mean that (UAC on behalf on Microsoft) considers an administrator
to be more stupid then a standard user???
Please tell me that it is not so.
Click to expand...

You should be asking this in a Vista newsgroup. It has nothing to do with
VB since you're talking about RegEdit.

An administrator has write access to all of the Registry whereas a standard
user doesn't. When you start RegEdit, it has no idea what you're going to
use it to do, and what you do *could* have an affect on other users, so UAC
kicks in and prompts for permission. If you're logged into Windows as a
standard user, most areas of the Registry are read-only, so no prompt is
necessary (unless, of course, you run RegEdit as an administrator).

The basic concept behind UAC is that if you're trying to do something, or
could potentially do something, that could affect other users, you have to
OK it.
 
Hello,

UAC isn't about protecting users from themselves. It's about putting
administrative users in control over what programs get to use their admin
rights.

The purpose of the UAC prompt is to confirm with you (as the administrative
user) that you indeed requested that a program start with admin rights.

As such, if a program starts that does not demand admin rights if they are
not available (like regedit), there will not be a prompt.

- JB
 
MikeD said:
You should be asking this in a Vista newsgroup. It has nothing to do with
VB since you're talking about RegEdit.
Click to expand...


Didn't notice it was cross-posted. Still irrelevant in a VB newsgroup
though.
 
MikeD said:
Didn't notice it was cross-posted. Still irrelevant in a VB newsgroup
though.
Click to expand...

Well he has posted other threads where he has indicated various issues he
has with Vista and registry, so this is obviously him trying out regedit to
read those keys and being perplexed there as well. It's a direct result of
his programming attempts and is really him trying to understand tools used
for/by developers and how Vista registry and UAC works. In *context* of
that, it doesn't seem off topic at all .

From the developer perspective it means that regedit has the UAC permission
request set to "highestAvailable", e.g:
<requestedExecutionLevel level="highestAvailable" uiAccess="false" />

And a quick look inside regedit's manifest shows exactly that :)
Does that make it "developer" enough for ya ? ;)
 
Heh, you're such a dick.

|
| | >
| > | >>
| >> | >>> That does not make sense to me.
| >>> How about you?
| >>> Here is the scenario:
| >>> ================
| >>> 2 users:
| >>> user A standard user, UAC turned ON
| >>> user B administrator, UAC turned ON.
| >>>
| >>> Logging as a user A
| >>> I can open registry (regedit) without any prompt and delete any key
| >>> under HKEY_CURRENT_USER
| >>> Logging as a user B (adminstrator):
| >>> As soon as I want to open the registry, UAC kicks in, asking ME for
| >>> permission to continue.
| >>>
| >>> Does it mean that (UAC on behalf on Microsoft) considers an
| >>> administrator to be more stupid then a standard user???
| >>> Please tell me that it is not so.
| >>
| >> You should be asking this in a Vista newsgroup. It has nothing to do
| >> with VB since you're talking about RegEdit.
| >
| >
| > Didn't notice it was cross-posted. Still irrelevant in a VB newsgroup
| > though.
| >
|
| Well he has posted other threads where he has indicated various issues he
| has with Vista and registry, so this is obviously him trying out regedit
to
| read those keys and being perplexed there as well. It's a direct result
of
| his programming attempts and is really him trying to understand tools used
| for/by developers and how Vista registry and UAC works. In *context* of
| that, it doesn't seem off topic at all .
|
| From the developer perspective it means that regedit has the UAC
permission
| request set to "highestAvailable", e.g:
| <requestedExecutionLevel level="highestAvailable" uiAccess="false" />
|
| And a quick look inside regedit's manifest shows exactly that :)
| Does that make it "developer" enough for ya ? ;)
|
|
|
|
|
|
|
|
|
|
|
 
Mike, I do have problem with Vista as a programmer.
If you missed my other post, please read this and let me know what you
think.:
---------------- cut from other thread ----
I have run more tests and I cannot arrive to any conclusion.
The main problem:
Logging as a standard user my code (IDE and compiled executable) cannot read
one value from the registry (return is 2= file not found) although the value
exists in the registry (under HKCU key) and I can change, modify or delete
it using regedit.
But there is not a problem reading another value (the same type) from HKLM
key.

Logging as an administrator the registry value which was not read above is
being read without any problem.

Please help me to understand that. My hair turning grey!!!!
Jack
----------------------------------
 
Bill McCarthy said:
Well he has posted other threads where he has indicated various issues he
has with Vista and registry, so this is obviously him trying out regedit
to read those keys and being perplexed there as well. It's a direct
result of his programming attempts and is really him trying to understand
tools used for/by developers and how Vista registry and UAC works. In
*context* of that, it doesn't seem off topic at all .

From the developer perspective it means that regedit has the UAC
permission request set to "highestAvailable", e.g:
<requestedExecutionLevel level="highestAvailable" uiAccess="false" />

And a quick look inside regedit's manifest shows exactly that :)
Does that make it "developer" enough for ya ? ;)
Click to expand...

How do you check regedit's manifest, Bill?
Thanks,
Jack
 
Jack said:
How do you check regedit's manifest, Bill?
Thanks,
Jack
Click to expand...

I just open the exe in Visual Studio and read the RT_MANIFEST. Visual
Studio by default opens the resources of an exe.
There's other tools out there that do the same, or you could use win API.
This is regedit's embedded manifest:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!-- Copyright (c) Microsoft Corporation -->
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity
processorArchitecture="x86"
version="1.0.0.0"
name="Microsoft.Windows.Regedit" type="win32" />
<description>Registry Editor</description>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
publicKeyToken="6595b64144ccf1df"
processorArchitecture="x86"
/>
</dependentAssembly>
</dependency>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel
level="highestAvailable"
uiAccess="false"
/>
</requestedPrivileges>
</security>
</trustInfo>
</assembly>
 
He's not using .NET you @ss. Even you should have known that about this guy
having posted VB6 so often in the past. Stop being a .NET troll. His best
bet would be ResourceHacker.

Stop bringing any version of .NET into this group, bitch.

|
| | >>
| >> From the developer perspective it means that regedit has the UAC
| >> permission request set to "highestAvailable", e.g:
| >> <requestedExecutionLevel level="highestAvailable" uiAccess="false" />
| >>
| >> And a quick look inside regedit's manifest shows exactly that :)
| >> Does that make it "developer" enough for ya ? ;)
| >>
| >
| > How do you check regedit's manifest, Bill?
| > Thanks,
| > Jack
|
| I just open the exe in Visual Studio and read the RT_MANIFEST. Visual
| Studio by default opens the resources of an exe.
| There's other tools out there that do the same, or you could use win API.
| This is regedit's embedded manifest:
|
| <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
| <!-- Copyright (c) Microsoft Corporation -->
| <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
| <assemblyIdentity
| processorArchitecture="x86"
| version="1.0.0.0"
| name="Microsoft.Windows.Regedit" type="win32" />
| <description>Registry Editor</description>
| <dependency>
| <dependentAssembly>
| <assemblyIdentity
| type="win32"
| name="Microsoft.Windows.Common-Controls"
| version="6.0.0.0"
| publicKeyToken="6595b64144ccf1df"
| processorArchitecture="x86"
| />
| </dependentAssembly>
| </dependency>
| <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
| <security>
| <requestedPrivileges>
| <requestedExecutionLevel
| level="highestAvailable"
| uiAccess="false"
| />
| </requestedPrivileges>
| </security>
| </trustInfo>
| </assembly>
|
 
Type OSVERSIONINFO
OSVSize As Long
dwVerMajor As Long .
dwVerMinor As Long
dwBuildNumber As Long
PlatformID As Long
szCSDVersion As String * 128
End Type
 
Hi Jack,

VB6 added some good stuff like returning arrays from functions and some
handy string functions. I've never noticed any performance issues with it.

Oh and ignore Casey (aka Kevin). He gets all worked up if people use Visual
Studio. Seems my answering your question has got him blowing yet another
gasket <g>
 
Yeah, I see you stalking my old blog. IP logging is a beautiful thing. Do
I need to get a restraining order? I'm willing to be if we were face to
face, you're piss poor attitude would suddenly change, since you are a
bloody coward.

| Hi Jack,
|
| VB6 added some good stuff like returning arrays from functions and some
| handy string functions. I've never noticed any performance issues with it.
|
| Oh and ignore Casey (aka Kevin). He gets all worked up if people use
Visual
| Studio. Seems my answering your question has got him blowing yet another
| gasket <g>
|
|
| | > In fact I am not using vbasic6, I've found it overblown and slow.
| > I am using vbasic 5.
| > Jack
| >
| > | >> He's not using .NET you @ss. Even you should have known that about
this
| >> guy
| >> having posted VB6 so often in the past. Stop being a .NET troll. His
| >> best
| >> bet would be ResourceHacker.
| >>
| >> Stop bringing any version of .NET into this group, bitch.
| >>
| >> | >> |
| >> | | >> | >>
| >> | >> From the developer perspective it means that regedit has the UAC
| >> | >> permission request set to "highestAvailable", e.g:
| >> | >> <requestedExecutionLevel level="highestAvailable"
uiAccess="false"
| >> />
| >> | >>
| >> | >> And a quick look inside regedit's manifest shows exactly that :)
| >> | >> Does that make it "developer" enough for ya ? ;)
| >> | >>
| >> | >
| >> | > How do you check regedit's manifest, Bill?
| >> | > Thanks,
| >> | > Jack
| >> |
| >> | I just open the exe in Visual Studio and read the RT_MANIFEST.
Visual
| >> | Studio by default opens the resources of an exe.
| >> | There's other tools out there that do the same, or you could use win
| >> API.
| >> | This is regedit's embedded manifest:
| >> |
| >> | <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
| >> | <!-- Copyright (c) Microsoft Corporation -->
| >> | <assembly xmlns="urn:schemas-microsoft-com:asm.v1"
| >> manifestVersion="1.0">
| >> | <assemblyIdentity
| >> | processorArchitecture="x86"
| >> | version="1.0.0.0"
| >> | name="Microsoft.Windows.Regedit" type="win32" />
| >> | <description>Registry Editor</description>
| >> | <dependency>
| >> | <dependentAssembly>
| >> | <assemblyIdentity
| >> | type="win32"
| >> | name="Microsoft.Windows.Common-Controls"
| >> | version="6.0.0.0"
| >> | publicKeyToken="6595b64144ccf1df"
| >> | processorArchitecture="x86"
| >> | />
| >> | </dependentAssembly>
| >> | </dependency>
| >> | <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
| >> | <security>
| >> | <requestedPrivileges>
| >> | <requestedExecutionLevel
| >> | level="highestAvailable"
| >> | uiAccess="false"
| >> | />
| >> | </requestedPrivileges>
| >> | </security>
| >> | </trustInfo>
| >> | </assembly>
| >> |
| >>
| >>
| >
| >
|
 
cross-posted????
Click to expand...

You have included more that one group in the distribution -
microsoft.public.vb.general.discussion and
microsoft.public.windows.vista.general

Don't worry, cross-posting is considered as much better than multi-posting.
 
That does not make sense to me.
How about you?
Here is the scenario:
================
2 users:
user A standard user, UAC turned ON
user B administrator, UAC turned ON.

Logging as a user A
I can open registry (regedit) without any prompt and delete any key under
HKEY_CURRENT_USER
Logging as a user B (adminstrator):
As soon as I want to open the registry, UAC kicks in, asking ME for
permission to continue.

Does it mean that (UAC on behalf on Microsoft) considers an administrator to
be more stupid then a standard user???
Click to expand...

No, it means that the Administrator user will be modifying the real
registry, while the standard user will be modifying the 'fake'
(virtual) one...
 
Back
Top