[Bug 769438] New: [PATCH] Fix syntax of code examples within rpm-guide-programming-python.xml
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: [PATCH] Fix syntax of code examples within rpm-guide-programming-python.xml
https://bugzilla.redhat.com/show_bug.cgi?id=769438
Summary: [PATCH] Fix syntax of code examples within
rpm-guide-programming-python.xml
Product: Fedora Documentation
Version: devel
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: rpm-guide
AssignedTo: bcotton+fedora(a)gmail.com
ReportedBy: dmalcolm(a)redhat.com
QAContact: docs-qa(a)lists.fedoraproject.org
CC: oglesbyzm(a)gmail.com, pkovar(a)redhat.com
Classification: Fedora
Story Points: ---
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Created attachment 548940
--> https://bugzilla.redhat.com/attachment.cgi?id=548940
Patch to Rpm Guide to fix rpm-guide-programming-python.xml
Unfortunately the examples of Python code within the RPM guide have been
thoroughly broken since the initial conversion to DocBook, due to the way
Python treats leading whitespace as significant.
I'm attaching a patch which overhauls this page, so that the code examples are
syntactically valid. See the notes in the patch
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
6 years, 4 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 808103] New: Would be great to have a direct link to bugzilla repot
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: Would be great to have a direct link to bugzilla repot
https://bugzilla.redhat.com/show_bug.cgi?id=808103
Summary: Would be great to have a direct link to bugzilla repot
Product: Fedora Documentation
Version: devel
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: low
Priority: unspecified
Component: documentation-guide
AssignedTo: eric(a)christensenplace.us
ReportedBy: kev.raymond(a)gmail.com
QAContact: docs-qa(a)lists.fedoraproject.org
CC: stickster(a)gmail.com, kwade(a)redhat.com,
oglesbyzm(a)gmail.com, jhradile(a)redhat.com,
pkovar(a)redhat.com
Classification: Fedora
Story Points: ---
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
As per a mailing list request[1], it should be better to have a direct link in
all guides to the corresponding bugzilla component, in order to give feedback.
Currently it's only plain text.
On the release notes is should even be a mailto: link.
[1] http://lists.fedoraproject.org/pipermail/websites/2012-March/019372.html
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
11 years, 9 months
[Bug 789493] New: Musician's Guide 1.1.1, par. 2, change "infinite"->"continuously variable"
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: Musician's Guide 1.1.1, par. 2, change "infinite"->"continuously variable"
https://bugzilla.redhat.com/show_bug.cgi?id=789493
Summary: Musician's Guide 1.1.1, par. 2, change
"infinite"->"continuously variable"
Product: Fedora Documentation
Version: devel
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: low
Priority: unspecified
Component: musicians-guide
AssignedTo: crantila(a)acanac.net
ReportedBy: thomas(a)hedden.org
QAContact: docs-qa(a)lists.fedoraproject.org
CC: oglesbyzm(a)gmail.com
Classification: Fedora
Story Points: ---
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Description of problem:
Poor wording.
Version-Release number of selected component (if applicable):
N/A
How reproducible:
Always
Steps to Reproduce:
1. Open Fedora Musician's Guide
2. Go to chapter 1.1.1. Audio Interfaces, 2nd paragraph
3. Find sentence beginning "Computers cannot process ..."
Actual results:
The sentence uses the phrase "infinite information"
Expected results:
The sentence should use the phrase "continuous information" or "continuously
variable information"
Additional info:
The use of the word "infinite" in the meaning "continuously variable" is what I
would expect in the instructions for a washing machine, not in a Fedora manual.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
11 years, 9 months
[Bug 808246] New: Link to SRTM files is broken
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: Link to SRTM files is broken
https://bugzilla.redhat.com/show_bug.cgi?id=808246
Summary: Link to SRTM files is broken
Product: Fedora Documentation
Version: devel
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: amateur-radio-guide
AssignedTo: wb8rcr(a)arrl.net
ReportedBy: eric(a)christensenplace.us
QAContact: docs-qa(a)lists.fedoraproject.org
CC: eric(a)christensenplace.us, oglesbyzm(a)gmail.com
Classification: Fedora
Story Points: ---
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Description of problem: The link to the NASA repository of SRTM files is
broken.
Version-Release number of selected component (if applicable): 16
Additional info: I think I found a place to download them from the USGS but it
is a painful process that requires an account and I have yet to successfully
download a file.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
12 years