leading to predictable session keys~\cite{HDWH12}.
\subsection{Linux}
+\label{subsec:RNG-linux}
On Linux there are two devices that return random bytes when read, the
\verb+/dev/random+ can block until sufficient entropy has been collected
process. On the other hand this can be used for running a secondary
entropy collector to inject entropy into the kernel entropy pool.
+On Linux you can check how much entropy is available with the command:
+\begin{lstlisting}
+$ cat /proc/sys/kernel/random/entropy_avail
+\end{lstlisting}
+
%% specifics for libraries
%% Openssl uses /dev/urandom. See the paper: https://factorable.net/weakkeys12.conference.pdf (section 5.2)
%% What about other libs?
default-preference-list SHA512 SHA384 SHA256 SHA224 AES256 AES192 AES CAST5 ZLIB BZIP2 ZIP Uncompressed
\end{lstlisting}
+Before you generate a new PGP key, make sure there is enough entropy available (see subsection \ref{subsec:RNG-linux}).
+
%\subsubsection{PGP / GPG Operations}
%% Ciphering - Unciphering operations
leading to predictable session keys~\cite{HDWH12}.
\subsection{Linux}
+\label{subsec:RNG-linux}
\todo{Other architectures, BSD, Windows?}
process. On the other hand this can be used for running a secondary
entropy collector to inject entropy into the kernel entropy pool.
+On Linux you can check how much entropy is available with the command:
+\begin{lstlisting}
+$ cat /proc/sys/kernel/random/entropy_avail
+\end{lstlisting}
+
%% specifics for libraries
%% Openssl uses /dev/urandom. See the paper: https://factorable.net/weakkeys12.conference.pdf (section 5.2)
%% What about other libs?