On 2/14/2017 7:37 AM, Kostas Liakakis wrote: > > Hi Jeffrey, > > Thanks for taking the time to answer. Please read below inline. > > > On 2017-02-14 03:53, Jeffrey Altman wrote: >> They are built with WiX 3.9 scripts. The >> installation packaging in the OpenAFS tree can no longer be used. > I see. So I'll switch to a later version as Ben suggested and see what > happens. Hopefully we won't have to reinvent the wheel.
The WiX 2.0 scripts cannot be used. Someone will have to write a new installer. >> As a reminder, the 1.7.3301 installers that AuriStor, Inc. distributes >> >> https://www.auristor.com/openafs/client-installer/ >> >> can be installed on Windows 10 and Windows Server 2016 because they are >> grand-fathered. If the same sources were built today they would not >> produce a working file system. > > This statement is a bit disturbing. But should not be surprising since I gave the community plenty of warning: https://lists.openafs.org/pipermail/openafs-info/2015-March/041324.html https://lists.openafs.org/pipermail/openafs-info/2015-April/041325.html https://lists.openafs.org/pipermail/openafs-info/2015-April/041328.html https://lists.openafs.org/pipermail/openafs-info/2015-April/041330.html https://lists.openafs.org/pipermail/openafs-info/2015-April/041332.html https://lists.openafs.org/pipermail/openafs-info/2015-June/041392.html https://lists.openafs.org/pipermail/openafs-info/2015-July/041449.html http://workshop.openafs.org/afsbpw15/talks/thursday/AFS-on-Windows-AFSBPW15.pdf http://workshop.openafs.org/afsbpw15/talks/friday/Securing_The_OS.pdf > Do you mean that given the state of things, even if Windows buildbots > start springing back to life and binaries for current OpenAFS versions > become available, no later version than the already built and signed > 1.7.3301 can be installed on Win10 and later? Will Win7 be ok at least? I've answered these questions in the e-mails and presentations listed above. > Do you consider the whole effort to revive the Windows port is in vain? In April 2015 I provided estimates of what I believe the on-going costs are for obtaining and maintaining a Microsoft signature for a file system. (Second link above.) Last week I attended IFS PlugFest 29. Microsoft is serious about improving the reliability of Windows and its resistance to root kits, ransomeware, and other forms of malware. Each year the requirements that driver vendors must satisfy become more demanding. * Mandatory to implement functionality * Mandatory to use build chains * Mandatory to submit testing reports for each OS variant on which the driver might be installed * Mandatory use of EV code signing certificates The challenge for the OpenAFS community is that the requirements cannot be satisfied simply by compiling the Windows client with the latest tool chains. The mandatory to implement functionality requires support from AFS (VL, FILE, RX, ...) that simply does not exist today. With the release of Windows 10 Creators Update the bar will be raised once again. > Or is there something the the Foundation is planning to do in order to > move forward again on the Windows platform? I am not a member of the Foundation Board. Their minutes can be reviewed at http://www.openafsfoundation.org/about/minutes/ Perhaps a board member could comment on their plans. Jeffrey Altman
<<attachment: jaltman.vcf>>
smime.p7s
Description: S/MIME Cryptographic Signature
