[Bug 1290654] New: ostreesetup --nogpgcheck should be --nogpg
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1290654
Bug ID: 1290654
Summary: ostreesetup --nogpgcheck should be --nogpg
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: puiterwijk(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
In the appendix with Kickstart syntax reference for Fedora 23, it says that
ostreesetup accepts --nogpgcheck to disable GPG checks, while this is in fact
--nogpg.
Version-Release number of selected component (if applicable):
Fedora 23
How reproducible:
Consistent
Steps to Reproduce:
1. Make a signed rpm-ostree repo
2. Use ostreesetup to install it and add --nogpgcheck
Actual results:
An error that --nogpgcheck is unknown.
Expected results:
A correctly pulled down tree.
Additional info:
Using --nogpg does what is expected.
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years, 4 months
[Bug 1283087] New: Typo in F23 section 5.2.1
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1283087
Bug ID: 1283087
Summary: Typo in F23 section 5.2.1
Product: Fedora Documentation
Version: devel
Component: release-notes
Assignee: relnotes(a)fedoraproject.org
Reporter: magfr(a)lysator.liu.se
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Description of problem:
Currently the text reads
5.2.1. Eclipse
... Mars (4.5) release. Som enew key features ...
That should be
5.2.1. Eclipse
... Mars (4.5) release. Some new key features ...
Version-Release number of selected component (if applicable):
23
How reproducible:
Always
Steps to Reproduce:
1. Look at
https://docs.fedoraproject.org/en-US/Fedora/23/html/Release_Notes/sect-Re...
Actual results:
Sees the type 'Som enew'
Expected results:
Sees the correctly spelled version 'Some new'
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years, 4 months
[Bug 1180524] New: confining users section unclear
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1180524
Bug ID: 1180524
Summary: confining users section unclear
Product: Fedora Documentation
Version: devel
Component: selinux-user-guide
Assignee: mprpic(a)redhat.com
Reporter: nmavrogi(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: mprpic(a)redhat.com, pkennedy(a)redhat.com,
zach(a)oglesby.co
The section 6 (confining users) in Fedora 21 documentation of SELinux is very
unclear.
1. What does confining mean actually? How are they confined? What capabilities
these user lose? These are crucial information, never discussed in the text.
2. In fedora with "seinfo -u" I see several selinux users. These, along with
the limitation each has, are never discussed.
3. "6.5. xguest: Kiosk Mode": I miss some technical info on the restrictions of
the xguest account. What that user can't do and what can it do. Without that
information the text could just say, trust us we've done everything for you
(nothing bad with it, except that in technical documentation you expect more).
4. I miss a "confining a server process/app" section. This is a very common
usage for selinux but no information is provided about that at all. Can I put
some server in a confined state, as the documentation discusses with the user?
Do we provide some preconfigured selinux users, roles, types for that purpose?
What about the sandbox tool we ship? That would be the information I'd expect
from such a section.
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years, 4 months
[Bug 1180142] New: issues in the introduction of selinux-user-guide
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1180142
Bug ID: 1180142
Summary: issues in the introduction of selinux-user-guide
Product: Fedora Documentation
Version: devel
Component: selinux-user-guide
Assignee: mprpic(a)redhat.com
Reporter: nmavrogi(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: mprpic(a)redhat.com, pkennedy(a)redhat.com,
zach(a)oglesby.co
[Originally sent to authors of the document]
I was trying to understand selinux using that guide, and had quite some issues
in the introduction. I send you my issues in the hope they will help to improve
the text.
-------------------------------------------------------------
Chapter 2. Introduction to SELinux:
I couldn't really understand what is selinux based on this section. It
says it is mandatory access control mechanism, and then it goes into
length explaining the 'Discretionary Access Control (DAC) system' used
typically in Linux. That's nice if you already know what selinux is,
because you can see the difference, but the opposite what I'd expect at
the moment since I have no idea what selinux is.
My suggestion would be to add the description I saw in
https://www.imperialviolet.org/2009/07/14/selinux.html
"SELinux is fundamentally about answering questions of the form “May x
do y to z?” and enforcing the result (x is subject, z is object) ...
The action (y) boils down to a class and a permission. Each class can
have up to 32 permissions (because they are stored as a bitmask in a
32-bit int). Examples of classes are FILE, TCP_SOCKET and X_EVENT. For
the FILE class, some examples of permissions are READ, WRITE, LOCK etc."
At least for me that was all the information that I needed to understand
what I can do with SELinux. A complete pictures may require to go into a
bit more length with explaining what can be a subject, object and
actions. Then mentioning about MAC and explaining it in addition to DAC
will be more natural IMO.
---------------------------------------------------------------------
2.1. Benefits of running SELinux
This is section vaguely defines domain. I reached "3.1. Domain
Transitions" and didn't know what a domain was.
Maybe add a definition of domain in 3.1 or earlier in the introduction.
---------------------------------------------------------------------
Chapter 3. SELinux Contexts
level:
It explains that in Fedora there is a single sensitivity and multiple
categories. I miss what are these categories intended to be used to? An
example with two different categories would be helpful.
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years, 4 months