Errors in man pages, here: random.4.po: Wording

Errors in man pages, here: random.4.po: Wording

[Helge Kreutzmann]

Dear manpages maintainers.
the manpage-l10n project maintains a large number of translations of
man pages both from a large variety of sources (including manpages) as
well for a large variety of target languages.

During their work translators notice different possible issues in the
original (english) man pages. Sometiems this is a straightforward
typo, sometimes a hard to read sentence, sometimes this is a convention
not held up and sometimes we simply do not understand the original.

We use several distributions as sources and update regularly (at
least every 2 month). This means we are fairly recent (some
distributions like archlinux also update frequently) but might miss
the latest upstream version once a while, so the error might be
already fixed. We apologize and ask you to close the issue immediately
if this should be the case, but given the huge volume of projects and
the very limited number of volunteers we are not able to double check
each and every issue.

Secondly we translators see the manpages in the neutral po format,
i.e. converted and harmonized, but not the original source (be it man,
groff, xml or other). So we cannot provide a true patch (where
possible), but only an approximation which you need to translate into
your source format.

Finally the issues I'm reporting have accumulated over time and are
not always discovered by me, so sometimes my description of the
problem my be a bit limited - do not hesitate to ask so we can clarify
them.

I'm now reporting the errors for your project. As requested, each
issue is sent in an unique mail for easier tracking on your side. If
future reports should use another channel, please let me know.

**

The first sentence is very hard to read and should be reworded, maybe
into two sentences.

"If a seed file is saved across reboots as recommended below (all major Linux "
"distributions have done this since 2000 at least), the output is "
"cryptographically secure against attackers without local root access as soon "
"as it is reloaded in the boot sequence, and perfectly adequate for network "
"encryption session keys.  Since reads from I</dev/random> may block, users "
"will usually want to open it in nonblocking mode (or perform a read with "
"timeout), and provide some sort of user notification if the desired entropy "
"is not immediately available."

-- 
      Dr. Helge Kreutzmann                     debian@helgefjell.de
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software libre: http://www.ffii.de/

Re: Errors in man pages, here: random.4.po: Wording

[Michael Kerrisk (man-pages)]

On 4/19/20 8:48 AM, Helge Kreutzmann wrote:
> Dear manpages maintainers.
> the manpage-l10n project maintains a large number of translations of
> man pages both from a large variety of sources (including manpages) as
> well for a large variety of target languages.
> 
> During their work translators notice different possible issues in the
> original (english) man pages. Sometiems this is a straightforward
> typo, sometimes a hard to read sentence, sometimes this is a convention
> not held up and sometimes we simply do not understand the original.
> 
> We use several distributions as sources and update regularly (at
> least every 2 month). This means we are fairly recent (some
> distributions like archlinux also update frequently) but might miss
> the latest upstream version once a while, so the error might be
> already fixed. We apologize and ask you to close the issue immediately
> if this should be the case, but given the huge volume of projects and
> the very limited number of volunteers we are not able to double check
> each and every issue.
> 
> Secondly we translators see the manpages in the neutral po format,
> i.e. converted and harmonized, but not the original source (be it man,
> groff, xml or other). So we cannot provide a true patch (where
> possible), but only an approximation which you need to translate into
> your source format.
> 
> Finally the issues I'm reporting have accumulated over time and are
> not always discovered by me, so sometimes my description of the
> problem my be a bit limited - do not hesitate to ask so we can clarify
> them.
> 
> I'm now reporting the errors for your project. As requested, each
> issue is sent in an unique mail for easier tracking on your side. If
> future reports should use another channel, please let me know.
> 
> **
> 
> The first sentence is very hard to read and should be reworded, maybe
> into two sentences.
> 
> "If a seed file is saved across reboots as recommended below (all major Linux "
> "distributions have done this since 2000 at least), the output is "
> "cryptographically secure against attackers without local root access as soon "
> "as it is reloaded in the boot sequence, and perfectly adequate for network "
> "encryption session keys.  Since reads from I</dev/random> may block, users "
> "will usually want to open it in nonblocking mode (or perform a read with "
> "timeout), and provide some sort of user notification if the desired entropy "
> "is not immediately available."

Changed as per patch below.

Thanks,

Michael

diff --git a/man4/random.4 b/man4/random.4
index 5f0d52472..95fee6ed0 100644
--- a/man4/random.4
+++ b/man4/random.4
@@ -136,11 +136,13 @@ these applications,
 must be used instead,
 because it will block until the entropy pool is initialized.
 .PP
-If a seed file is saved across reboots as recommended below (all major
-Linux distributions have done this since 2000 at least), the output is
+If a seed file is saved across reboots as recommended below,
+the output is
 cryptographically secure against attackers without local root access as
 soon as it is reloaded in the boot sequence, and perfectly adequate for
 network encryption session keys.
+(All major Linux distributions have saved the seed file across reboots
+since 2000 at least.)
 Since reads from
 .I /dev/random
 may block, users will usually want to open it in nonblocking mode


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/