Hello, What does this mean exactly? Will it be possible to install the OpenAFS-client after 31.12.2017? Is it just an academic problem? We set a computers BIOS to the future and, installed the OS (non-networked) and then installed the client (non-networked), and it worked fine.
MVH Anders -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Andreas Ladanyi Sent: den 5 december 2017 09:24 To: Lars Schimmer <[email protected]>; [email protected] Subject: Re: [OpenAFS] Windows 10 Pro and OpenAFS Client Hi, > > But take care, depending on the setup of your windows (secure > boot,etc.) OpenAFS will no more work on windows after 31.12.2017, as > the kernel module has no more a valid signature (in the def. of MS). if i understand the facts correctly i have two options: 1. I use the windows client package from auristor which is signed from microsoft ? 2. I use the UEFI boot option without Secure Boot and switch my windows 10 setup into the test signing mode for using the unsigned driver (after 31.12.2017) in the OpenAFS windows client package. Andreas _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
