It's worth noting, OSXFUSE is signed.

codesign --display -vvv
/Library/Filesystems/osxfusefs.fs/Support/osxfusefs.kext
Executable=/Library/Filesystems/osxfusefs.fs/Support/osxfusefs.kext/Contents/MacOS/osxfusefs
Identifier=com.github.osxfuse.filesystems.osxfusefs
[]
Authority=Developer ID Application: Benjamin Fleischer (3T5GSNBU6W)
[]


On Thu, Oct 23, 2014 at 9:52 PM, Brandon Allbery <[email protected]>
wrote:

> On Thu, 2014-10-23 at 20:37 -0500, Andrew Deason wrote:
> > On Thu, 23 Oct 2014 18:27:27 -0400
> > Stephen Joyce <[email protected]> wrote:
> >
> > > In any case, OpenAFS is not the only project which must decide how to
> > > move forward in this scenario. It might be instructive to see how
> > > macports, homebrew, etc. respond.
> >
> > Those won't involve kexts (if they even use Apple's signing framework at
> > all? Installing a package via macports doesn't go through the OS X
> > packaging system). I would imagine there are not many software projects
> > that provide kexts on OS X that are signed by a non-commercial entity,
> > but have commercial organizations related to them.
>
> In fact there are several MacPorts ports that install kexts, notably
> (and rather commonly) osxfuse. We're only just starting to look at
> possible solutions, but the fact that ports are usually built locally
> for both MacPorts and Homebrew introduces complications that OpenAFS
> won't face.
>
> --
> brandon s allbery kf8nh                           sine nomine associates
> [email protected]                              [email protected]
> unix openafs kerberos infrastructure xmonad        http://sinenomine.net
>



-- 
D

Reply via email to