-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support cross-platform compatibility by making xattr conditionally dependent #227
Comments
Here are some of the places I could find that will need to be modified if references to
|
Need to have an offline discussion about how to preserve existing |
Red Balloon Security, Inc. has previously encountered extended attributes in an embedded device filesystem. With widening adoption of SELinux kernel features, we should expect to see its usage more in the future. Improper (read: lack of) handling extended attributes lead to consistent crashes on boot in our previous efforts. In that case, the kernel was not verbose in the root cause of its failure, leading to extended debug times to root cause the issue. To save OFRAK users time and heartache, I recommend not removing this functionality, but, however possible, maintaining its support and warning users on platforms that do not support |
Resolved by #228 |
What is the use case for the feature?
OFRAK, and in particularFilesystemEntry
, currently supports working withxattr
attributes, which exist for Linux and macOS files. Rather thanxattr
, Windows uses Alternative Data Streams. As such, OFRAK has a platform-specific dependency forxattr
that prevents Windows users from using OFRAK. Since we currently only manipulatexattr
attributes for completeness (copying them to files OFRAK has modified), we can remove this dependency for now in order to enable OFRAK on Windows.Rather than removing support for
xattr
, we will make it a dependency conditional upon the platform running OFRAK. On platforms which do not supportxattr
(e.g., Windows), we will use a stubxattr
library that will warn users that extended attributes are not supported when using OFRAK on Windows.Does the feature contain any proprietary information about another company's intellectual property?
No.
How would you implement this feature?
Remove references toxattr
from theFilesystemEntry
class.Make
xattr
dependency conditional onplatform_system
. Any file importingxattr
will fall back to the stub library ifxattr
is not present.Are there any (reasonable) alternative approaches?
It makes sense to remove
xattr
for now in order to get Windows users up and running on OFRAK. We should have design discussions around whether/how we will supportxattr
/ADS
in the future.Are you interested in implementing it yourself?
Yes.
The text was updated successfully, but these errors were encountered: