[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, 5 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, 5 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, 5 months
[Bug 1282228] New: Problems Verifying Checksums on both Mac OS X and Ubuntu Linux
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1282228
Bug ID: 1282228
Summary: Problems Verifying Checksums on both Mac OS X and
Ubuntu Linux
Product: Fedora Documentation
Version: devel
Component: install-guide
Severity: medium
Assignee: pbokoc(a)redhat.com
Reporter: ajstewart426(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
shasum and sha256 sum do not like the format of your checksum files for some
reason.
Version-Release number of selected component (if applicable):
Fedora-Live-Workstation-x86_64-23-10.iso
Fedora-Workstation-23-x86_64-CHECKSUM
How reproducible:
Follow the instructions in section 3.3.2
Steps to Reproduce:
1. Download the Fedora image and appropriate checksum file. I was using the
versions listed above. I tried both saving the checksum webpage itself and
copying and pasting the text into a txt file.
2. In a terminal, navigate to the directory containing the files
3. For Linux:
$ sha256sum -c *CHECKSUM
For OS X:
$ shasum -a 256 -c *CHECKSUM
Actual results:
When running the above commands on both OS X and Ubuntu, I get something along
the lines of the following:
shasum: Fedora-Workstation-23-x86_64-CHECKSUM: no properly formatted SHA1
checksum lines found
For some reason it does not like the formatting of your files.
Expected results:
Something saying the checksum is valid I assume.
Additional info:
When I remove the -c option, it spits out the checksum itself. I was able to
manually verify the download that way. This solution should be sufficient for
most users. At least, it's better than having them run into the above error
message. A better solution would involve figuring out why it doesn't like the
formatting. I tried switching the line-ending characters from \n to \r\n since
that's such a common problem but it didn't help. If you want any more detailed
information on how to recreate this bug just let me know.
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years, 6 months
[Bug 1231578] New: No valid SHA1 checksums in checksum file
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1231578
Bug ID: 1231578
Summary: No valid SHA1 checksums in checksum file
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: misterfluff(a)me.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
Following the installation procedure for Fedora 22 the section in 3,3,2
(verifying checksums on Linux and OS X systems) fails.
Version-Release number of selected component (if applicable):
Fedora-Live-Scientific_KDE-x86_64-22-3.iso
How reproducible:
100%
Steps to Reproduce:
1. Download Fedora-Live-Scientific_KDE-x86_64-22-3.iso from spins page
2. Download Fedora-Spins-x86_64-22-CHECKSUM
3. shasum -a 256 -c *CHECKSUM
Actual results:
Fedora-Spins-x86_64-22-CHECKSUM: no properly formatted SHA1 checksum lines
found
Expected results:
Success, of course...:)
Additional info:
Additional checksum file Fedora-Workstation-22-x86_64-CHECKSUM file gave same
result.
Also performed "curl https://getfedora.org/static/fedora.gpg | gpg --import"
with no change in eventual result.
Is the process the same for checking a spin install versus the regular
workstation?
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years, 6 months
[Bug 1285374] New: F23 release notes don't mention that OpenSSH 7.0
disabled ssh-dss public keys by default
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1285374
Bug ID: 1285374
Summary: F23 release notes don't mention that OpenSSH 7.0
disabled ssh-dss public keys by default
Product: Fedora Documentation
Version: devel
Component: release-notes
Assignee: relnotes(a)fedoraproject.org
Reporter: mstahl(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Blocks: 151189 (fc-relnotes-traqr)
Fedora 22 to Fedora 23 upgrades OpenSSH from 6.9 to 7.1, but the release notes
only mention 7.1 and don't mention the default configuration changes that
happened in 7.0, such as the disabling of ssh-dss public keys that may prevent
a login to/from upgraded systems without explicit command line parameters.
https://docs.fedoraproject.org/en-US/Fedora/23/html/Release_Notes/sect-Re...
Actual results:
it only links to 7.1 release notes.
"3.4.2. OpenSSH 7.1
The OpenSSH project continues to improve the security of network communication
with the release of OpenSSH 7.1. See the upstream release notes for detailed
information about this release."
Expected results:
there should be at least a link to the OpenSSH 7.0 release notes too;
possibly explicitly mentioning the disabling of public keys.
http://www.openssh.com/txt/release-7.0
"Support for ssh-dss, ssh-dss-cert-* host and user keys is disabled by default
at run-time. To temporarily enable existing host keys, use the command line
option '-oHostKeyAlgorithms=ssh-dss' and to enable existing user keys, use
'-oPubkeyAcceptedKeyTypes=ssh-dss'."
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=151189
[Bug 151189] Fedora release notes tracker bug
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years, 6 months