[OpenAFS] Windows 10 Pro and OpenAFS Client
Sat, 9 Dec 2017 22:07:19 +0100
> On 2017-12-08 13:20, Anders Nordin wrote:
>> 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.
> It is a real issue.
> Because WIndows 10 compatibility is only signed with secure mode. Also
> the new Windows secure settings and anti-malware tools do only work in
> secure mode reliable.
> Also some companies do have the need to enable secure boot.
> And, nevertheless, no one knows what changes MS will do next time
> without announcing it.
> OpenAFS needs a substainable big contribution into the MS branch with
> getting a MS signature and be a valid kernel driver for the next years.
If i understand it correctly Auristor offers a signed AFS client for
windows ? So when using it after 31.12.2017 it will work ?
> To bad my gorup can´t do that (20 people only) and so we do migrate away
> from the AFS.