Recent DiscussionsMost RecentNewest TopicsMost LikesSolutionsTagged:TagRe: Azure certification for x509 authentication device giving error tjayparakash This issue is due to your test certificate subject being overly generic. IE: "mydevice". It's a shared X.509 enrollment testing space so someone else has already used the subject name you choose. When creating your test certificate, you can set the subject to the project GUID (displayed in the URL of the project) so it's always unique. If you're using the test cert creation scripts from GitHub, this would be the command. ./certGen.sh create_device_certificate_from_intermediate "<Insert GUID here>" Re: Make it easier to block domains in search resultsDone!Make it easier to block domains in search results So, recently (or maybe not so recently), almost all searches inevitably are showing results from *.it domains that "look" legit but are not. Instead they are hacked sites trying to do bad stuff. It would be really great if it were easier to block entire domains (or sites) from search results by including an option in Edge that appends the "-site:*.<domain>" to your search URL. I can do this, but i have to manually create my own "search engine" item and modifying the URL. It sure would be great if this were a feature that was more easily accessible. For example, here is how I have to achieve this. Create a new search engine named FOO. Then copy and modify the Bing or Google's search URL to block all .it domains from showing in my results. Bing: {bing:baseURL}search?q=%s+-site:*.it&{bing:cvid} Google {google:baseURL}search?q=%s+-site:*.it&{google:RLZ}{google:originalQueryForSuggestion}{google:assistedQueryStats}{google:searchFieldtrialParameter}{google:iOSSearchLanguage}{google:searchClient}{google:sourceId}{google:contextualSearchVersion}ie={inputEncoding}
Recent Blog ArticlesNewest TopicsMost LikesTagged:TagSimplify Wi-Fi IoT device onboarding with Zero Touch Provisioning Zero Touch Provisioning for the Azure Percept DK automates the setup of its Wi-Fi connection. Hardware Partner Center – SHA 1 signing deprecation notice Starting in November 2019, Hardware Partner Center will be moving to sign everything using the more secure SHA-2 algorithm exclusively. Upcoming Hardware Dev Center changes that enable support for Retpoline compiled binaries Effective May 1 2019: In order to support Retpoline compiled binaries on Hardware Dev Center, Microsoft will be treating Retpoline compiled binaries submitted to Hardware Dev Center differently th...The Hardware Dev Center has a new blog location! Welcome to the new Hardware Dev Center Blog. We will use this area to post information on Driver portal changes, signing requirements and feature enhancements. You'll also note we have a ne...Welcome to the new Windows Hardware Certification Blog space! Welcome to the new Windows Hardware Certification Blog! The HLK/HCK Blog now has a new location and name "Windows Hardware Certification Blog".
