[OpenAFS] OpenAFS Installation on Windows
Odoom, Jason
jo75@njit.edu
Fri, 2 Sep 2016 12:58:42 -0400
--001a1148755a8d514b053b894062
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Jeffrey,
I am running Windows 10 Education on x64 architecture. The version of the
AFS client I am installing is 1.7 provided by YFS.
*yfs-openafs-en_US-AMD64-1_7_3301.msi
*I've installed it along with one dll file - afscreds_1033.dll. But thanks
to the information you provided I was able to get it running.
Thanks for your help,
On Fri, Sep 2, 2016 at 10:40 AM, Jeffrey Altman <jaltman@auristor.com>
wrote:
> On 9/1/2016 4:07 PM, Odoom, Jason wrote:
> >
> > =E2=80=8BHello,
> >
> > I've been having difficulty installing OpenAFS on Windows 10. I receiv=
e
> > the error "Installation of network provider failed" when installing the
> > OpenAFS client msi package. I saw from a previous mailing list[1] that =
I
> > have to run the msi with administrative privileges. However, that does
> > not fix the issue. How do I fix this issue?
> >
> > [1]:https://lists.openafs.org/pipermail/openafs-info/2011-
> January/035370.html
> > <https://lists.openafs.org/pipermail/openafs-info/2011-
> January/035370.html>
> >
> > Any assistance would be appreciated,
> > =E2=80=8B
> >
> > --
> > -Jason Odoom
> > ARCS Student Assistant
>
> Jason,
>
> When requesting assistance it is important that you be specific about
> the variables in your environment:
>
> * what version of Windows are you using? You say Windows 10
> but Windows 10 is a moniker that describes every version of
> Windows shipped since 29 July 2015 as well as many different
> variants?
>
> home, professional, educational, enterprise, tablet, mobile, IoT, ...
>
> x64, x86, arm, ...
>
> Within each variant there are major milestone releases with
> different features and requirements.
>
> * what version of OpenAFS are you installing and whose packaging?
>
>
> If you are not already aware, the OpenAFS client for Windows 1.7.x is
> implemented with several "system" component extensions
>
> * two file system drivers
>
> * two network provider dlls. one for authentication and one for
> interfacing with the file system drivers to support drive letter
> mapping, path evaluation, etc.
>
> * a system service
>
> * a suite of file explorer object classes
>
> All of the OpenAFS MSIs and the binaries included within them were
> signed by Your File System, Inc. with a SHA1 hash. Microsoft has warned
> for years that SHA1 code signing would be deprecated. Due to additional
> weaknesses in SHA1 hashes Microsoft and Mozilla decided to accelerate
> the deprecation process.
>
> https://blogs.windows.com/msedgedev/2015/11/04/sha-1-deprecation-update/
>
> While SHA1 signed MSIs are still accepted, SHA1 signed system binaries,
> depending upon the Windows variant and domain policy, are not. An
> attempt to install a system binary on a system that requires SHA2
> signatures will fail.
>
> Also, it is important to note that as of Windows 10 version 1607 the new
> driver signing requirements for file system drivers are being enforced.
>
> https://blogs.msdn.microsoft.com/windows_hardware_
> certification/2016/07/26/driver-signing-changes-in-
> windows-10-version-1607/
>
> However, I doubt that this is the cause of the problems you are
> experiencing. Last night I clean installed the 1607 professional 1607
> build on both x86 and x64. The AuriStor distributed OpenAFS for Windows
> installers (1.7.3301) that utilize the AuriStor (formerly Your File
> System) packaging installed successfully on both systems and the client
> operated as expected. The drivers included in this installer are
> accepted under the grandfather exception for cross-signing certificates
> issued before 29 June 2015.
>
> Jeffrey Altman
>
>
--=20
-Jason Odoom
ARCS Student Assistant
--001a1148755a8d514b053b894062
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:monospac=
e,monospace">Jeffrey,</div><div class=3D"gmail_default" style=3D"font-famil=
y:monospace,monospace"><br></div><div class=3D"gmail_default" style=3D"font=
-family:monospace,monospace">=C2=A0I am running Windows 10 Education on x64=
architecture. The version of the AFS client I am installing is 1.7 provide=
d by YFS. <i>yfs-openafs-en_US-AMD64-1_7_3301.msi </i>I've installed it=
along with one dll file -=C2=A0afscreds_1033.dll. But thanks to the inform=
ation you provided I was able to get it running.=C2=A0</div><div class=3D"g=
mail_default" style=3D"font-family:monospace,monospace"><br></div><div clas=
s=3D"gmail_default" style=3D"font-family:monospace,monospace">Thanks for yo=
ur help,=C2=A0</div></div><div class=3D"gmail_extra"><br><div class=3D"gmai=
l_quote">On Fri, Sep 2, 2016 at 10:40 AM, Jeffrey Altman <span dir=3D"ltr">=
<<a href=3D"mailto:jaltman@auristor.com" target=3D"_blank">jaltman@auris=
tor.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=
=3D"HOEnZb"><div class=3D"h5">On 9/1/2016 4:07 PM, Odoom, Jason wrote:<br>
><br>
> =E2=80=8BHello,<br>
><br>
>=C2=A0 I've been having difficulty installing OpenAFS on Windows 10=
. I receive<br>
> the error "Installation of network provider failed" when ins=
talling the<br>
> OpenAFS client msi package. I saw from a previous mailing list[1] that=
I<br>
> have to run the msi with administrative privileges. However, that does=
<br>
> not fix the issue. How do I fix this issue?<br>
><br>
> [1]:<a href=3D"https://lists.openafs.org/pipermail/openafs-info/2011-J=
anuary/035370.html" rel=3D"noreferrer" target=3D"_blank">https://lists.open=
afs.org/<wbr>pipermail/openafs-info/2011-<wbr>January/035370.html</a><br>
> <<a href=3D"https://lists.openafs.org/pipermail/openafs-info/2011-J=
anuary/035370.html" rel=3D"noreferrer" target=3D"_blank">https://lists.open=
afs.org/<wbr>pipermail/openafs-info/2011-<wbr>January/035370.html</a>><b=
r>
><br>
> Any assistance would be appreciated,<br>
> =E2=80=8B<br>
><br>
> --<br>
> -Jason Odoom<br>
> ARCS Student Assistant<br>
<br>
</div></div>Jason,<br>
<br>
When requesting assistance it is important that you be specific about<br>
the variables in your environment:<br>
<br>
=C2=A0* what version of Windows are you using?=C2=A0 =C2=A0You say Windows =
10<br>
=C2=A0 =C2=A0but Windows 10 is a moniker that describes every version of<br=
>
=C2=A0 =C2=A0Windows shipped since 29 July 2015 as well as many different<b=
r>
=C2=A0 =C2=A0variants?<br>
<br>
=C2=A0 =C2=A0home, professional, educational, enterprise, tablet, mobile, I=
oT, ...<br>
<br>
=C2=A0 =C2=A0x64, x86, arm, ...<br>
<br>
=C2=A0 =C2=A0Within each variant there are major milestone releases with<br=
>
=C2=A0 =C2=A0different features and requirements.<br>
<br>
* what version of OpenAFS are you installing and whose packaging?<br>
<br>
<br>
If you are not already aware, the OpenAFS client for Windows 1.7.x is<br>
implemented with several "system" component extensions<br>
<br>
=C2=A0* two file system drivers<br>
<br>
=C2=A0* two network provider dlls.=C2=A0 one for authentication and one for=
<br>
=C2=A0 =C2=A0interfacing with the file system drivers to support drive lett=
er<br>
=C2=A0 =C2=A0mapping, path evaluation, etc.<br>
<br>
=C2=A0* a system service<br>
<br>
=C2=A0* a suite of file explorer object classes<br>
<br>
All of the OpenAFS MSIs and the binaries included within them were<br>
signed by Your File System, Inc. with a SHA1 hash.=C2=A0 Microsoft has warn=
ed<br>
for years that SHA1 code signing would be deprecated.=C2=A0 Due to addition=
al<br>
weaknesses in SHA1 hashes Microsoft and Mozilla decided to accelerate<br>
the deprecation process.<br>
<br>
=C2=A0<a href=3D"https://blogs.windows.com/msedgedev/2015/11/04/sha-1-depre=
cation-update/" rel=3D"noreferrer" target=3D"_blank">https://blogs.windows.=
com/<wbr>msedgedev/2015/11/04/sha-1-<wbr>deprecation-update/</a><br>
<br>
While SHA1 signed MSIs are still accepted, SHA1 signed system binaries,<br>
depending upon the Windows variant and domain policy, are not.=C2=A0 =C2=A0=
An<br>
attempt to install a system binary on a system that requires SHA2<br>
signatures will fail.<br>
<br>
Also, it is important to note that as of Windows 10 version 1607 the new<br=
>
driver signing requirements for file system drivers are being enforced.<br>
<br>
<a href=3D"https://blogs.msdn.microsoft.com/windows_hardware_certification/=
2016/07/26/driver-signing-changes-in-windows-10-version-1607/" rel=3D"noref=
errer" target=3D"_blank">https://blogs.msdn.microsoft.<wbr>com/windows_hard=
ware_<wbr>certification/2016/07/26/<wbr>driver-signing-changes-in-<wbr>wind=
ows-10-version-1607/</a><br>
<br>
However, I doubt that this is the cause of the problems you are<br>
experiencing.=C2=A0 =C2=A0 Last night I clean installed the 1607 profession=
al 1607<br>
build on both x86 and x64.=C2=A0 The AuriStor distributed OpenAFS for Windo=
ws<br>
installers (1.7.3301) that utilize the AuriStor (formerly Your File<br>
System) packaging installed successfully on both systems and the client<br>
operated as expected.=C2=A0 =C2=A0The drivers included in this installer ar=
e<br>
accepted under the grandfather exception for cross-signing certificates<br>
issued before 29 June 2015.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Jeffrey Altman<br>
<br>
</font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b=
r><div class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div di=
r=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div style=3D"font-si=
ze:small"><font face=3D"monospace, monospace">-Jason Odoom=C2=A0</font></di=
v><div style=3D"font-size:small"><span style=3D"font-size:12.8000001907349p=
x"><font face=3D"monospace, monospace">ARCS Student Assistant</font></span>=
</div></div></div></div></div></div></div>
</div>
--001a1148755a8d514b053b894062--