Skip to content
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

Facilitate use of secured Linux environments for application providers #8

Open
kayatate opened this issue Apr 9, 2014 · 2 comments

Comments

@kayatate
Copy link

kayatate commented Apr 9, 2014

+LSB Specification Proposal
+
+Problem Statement:
+------------------
+
+It can be difficult for application providers to install their products on Linux
+systems that have security features turned on compared to those with the
+features turned off. Documentation is needed to guide application providers
+for how to build their applications and installers for systems with SELinux and

  • apparmor in use as well as for non-secured systems.
    +
    +(Proposed) Solution:
    +--------------------
    +
    +Create guideline documentation for applications for installing and running within
    +typical SELinux and apparmor environments compared to environments not using them.
    +
    +Solution Discussion Links:
    +--------------------------
    +
    +Solution Rationale:
    +------------------
    +
    +Many customers today want to use their preferred applications in a secure environment.
    +A number of commercial applications are programmed to use more system facilities
    +than are allowed to them in the secured environment. To complete the installation and
    +run successfully, they advise the customer to turn off the security feature. The
    +customer is then forced to make a decision between a more secure environment and
    +using the application. Clearer advice on how to set up applications in secured
    +environments would assist application providers in working within the environment.
    +
    +Distributions Support:
    +----------------------
    +
    +Ubuntu and OpenSUSE ship with apparmor turned on by default.
    +Fedora ships with SELinux turned on by default.
    +
    +Verification Test:
    +------------------
    +
    +Documentation, testing not required
    +
@kayatate
Copy link
Author

kayatate commented Apr 9, 2014

OK, yet another glitch. Flog me now. That'll teach me to not do a preview before submission.

@mwichmann
Copy link
Member

Yes, you got caught by this little note: "Comments are parsed with GitHub Flavored Markdown" (would not have happened if you submitted a file)

ajaissle added a commit to ajaissle/lsb that referenced this issue May 7, 2014
* Transformed the proposal from issue LinuxStandardBase#8 [1] to a proposal file
* Moved the Solution Rationale and Distributions Support sections to the Problem Statement, as these 'stages' are not yet reached (e.g. Ubuntu and openSUSE do not yet pledge to adhere to this specification, as there is no specification formed, yet)
* Added a State header with state "Problem Statement"
* Corrected the spelling of proper nouns (apparmor -> AppArmor, OpenSUSE -> openSUSE)

[1] LinuxStandardBase#8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants