![]() | |
![]() |
| | Thread Tools | Display Modes |
#31
| |||
| |||
|
|
Sundial Services <i... (AT) sundialservices (DOT) com> wrote innews:47857d15 (AT) pnews (DOT) thedbcommunity.com: Vista is the first Windows release that really embraces this... that grabs on the notion that "even though this is 'your' computer, there are things that 'you' should not be able to do" and will not let go. I prefer to phrase this as "your day-to-day normal login". "You" can still do almost anything by logging in as administrator, but this is now strongly discouraged in order to create a barrier between automatically-run malicious programs and critical system resources. But there are a few things that I think are overzealously protected. The one that I find problematic is MS-signed drivers. Without their signature, a driver won't load at boot time unless you take the system into developer mode and approve the driver with each boot. This should be something the owner of the machine can sign once to approve, presumably with suitable barriers to prevent a mindless click-through by a regular user. Without this, there's a significant barrier to entry by freeware and open source hardware driver writers. |
#32
| |||
| |||
|
|
Sundial Services <i... (AT) sundialservices (DOT) com> wrote innews:47857d15 (AT) pnews (DOT) thedbcommunity.com: Vista is the first Windows release that really embraces this... that grabs on the notion that "even though this is 'your' computer, there are things that 'you' should not be able to do" and will not let go. I prefer to phrase this as "your day-to-day normal login". "You" can still do almost anything by logging in as administrator, but this is now strongly discouraged in order to create a barrier between automatically-run malicious programs and critical system resources. But there are a few things that I think are overzealously protected. The one that I find problematic is MS-signed drivers. Without their signature, a driver won't load at boot time unless you take the system into developer mode and approve the driver with each boot. This should be something the owner of the machine can sign once to approve, presumably with suitable barriers to prevent a mindless click-through by a regular user. Without this, there's a significant barrier to entry by freeware and open source hardware driver writers. |
#33
| |||
| |||
|
|
Sundial Services <i... (AT) sundialservices (DOT) com> wrote innews:47857d15 (AT) pnews (DOT) thedbcommunity.com: Vista is the first Windows release that really embraces this... that grabs on the notion that "even though this is 'your' computer, there are things that 'you' should not be able to do" and will not let go. I prefer to phrase this as "your day-to-day normal login". "You" can still do almost anything by logging in as administrator, but this is now strongly discouraged in order to create a barrier between automatically-run malicious programs and critical system resources. But there are a few things that I think are overzealously protected. The one that I find problematic is MS-signed drivers. Without their signature, a driver won't load at boot time unless you take the system into developer mode and approve the driver with each boot. This should be something the owner of the machine can sign once to approve, presumably with suitable barriers to prevent a mindless click-through by a regular user. Without this, there's a significant barrier to entry by freeware and open source hardware driver writers. |
#34
| |||
| |||
|
|
Sundial Services <i... (AT) sundialservices (DOT) com> wrote innews:47857d15 (AT) pnews (DOT) thedbcommunity.com: Vista is the first Windows release that really embraces this... that grabs on the notion that "even though this is 'your' computer, there are things that 'you' should not be able to do" and will not let go. I prefer to phrase this as "your day-to-day normal login". "You" can still do almost anything by logging in as administrator, but this is now strongly discouraged in order to create a barrier between automatically-run malicious programs and critical system resources. But there are a few things that I think are overzealously protected. The one that I find problematic is MS-signed drivers. Without their signature, a driver won't load at boot time unless you take the system into developer mode and approve the driver with each boot. This should be something the owner of the machine can sign once to approve, presumably with suitable barriers to prevent a mindless click-through by a regular user. Without this, there's a significant barrier to entry by freeware and open source hardware driver writers. |
#35
| |||
| |||
|
|
Sundial Services <i... (AT) sundialservices (DOT) com> wrote innews:47857d15 (AT) pnews (DOT) thedbcommunity.com: Vista is the first Windows release that really embraces this... that grabs on the notion that "even though this is 'your' computer, there are things that 'you' should not be able to do" and will not let go. I prefer to phrase this as "your day-to-day normal login". "You" can still do almost anything by logging in as administrator, but this is now strongly discouraged in order to create a barrier between automatically-run malicious programs and critical system resources. But there are a few things that I think are overzealously protected. The one that I find problematic is MS-signed drivers. Without their signature, a driver won't load at boot time unless you take the system into developer mode and approve the driver with each boot. This should be something the owner of the machine can sign once to approve, presumably with suitable barriers to prevent a mindless click-through by a regular user. Without this, there's a significant barrier to entry by freeware and open source hardware driver writers. |
#36
| |||
| |||
|
|
Sundial Services <i... (AT) sundialservices (DOT) com> wrote innews:47857d15 (AT) pnews (DOT) thedbcommunity.com: Vista is the first Windows release that really embraces this... that grabs on the notion that "even though this is 'your' computer, there are things that 'you' should not be able to do" and will not let go. I prefer to phrase this as "your day-to-day normal login". "You" can still do almost anything by logging in as administrator, but this is now strongly discouraged in order to create a barrier between automatically-run malicious programs and critical system resources. But there are a few things that I think are overzealously protected. The one that I find problematic is MS-signed drivers. Without their signature, a driver won't load at boot time unless you take the system into developer mode and approve the driver with each boot. This should be something the owner of the machine can sign once to approve, presumably with suitable barriers to prevent a mindless click-through by a regular user. Without this, there's a significant barrier to entry by freeware and open source hardware driver writers. |
![]() |
| Thread Tools | |
| Display Modes | |
| |