This is the mail archive of the
mailing list for the Cygwin project.
Re: FUSE for Cygwin
- From: Bill Zissimopoulos <billziss at navimatics dot com>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Wed, 22 Jun 2016 22:15:19 +0000
- Subject: Re: FUSE for Cygwin
- Authentication-results: sourceware.org; auth=none
- Authentication-results: spf=none (sender IP is ) smtp dot mailfrom=billziss at navimatics dot com;
- References: <D389ABB9 dot 931F%billziss at navimatics dot com> <57667FEF dot 5070801 at gmx dot de> <D38C1E3D dot 9385%billziss at navimatics dot com> <57670140 dot 7050001 at gmx dot de> <D3903007 dot 94EF%billziss at navimatics dot com> <98d5ffd0-6b20-8492-3053-fd21e010c237 at secure-endpoints dot com>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
On 6/22/16, 1:39 PM, "Jeffrey Altman" <firstname.lastname@example.org on behalf
of email@example.com> wrote:
>On 6/22/2016 3:43 PM, Bill Zissimopoulos wrote:
>> The bigger question is whether the Cygwin community would want a package
>> like this. The obvious answer might be yes (I hope), but there is a
>> caveat. WinFsp includes a kernel-mode driver that needs to be built
>> Microsoft tools and signed using an EV certificate. In fact it looks
>> those requirements will only get harder as time passes -- soon we may
>> a sysdev account just to sign drivers. This means that the familiar
>> of getting the source and compiling everything using Cygwin tools cannot
>> work here.
>I believe that as of Windows 10 Anniversary Edition and Server 2016
>Secure Boot becomes mandatory for new installations and with Secure Boot
>comes the requirement that all device drivers (including file system
>drivers) be signed by Microsoft.
I agree. That is my understanding as well.