[OpenAFS] any experiences with OpenAFS client on the upcoming MacOS 10.10 (yosemite) release?

Mattias Pantzare pantzer@ludd.ltu.se
Tue, 25 Nov 2014 22:05:24 +0100


--f46d0442808e19b6d30508b545c1
Content-Type: text/plain; charset=UTF-8

On Mon, Oct 20, 2014 at 9:14 PM, Mattias Pantzare <pantzer@ludd.ltu.se>
wrote:

>
> 10.10 requires all kernel extensions to be signed. They ship a list of
> hashes for old kernel extensions, that is why some versions of openafs will
> work on an upgraded system. But new openafs versions have to be signed.
>
> I have not been able to sign my kernel extension as I just discovered that
> I have to apply for rights to sign kernel extensions. A normal developer
> certificate is not enough. I don't know how long that process will take.
>

I have an update on the signing issue.

We have now received "The kext signing attribute" on our developer ID. We
can now sign kernel extensions.

There was no additional paperwork, we just received an e-email from Apple
that said that we where approved.

So there is no extra legal text to approve apart from the normal Apple
developer ID.

--f46d0442808e19b6d30508b545c1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Mon, Oct 20, 2014 at 9:14 PM, Mattias Pantzare <span dir=3D"ltr">&lt=
;<a href=3D"mailto:pantzer@ludd.ltu.se" target=3D"_blank">pantzer@ludd.ltu.=
se</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,20=
4);border-left-style:solid;padding-left:1ex"><div dir=3D"ltr"><div><br></di=
v><div>10.10 requires all kernel extensions to be signed. They ship a list =
of hashes for old kernel extensions, that is why some versions of openafs w=
ill work on an upgraded system. But new openafs versions have to be signed.=
</div><div><br></div><div>I have not been able to sign my kernel extension =
as I just discovered that I have to apply for rights to sign kernel extensi=
ons. A normal developer certificate is not enough. I don&#39;t know how lon=
g that process will take.</div></div></blockquote><div><br></div><div>I hav=
e an update on the signing issue.</div><div><br></div><div>We have now rece=
ived &quot;The kext signing attribute&quot; on our developer ID. We can now=
 sign kernel extensions.</div><div><br></div><div>There was no additional p=
aperwork, we just received an e-email from Apple that said that we where ap=
proved.</div><div><br></div><div>So there is no extra legal text to approve=
 apart from the normal Apple developer ID.</div></div></div></div>

--f46d0442808e19b6d30508b545c1--