[Bug 829952] New: Outdated information about cgconfig service in Resource Management Guide for Fedora 17
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=829952
Bug ID: 829952
QA Contact: docs-qa(a)lists.fedoraproject.org
Severity: unspecified
Version: devel
Priority: unspecified
CC: oglesbyzm(a)gmail.com
Assignee: mprpic(a)redhat.com
Summary: Outdated information about cgconfig service in
Resource Management Guide for Fedora 17
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: brezhnev(a)redhat.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: resource-management-guide
Product: Fedora Documentation
Description of problem:
The Resource Management Guide for Fedora 17 contains outdated information about
cgconfig service in section 2.1 "The cgconfig Service"
The guide states that the cgconfig service is not started by default in Fedora
17. It is not true. In addition, the guide contains phrase "When you start the
service with chkconfig" that is wrong for any release. For Fedora 17 is should
be "When you start the service with the <command>systemctl start</command>
command".
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years, 11 months
[Bug 928623] New: Need to explain HOW to try different desktop environments in live image
by Red Hat Bugzilla
Product: Fedora Documentation
https://bugzilla.redhat.com/show_bug.cgi?id=928623
Bug ID: 928623
Summary: Need to explain HOW to try different desktop
environments in live image
Product: Fedora Documentation
Version: devel
Component: readme-live-image
Severity: unspecified
Priority: unspecified
Assignee: docs(a)lists.fedoraproject.org
Reporter: mike(a)thosehallidays.org
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: nathan(a)afternoondust.co.uk, oglesbyzm(a)gmail.com
Description of problem:
Chapter 6 says "You can use the live image to try different desktop
environments such as GNOME, KDE, Xfce, or others" but does not explain HOW to
do that (or provide a contextual reference).
Version-Release number of selected component (if applicable):
Fedora 18
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
9 years, 2 months
[Bug 977045] New: Guide should document chronyd, not ntpd
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=977045
Bug ID: 977045
Summary: Guide should document chronyd, not ntpd
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: unspecified
Priority: unspecified
Assignee: jhradile(a)redhat.com
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
As of F16, Fedora uses `chrony` (chronyd.service) as the default time
daemon[1]. Chrony monitors and offsets local clock skew, making it superior
for machines without a constant connection to an ntp server. It also
effectively changes the system clock for even very large time changes, where
ntpd would require manual adjustment. The System administrator's guide should
be updated to reflect this.
The following sections, and references to them, should be updated:
2.2.3, “Configuring the Network Time Protocol”
D.1.14. /etc/sysconfig/ntpd
--Pete
[1]
https://git.fedorahosted.org/cgit/docs/release-notes.git/plain/en-US/Syst...
--
You are receiving this mail because:
You are the QA Contact for the bug.
9 years, 2 months
[Bug 904083] New: Storage Administration Guide is obsolete or not?
by Red Hat Bugzilla
Product: Fedora Documentation
https://bugzilla.redhat.com/show_bug.cgi?id=904083
Bug ID: 904083
Summary: Storage Administration Guide is obsolete or not?
Product: Fedora Documentation
Version: devel
Component: storage-administration-guide
Severity: medium
Priority: unspecified
Reporter: q2dg(a)yahoo.es
I've seen in http://docs.fedoraproject.org that last version of "Storage
Administration Guide" is for Fedora 14. It's more than two years ago!!
I don't know if this fact is due to this guide doesn't need any update or if
it's due to a lack of love from editors.
I want to notify this in Bugzilla to remember this situation, but I'm not sure
it is really a bug...
Could you tell me the reason of this abandonment?
Thanks!!
--
You are receiving this mail because:
You are the QA Contact for the bug.
9 years, 9 months
[Bug 891931] New: Chapter 3
by Red Hat Bugzilla
Product: Fedora Documentation
https://bugzilla.redhat.com/show_bug.cgi?id=891931
Bug ID: 891931
Summary: Chapter 3
Product: Fedora Documentation
Version: devel
Component: uefi-secure-boot-guide
Severity: unspecified
Priority: unspecified
Reporter: jwboyer(a)redhat.com
Description of problem:
I wrote this a couple of weeks ago:
http://jwboyer.livejournal.com/46149.html
It details building a custom kernel. Feel free to use anything you'd like from
there. However, it doesn't cover:
- generating your own key/certs
- signing shim or grub2 (trivially derived from the existing kernel example)
- third party module signing
Peter is working on a tool to make generating certs that UEFI likes easier for
people. I was waiting for that tool to be available before really covering
those aspects, as that is what we want users to use.
--
You are receiving this mail because:
You are the QA Contact for the bug.
9 years, 10 months
[Bug 892673] New: UEFI Secure Boot Guide: suggestions for edits
by Red Hat Bugzilla
Product: Fedora Documentation
https://bugzilla.redhat.com/show_bug.cgi?id=892673
Bug ID: 892673
Summary: UEFI Secure Boot Guide: suggestions for edits
Product: Fedora Documentation
Version: devel
Component: uefi-secure-boot-guide
Severity: unspecified
Priority: unspecified
Reporter: fweimer(a)redhat.com
Replace: "With the planned release of Windows 8, Microsoft has decided that all
hardware that is marked "Windows 8 client ready" should"
With: "Microsoft requires that client devices carrying the Windows 8 logo must"
Replace: "This means that Fedora as it stands booted on such hardware will
refuse to boot until the user disables secure boot in the firmware."
With: "The UEFI boot loader on Fedora installation media and on the installed
system are signed with the Microsoft key, to enable booting and installation on
such systems."
Remove the following paragraph, ending in "This plan has been approved by the
Fedora Engineering Steering Committee as of 23-Jul-2012."
After: "any operations from userland which cause userland-defined DMA"
Insert: "disable support for hibernate/suspend-to-disk, and other features
which would allow executing arbitrary code in kernel mode (even for the root
user)."
--
You are receiving this mail because:
You are the QA Contact for the bug.
9 years, 10 months
[Bug 782916] New: value of security measures; no metric, no scope description
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: value of security measures; no metric, no scope description
https://bugzilla.redhat.com/show_bug.cgi?id=782916
Summary: value of security measures; no metric, no scope
description
Product: Fedora Documentation
Version: devel
Platform: Unspecified
OS/Version: All
Status: NEW
Severity: unspecified
Priority: unspecified
Component: security-guide
AssignedTo: eric(a)christensenplace.us
ReportedBy: budden(a)nps.navy.mil
QAContact: docs-qa(a)lists.fedoraproject.org
CC: pkennedy(a)redhat.com, eric(a)christensenplace.us,
security-guide-list(a)redhat.com, oglesbyzm(a)gmail.com
Classification: Fedora
Story Points: ---
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Description of problem:
The juncture between computer security and network security is inadequate --
too many seams which leaves too many man-in-middle attack opportunities.
The most egregious omission in this (otherwise pretty good) document is
treatment of SCOPE. This probably belongs in the vicinity of 1.3.
Analysis first. Map each of the security solutions you have in the guide onto
the ISO Reference Model:
Layer 1/2 security measures (like WiFi security) protect frames. The scope of
the security is limited to a single segment. No security beyond the router and
no security within end systems.
Layer 3 security protected datagrams (VPNs do this, IPSec ....). The scope is
an enclave tunneled through an internetwork. The protection cannot extend
beyond the VPN boxes, so data is wholly unprotected within end systems (and LAN
if the VPN box is associated with the last router).
Layer 4/5 security includes SSL (aka TLS). You have a how-to for securing an
http server (good) but no admonitions regarding scope -- the security extends
from the TCP socket in one end system to the TCP socket at the other end of the
connection -- again no security inside the OS comes from SSL.
All of the above security measures protect infrastructure. But they do not
protect the data.
Layer 6/7 security measures protect the data. Here the scope _can be_ truly
end to end. S/MIME is a good example (so is ssh and XML sign/crypt) where the
data passes over the internet and through the OS in protected form. Only in a
fairly small space is the data unprotected. In Evolution, for example, only
the parts of the UA that deal with composing, reading, ... mail are places
where the authenticity and confidentiality of the data is possible. Most of
the rest of the UA (including all the filing system deals with data that has
been protected exactly the way it's been sent over the network. In the case of
Evolution (UAs differ in implementation) secured data is stored in the file
system exactly the way it was transmitted.
Recommendations:
1) include a mapping similar to above so users have an idea what the scope of
this or that security measure is.
2) emphasize those security measures that apply to applications (layer 6/7) as
Fedora distribution evolves and matures. (What got me here this morning is the
continuing frustration getting Evolution to properly play ball with DoD CAC
cards ... works, but doesn't 'just work').
Version-Release number of selected component (if applicable):
Security Guide 16.3 (doesn't have a date)
How reproducible:
The above analysis doesn't invent anything; it only organizes and sorts.
Anyone can reproduce it.
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
9 years, 10 months
[Bug 977063] New: New NetworkManager features should be documented
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=977063
Bug ID: 977063
Summary: New NetworkManager features should be documented
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: unspecified
Priority: unspecified
Assignee: jhradile(a)redhat.com
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
NetworkManager now offers hotspot functionality, allowing users to easily share
a non-wireless connection over a wireless interface.
As of F19, NetworkManager allows the creation and usage of both bridge and bond
virtual devices.
These features should be documented in the System Administrator's guide.
--Pete
--
You are receiving this mail because:
You are the QA Contact for the bug.
10 years, 1 month
[Bug 831619] New: Inaccuracy in Fedora 17 “Power Management Guide”
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=831619
Bug ID: 831619
QA Contact: docs-qa(a)lists.fedoraproject.org
Severity: low
Version: devel
Priority: unspecified
CC: ddomingo(a)redhat.com, oglesbyzm(a)gmail.com
Assignee: r.landmann(a)redhat.com
Summary: Inaccuracy in Fedora 17 “Power Management Guide”
Regression: ---
Story Points: ---
Classification: Fedora
OS: Linux
Reporter: vaskodd(a)yahoo.com
Type: Bug
Documentation: ---
Hardware: x86_64
Mount Type: ---
Status: NEW
Component: power-management-guide
Product: Fedora Documentation
Created attachment 591487
--> https://bugzilla.redhat.com/attachment.cgi?id=591487&action=edit
The problem description in .pdf format - easy to follow
Hi,
First I want to notice I am a Linux newbie and my English is not that good.
Now straight to the point! (The same description is available in the attached
pdf file and is more easy to follow)
I've noticed some inaccuracy in Fedora 17 “Power Management Guide” (Fedora
Documentation), particularly in section “2.5. Tuned and ktune” including
“2.5.1. The tuned.conf file” and “2.5.2 Tuned-adm”.
In section “2.5. Tuned and ktune” right bellow the “yum install tuned”
command it's written:
“Installing the tuned package also sets up a sample configuration file at
/etc/tuned.conf and activates the default profile.”
There is no such file in /etc. I found a /etc/tuned/active_profile file
containing the following: “/usr/lib/tuned/balanced/tuned.conf”. I'm not sure
this file (/etc/tuned.conf) is missing only on my system or it has a new
location by default for each profile - /usr/lib/tuned/profileX/tuned.conf.
Bellow in this section and in “2.5.1. The tuned.conf file” it is pointed again
that the default location for the tuned.conf file is /etc/tuned.conf.
In section “2.5.2 Tuned-adm” in the first paragraph it is written “Fedora 17
includes a number of predefined profiles for typical use cases...”. Just to be
precise it is good to be mentioned that these profiles are not installed by
default with “yum install tuned” command (tuned-2.0.1-1.fc17 package), but can
be found in tuned-profile-compat-2.0.1-1.fc17 package (I found it in Gnome
Package Manager).
Another thing in this section is in the last third of the page where it is
written:
“All the profiles are stored in separate subdirectories under
/etc/tune-profiles. So /etc/tune-profiles/desktop-powersave contains all the
necessary files and settings for that profile. Each of these directories
contains up to four files:”
There /etc/tune-profiles directory does not exist. Instead I found the profiles
stored in /run/lib/tuned.
Each directory for the corresponding profile typically contains only 2 files -
script.sh and tuned.conf. The presence of script.sh is not mentioned in the
directories contains description – it is mentioned ktune.sh insetad.
That's all. I hope this is helpful.
Best regards
Vasil Draganov
Fedora 17 3.4.0-1.fc17.x86_64
P.S. “Power Management Guide” is great. It's really useful. The moment i run
tuned service i noticed how quieter my laptop became (less heat – less fan
needed :) ). The first thing I noticed about new Fedora installation was that
the laptop was noisier in comparison to Win7 (I dual-boot with Win7). Tuned
just fixed that :)
Many thanks to the creators of Fedora Documentation!!!
--
You are receiving this mail because:
You are the QA Contact for the bug.
10 years, 5 months