docs-commits June 2014

docs-commits@lists.fedoraproject.org

5 participants
58 discussions

[system-administrators-guide] minor alignment issues
by Pete Travis 27 Jun '14

27 Jun '14

commit 70bb5b9c2a45e5679bac44d2332439ad420675cb Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Fri Jun 27 16:13:45 2014 -0600 minor alignment issues en-US/Managing_Users_and_Groups.xml | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) --- diff --git a/en-US/Managing_Users_and_Groups.xml b/en-US/Managing_Users_and_Groups.xml index 615c9df..de6fe53 100644 --- a/en-US/Managing_Users_and_Groups.xml +++ b/en-US/Managing_Users_and_Groups.xml @@ -912,10 +912,10 @@ total 28 drwx------. 4 juan juan 4096 Mar 3 18:23 . drwxr-xr-x. 5 root root 4096 Mar 3 18:23 .. -rw-r--r--. 1 juan juan 18 Jul 09 08:43 .bash_logout --rw-r--r--. 1 juan juan 176 Jul 09 08:43 .bash_profile --rw-r--r--. 1 juan juan 124 Jul 09 08:43 .bashrc -drwxr-xr-x. 4 juan juan 4096 Jul 09 08:43 .mozilla --rw-r--r--. 1 juan juan 658 Jul 09 08:43 .zshrc</screen> +-rw-r--r--. 1 juan juan 176 Jul 09 08:43 .bash_profile +-rw-r--r--. 1 juan juan 124 Jul 09 08:43 .bashrc +drwxr-xr-x. 4 juan juan 4096 Jul 09 08:43 .mozilla +-rw-r--r--. 1 juan juan 658 Jul 09 08:43 .zshrc</screen> </step> </procedure> <para>

1 0

[install-guide: 3/3] updating troubleshooting section re: incorrect memory to reflect grub2 behavior
by Pete Travis 27 Jun '14

27 Jun '14

commit cb6b56e4610505b2a06f45d5a77b331449e63db0 Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Fri Jun 27 16:01:58 2014 -0600 updating troubleshooting section re: incorrect memory to reflect grub2 behavior en-US/Trouble_After_Ram.xml | 54 +++++++++++++++++++++++++----------------- 1 files changed, 32 insertions(+), 22 deletions(-) --- diff --git a/en-US/Trouble_After_Ram.xml b/en-US/Trouble_After_Ram.xml index 13fafba..e058172 100644 --- a/en-US/Trouble_After_Ram.xml +++ b/en-US/Trouble_After_Ram.xml @@ -35,7 +35,7 @@ </step> <step> <para> - You are presented with a list of items in the configuration file for the boot label you have selected. Choose the line that starts with <computeroutput moreinfo="none">kernel</computeroutput> and type <command moreinfo="none">e</command> to edit this boot entry. + You are presented with a list of items in the configuration file for the boot label you have selected. Move to the line that starts with <computeroutput moreinfo="none">linux</computeroutput> or <computeroutput>linuxefi</computeroutput>. </para> </step> <step> @@ -46,17 +46,12 @@ <screen> <userinput moreinfo="none">mem=<replaceable>xx</replaceable>M</userinput></screen> <para> - where <replaceable>xx</replaceable> equals the amount of RAM in your system, then press <keycap moreinfo="none">Enter</keycap> to exit edit mode. + where <replaceable>xx</replaceable> equals the amount of RAM in your system in megabytes, then press <keycap moreinfo="none">F10</keycap> to boot the system. </para> </step> <step> <para> - Once the boot loader screen has returned, type <command moreinfo="none">b</command> to boot the system. - </para> - </step> - <step> - <para> - Run <command moreinfo="none">cat /proc/meminfo</command> again. If the known amount of RAM in your system is now displayed, add the following line to the <filename moreinfo="none">/etc/grub.d/10_linux</filename> file to make the change permanent: + Run <command moreinfo="none">cat /proc/meminfo</command> again. If the known amount of RAM in your system is now displayed, add the following to the <varname>GRUB_CMDLINE_LINUX</varname> line in <filename moreinfo="none">/etc/default/grub</filename>, inside the quotes, to make the change permanent: </para> <screen> @@ -68,23 +63,38 @@ <step> <para> To update the <filename>grub.cfg</filename> file so that the change will take effect, run the following command with root privileges. - </para> -<screen><command>grub2-mkconfig --output=/boot/grub2/grub.cfg</command></screen> + </para> + <screen> + # for BIOS systems + <command>grub2-mkconfig --output=/boot/grub2/grub.cfg</command> + </screen> + <screen> + # for UEFI systems + <command>grub2-mkconfig --output=/boot/efi/EFI/fedora/grub.cfg</command> + </screen> </step> </procedure> <para> - In <filename moreinfo="none">10_linux</filename>, the above example would look similar to the following: - </para> - -<screen> -default=0 -timeout=30 -splashimage=(hd0,1)/grub/splash.xpm.gz -menuentry 'Fedora Linux, with Linux 3.1.0-0.rc6.git0.3.fc16.x86_64' -set root=(hd0,1) -linux /vmlinuz-(2.6.32.130.el6.i686 ro root=UUID=04a07c13-e6bf-6d5a-b207-002689545705 mem=8192M -initrd /initrd-(2.6.32.130.el6.i686.img -</screen> + The resulting grub menu entry might look like this: + </para> + <screen> + menuentry 'Fedora (3.16.0-0.rc2.git2.1.fc21.x86_64) 21 (Rawhide)' { + load_video + set gfxpayload=keep + insmod gzio + insmod part_gpt + insmod ext2 + set root='hd1,gpt2' + if [ x$feature_platform_search_hint = xy ]; then + search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2 b34a57d9-03d7-415f-94f6-91689404d951 + else + search --no-floppy --fs-uuid --set=root b34a57d9-03d7-415f-94f6-91689404d951 + fi + linuxefi /vmlinuz-3.16.0-0.rc2.git2.1.fc21.x86_64 root=UUID=ece86abc-6419-4f29-84b6-1b810128f98d ro rootflags=subvol=root vconsole.font=latarcyrheb-sun16 vconsole.keymap=us LANG=en_US.UTF-8 mem=8192M + initrdefi /initramfs-3.16.0-0.rc2.git2.1.fc21.x86_64.img + } + + </screen> </section>

1 0

[install-guide: 2/3] Merge branch 'master' of ssh://git.fedorahosted.org/git/docs/install-guide
by Pete Travis 27 Jun '14

27 Jun '14

commit 2e82cb49dab2ff829918475ada641f2d69c376d3 Merge: 63a7a0b 92a2b3d Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Fri Jun 27 15:14:05 2014 -0600 Merge branch 'master' of ssh://git.fedorahosted.org/git/docs/install-guide Sure, dive right in... publican.cfg | 2 +- quickstart.cfg | 1 + 2 files changed, 2 insertions(+), 1 deletions(-) ---

1 0

[install-guide: 1/3] sometimes RAM is missing because of kernel quirks. Sometimes you just did it wrong.
by Pete Travis 27 Jun '14

27 Jun '14

commit 63a7a0bc2395931b0422705cfa0e7931e9bb4297 Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Fri Jun 27 15:13:24 2014 -0600 sometimes RAM is missing because of kernel quirks. Sometimes you just did it wrong. en-US/Trouble_After_Ram.xml | 8 +++++++- 1 files changed, 7 insertions(+), 1 deletions(-) --- diff --git a/en-US/Trouble_After_Ram.xml b/en-US/Trouble_After_Ram.xml index 7470f93..13fafba 100644 --- a/en-US/Trouble_After_Ram.xml +++ b/en-US/Trouble_After_Ram.xml @@ -11,7 +11,13 @@ <tertiary>RAM not recognized</tertiary> </indexterm> - + <note> + <title>Only showing 3.5GB?<title> + <para> + If you have 4GB or more memory installed, but Fedora only shows around 3.5GB or 3.7GB, you have probably installed a 32bit version of Fedora on a 64bit kernel. For modern systems, the 64bit version of Fedora is recommended. Refer to <xref linkend="sn-which-arch" /> for more details. + </para> + </title> + </note> <para> Sometimes, the kernel does not recognize all of your memory (RAM). The following procedure will allow you to confirm this and then adjust the kernel if necessary. </para>

1 0

[install-guide] (3 commits) ...updating troubleshooting section re: incorrect memory to reflect grub2 behavior
by Pete Travis 27 Jun '14

27 Jun '14

Summary of changes: 63a7a0b... sometimes RAM is missing because of kernel quirks. Sometime 2e82cb4... Merge branch 'master' of ssh://git.fedorahosted.org/git/doc cb6b56e... updating troubleshooting section re: incorrect memory to re

1 0

[amateur-radio-guide] Fixed will for BZ 1030257
by Eric Christensen 27 Jun '14

27 Jun '14

commit 76e4468ed146706033e37494895a6abd7cf7e300 Author: Eric Christensen <echriste(a)redhat.com> Date: Thu Nov 14 14:02:11 2013 -0500 Fixed will for BZ 1030257 en-US/Amateur_Radio_Guide.xml | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) --- diff --git a/en-US/Amateur_Radio_Guide.xml b/en-US/Amateur_Radio_Guide.xml index b6da7af..f59376a 100644 --- a/en-US/Amateur_Radio_Guide.xml +++ b/en-US/Amateur_Radio_Guide.xml @@ -12,8 +12,8 @@ more along the way. With new digital technologies being used everyday open sour edge in this ever-changing hobby. </para> <para> - Fedora has packaged dozens of software to make it easy for Fedora users to obtain and setup. Within seconds any user w -ill be able to have the tools they to enhance their amateur radio experience. + Fedora has packaged dozens of software to make it easy for Fedora users to obtain and setup. Within seconds any user +will be able to have the tools they to enhance their amateur radio experience. </para> </section>

1 0

[amateur-radio-guide] Fixed edge for BZ 1030257
by Eric Christensen 27 Jun '14

27 Jun '14

commit c594892679c76ab99464c5250878ee73bed20957 Author: Eric Christensen <echriste(a)redhat.com> Date: Thu Nov 14 11:52:39 2013 -0500 Fixed edge for BZ 1030257 en-US/Amateur_Radio_Guide.xml | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) --- diff --git a/en-US/Amateur_Radio_Guide.xml b/en-US/Amateur_Radio_Guide.xml index 45d30db..b6da7af 100644 --- a/en-US/Amateur_Radio_Guide.xml +++ b/en-US/Amateur_Radio_Guide.xml @@ -8,8 +8,8 @@ <title>Introduction</title> <para> Amateur radio and Linux go hand-in-hand. Both allow users to experiment to the extent of their knowledge and to learn -more along the way. With new digital technologies being used everyday open source software is the best way to stay cutting e -dge in this ever-changing hobby. +more along the way. With new digital technologies being used everyday open source software is the best way to stay cutting +edge in this ever-changing hobby. </para> <para> Fedora has packaged dozens of software to make it easy for Fedora users to obtain and setup. Within seconds any user w

1 0

[uefi-secure-boot-guide] master: Updated text for BZ 892673 (ee0ac10)
by Eric Christensen 27 Jun '14

27 Jun '14

Repository : http://git.fedorahosted.org/git/?p=docs/uefi-secure-boot-guide.git On branch : master >--------------------------------------------------------------- commit ee0ac10ce5b1feaf3f2726847ce74a0637bc7535 Author: Eric Christensen <echriste(a)redhat.com> Date: Fri Jun 27 09:56:57 2014 -0400 Updated text for BZ 892673 >--------------------------------------------------------------- en-US/Implementation_of_Secure_Boot.xml | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/en-US/Implementation_of_Secure_Boot.xml b/en-US/Implementation_of_Secure_Boot.xml index 1647d59..feb0439 100644 --- a/en-US/Implementation_of_Secure_Boot.xml +++ b/en-US/Implementation_of_Secure_Boot.xml @@ -1,4 +1,4 @@ -<?xml version='1.0' encoding='utf-8' ?> + <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ <!ENTITY % BOOK_ENTITIES SYSTEM "UEFI_Secure_Boot_Guide.ent"> %BOOK_ENTITIES; @@ -188,6 +188,7 @@ in Secure Boot mode, which will cause several things to be true: <member>it will validate the boot command line to only allow certain kernel settings</member> <member>it will check modules at load time for signatures and refuse to load them if they are unsigned or signed with a signature not found in the UEFI key store variables (see note)</member> <member>it will refuse any operations from userland which cause userland-defined DMA.</member> + <member>disable support for hibernate/suspend-to-disk, and other features which would allow executing arbitrary code in kernel mode (even for the root user).</member> </simplelist> </para> <para>

1 0

[securityguide] Added Crypto Policy feature
by Eric Christensen 27 Jun '14

27 Jun '14

commit e7b0dfcc21668d0aac28ecd9253c403fa978b41c Author: Eric H Christensen <sparks(a)redhat.com> Date: Fri Jun 27 09:31:41 2014 -0400 Added Crypto Policy feature en-US/Encryption.xml | 6 ++++++ 1 files changed, 6 insertions(+), 0 deletions(-) --- diff --git a/en-US/Encryption.xml b/en-US/Encryption.xml index 9b22d0c..ad937d6 100644 --- a/en-US/Encryption.xml +++ b/en-US/Encryption.xml @@ -64,6 +64,12 @@ AuthorizedKeysFile .ssh/authorized_keys</screen>The first line tells the SSH pro <para>Similarly to passwords and any other authentication mechanism, you should change your <application>SSH</application> keys regularly. When you do make sure you clean out any unused key from the authorized_key file.</para> </section> </section> + <section id="Security_Guide-Encryption-CryptoPolicy"> + <title>Crypto Policy</title> + <para>Beginning in Fedora 21, a system-wide crypto policy will be available for users to quickly setup the cryptographic options for their systems. Users that must meet certain cryptographic standards can make the policy change in <filename>/etc/crypto-policies/config</filename>, and run update-crypto-policies. At this point applications that are utilize the default set of ciphers in the GnuTLS and OpenSSL libraries will follow the policy requirements.</para> + <para>The available options are: (1) <literal>LEGACY</literal>, which ensures compatibility with legacy systems - 64-bit security, (2) <literal>DEFAULT</literal>, a reasonable default for today's standards - 80-bit security, and (3) <literal>FUTURE</literal>, a conservative level that is believed to withstand any near-term future attacks - 128-bit security. These levels affect SSL/TLS settings, including elliptic curve, signature hash functions, and ciphersuites and key sizes.</para> + <para>Additional information on this new feature can be found on the <ulink url="https://fedoraproject.org/wiki/Changes/CryptoPolicy">CryptoPolicy Changes wiki page</ulink>.</para> + </section> <xi:include href="DiskEncryptionUserGuide.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> <xi:include href="Using_GPG.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> </section>

1 0

[securityguide] Cleaned up a few lines
by Eric Christensen 27 Jun '14

27 Jun '14

commit 1c563092e88619ee7cbc857be52ec8c289ea21ed Author: Eric H Christensen <sparks(a)redhat.com> Date: Fri Jun 27 09:21:37 2014 -0400 Cleaned up a few lines en-US/Basic_Hardening.xml | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) --- diff --git a/en-US/Basic_Hardening.xml b/en-US/Basic_Hardening.xml index cbcc833..2562fa8 100644 --- a/en-US/Basic_Hardening.xml +++ b/en-US/Basic_Hardening.xml @@ -10,12 +10,12 @@ <section id="sect-Security_Guide-Basic_Hardening-General_Principles"> <title>General Principles</title> <para><simplelist> - <member>Encrypt all data transmitted over the network. Encrypting authentication information (such as passwords) is particularly important.</member> + <member>Encrypt all data transmitted over the network. Encrypting authentication information, such as passwords and cookies, is particularly important.</member> <member>Minimize the amount of software installed and running in order to minimize vulnerability.</member> <member>Use security-enhancing software and tools whenever available (e.g. SELinux and IPTables).</member> <member>Run each network service on a separate server whenever possible. This minimizes the risk that a compromise of one service could lead to a compromise of others.</member> <member>Maintain user accounts. Create a good password policy and enforce its use. Delete unused user accounts.</member> - <member>Review system and application logs on a routine basis. Send logs to a dedicated log server. This prevents intruders from easily avoiding detection by modifying the local logs.</member> + <member>Review system and application logs on a routine basis. Send logs to a dedicated, centralized log server. This prevents intruders from easily avoiding detection by modifying the local logs.</member> <member>Never log in directly as root, unless absolutely necessary. Administrators should use <command>sudo</command> to execute commands as root when required. The accounts capable of using sudo are specified in <filename>/etc/sudoers</filename>, which is edited with the visudo utility. By default, relevant logs are written to <filename>/var/log/secure</filename>.</member> </simplelist></para> </section>

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

docs-commits June 2014