1. posterid:21621
  2. In-Process is out

Re: In-Process is out

David Goldfield
 

Cyrille wrote:

security advisories and "In-Process" do not target the same audience.

 

With respect I’m not sure that we can make such a general statement. I’m sure there are many In-Process readers who don’t care about the details of security advisories who would just skip over such material. However, I’d be willing to bet that many readers would have an interest in such things and who would review all of the details. In-Process likely is seen by experts as well as novices. If I’ve misunderstood your assertion by all means please feel free to correct me.

David Goldfield,

Blindness Assistive Technology Specialist

NVDA Certified Expert

 

Subscribe to the Tech-VI announcement list to receive news, events and information regarding the blindness assistive technology field.

Email: tech-vi+subscribe@groups.io

www.DavidGoldfield.org

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Cyrille via groups.io
Sent: Thursday, October 20, 2022 3:27 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] In-Process is out

 

Hello

Quentin, you have copied the content of a security advisory. However security advisories and "In-Process" do not target the same audience.
I do not know if In-Process are usually edited after having been released but this case would be an opportunity.

If possible, I would:
1. put the .reg file option before the manual registry edition option
2. put a big warning for people before editing the registry as we can find everywhere (e.g. here) on the internet when dealing with registry edition.
3. fix the steps with the correct wording (key instead of folder) and make the steps according to what is most commonly found ("Personalizatino" missing); people already having the "Personalization" key can just ignore the step for creating it.
or
3 bis. Remove the steps to edit the registry and just link the security advisory.

Cheers,

Cyrille




On Thu, Oct 20, 2022 at 04:48 AM, Quentin Christensen wrote:

Brian,

 

Thanks for the help for William on this one - I must admit, I just copied those steps from a previous recommendation we had put up with another security fix related to the lock screen.   I had a lot of content this week (and already a few items held over for the next post) so I didn't analyse those steps as closely as I might have another time.  I did note that the steps weren't as fully written as I would have with every keystroke, although being the registry, my original thought was that people should know what they are doing before going in and editing it - but then again maybe that is just more reason why the steps should be provided in full as well...

 

Quentin.

 

On Thu, Oct 20, 2022 at 12:01 PM Brian Vogel <britechguy@...> wrote:

By the way, I have yet to encounter any Windows 10 machine in its default state that will have a Personalization subkey under the Registry Key, Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows.

Count on having to follow my previously noted steps to create it and set its value to 1.
--

Brian - Virginia, USA  - Windows 10, 64-Bit, Version 22H2, Build 19045  

There are many people who can only make themselves feel better about themselves by making themselves feel better than others.

    ~ Commenter Looking_in on the Washington Post, 7/10/2014

 

 


 

--

Quentin Christensen
Training and Support Manager

 
Join nvda@nvda.groups.io to automatically receive all group messages.