On Tue, Oct 21, 2014 at 12:23 PM, Stephen Joyce
wrote:
> Jeffrey,
>
> I'd like to learn more about this. However since you sell a proprietary
> fork of OpenAFS, it's difficult to discount your possible incentive to
> spread FUD regarding OpenAFS.
>
> Therefore can you provide URIs with specific i
On Tue, Oct 21, 2014 at 4:23 PM, Stephen Joyce wrote:
> Jeffrey,
>
> I'd like to learn more about this. However since you sell a proprietary fork
> of OpenAFS, it's difficult to discount your possible incentive to spread FUD
> regarding OpenAFS.
>
> Therefore can you provide URIs with specific inf
Stephen,
I spoke up because Ben asked if my companies would be willing to sign
the OSX installers since we sign the Windows installers. I explained
why we sign the Windows installers but not others. I would much rather
not be signing the Windows installers but do so knowing that the OpenAFS
Foun
Jeffrey,
I'd like to learn more about this. However since you sell a proprietary
fork of OpenAFS, it's difficult to discount your possible incentive to
spread FUD regarding OpenAFS.
Therefore can you provide URIs with specific information to educate me (and
possibly others) regarding these c
I shouldn't try to provide that text, but this bit from
http://www.openafs.org/credits.html may help:
"Several institutions have funded internal development of AFS code which has
been contributed for inclusion in OpenAFS distributions.
• Apple Computer, Inc - MacOS 10.3 client/server p
The use Microsoft cross-signed certificates and Apple signing
certificates come with contractual obligations specifying the
circumstances under which signatures may be used. A signature is not
simply a method of proving that code has not been altered. A signature
is an indication to a customer th
