1 [[!meta title="Binary Packages Available from Third Parties"]]
2 # Binary Packages Available from Third Parties #
4 While OpenAFS.org packages up binary releases of OpenAFS, third parties may also release their own binary packages of OpenAFS. This page is an attempt to collect, in one place, various third party binary packages. Keep in mind that the packages would be supported by the third party and not openafs.org. However, you can still ask the OpenAFS community with questions about how and why things do or do not work.
6 ### Fedora and CentOS7/RHEL7 ###
8 #### JSBillings Fedora Copr ####
10 Repackaged using sources from http://www.openafs.org/. Does not use the spec file included there, but a slimmer package that uses non-transarc paths.
12 Does not support Linux Kernel 4.5 or newer, as OpenAFS is not yet compatible with Linux Kernel 4.5 or newer.
14 * [OpenAFS](https://copr.fedorainfracloud.org/coprs/jsbillings/openafs/)
15 * [OpenAFS-KMod](https://copr.fedorainfracloud.org/coprs/jsbillings/openafs-kmod/)
19 Sine Nomine digitally signed 1.6.16 Installers for [10.9](http://download.sinenomine.net/openafs/bins/1.6.16/macos-10.9/), [10.10](http://download.sinenomine.net/openafs/bins/1.6.16/macos-10.10/), and [10.11](http://download.sinenomine.net/openafs/bins/1.6.16/macos-10.11/)
21 #### Release Notes for Sine Nomine Packages ####
23 The disk images provided here provide support for recent Mac OS X
24 versions, including provisional support for System Integrity Protection
25 (aka "rootless") on 10.11.
27 Included is an experimental change to the client to support the
28 additional security verification of 10.11, where programs using the
29 native "Cocoa" API will ask various root daemons (taskgated,
30 DesktopServicesHelper, syspolicyd, possibly others depending on
31 configuration) to verify files for them; these daemons do not have
32 access to the user's token, and would normally fail verification as a
33 result. This change means that root can read any AFS-resident file that
34 is locally cached without a token. While this is technically a security
35 violation, it should be noted that all versions of IBM AFS and OpenAFS
36 already allow root (or, with lax cache permissions, potentially any
37 user) to read any locally cached file by accessing the cache directory
38 directly. Thus, the risk this introduces is no greater than the risks
39 already carried by sites using AFS.
41 Programs using the BSD APIs do not use the root daemons and work as
42 expected, unless you run a signed binary from OpenAFS, in which case
43 taskgated will attempt to verify the binary's signature and internal
44 requirements and entitlements; this again requires the above root
47 On 10.11, client commands are installed to /opt/openafs/bin instead of
48 /usr/bin. The system path database is modified to add this directory to
49 the $PATH of new sessions. Running sessions after initial installation
50 of the client will need to add /opt/openafs/bin to their $PATH
53 The change to enable root to perform security checks appears to have
54 introduced an occasional issue where tab completion in a directory will
55 not work unless the directory's contents has previously been listed
56 (e.g. with "ls"). While the security checks are only performed on
57 10.11, the root access code path is active in all of the clients, so
58 this will also occur on 10.9 and 10.10. We are still working on
59 diagnosing the cause, and will provide an updated release when it is
60 available. In testing, this issue has proven uncommon and transient for
63 NOTE: The preference pane remains deprecated in this version of the
64 client. Sine Nomine is working on addressing problems in the preference
65 pane for future versions.