vndb/yhdev
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

ncdc 1.15 released

Browse source
This commit is contained in:
Yorhel 2013-03-02 14:49:06 +01:00
parent 94ae88d4b9
commit c99ea0d9fc
10 changed files with 83 additions and 74 deletions
Download patch file Download diff file Expand all files Collapse all files

39
dat/ncdc-faq
View file

@ -79,43 +79,20 @@ press and release the 'Esc' key as a replacement for Alt-something. If you're
on OS X, L<this stackoverflow answer|http://stackoverflow.com/a/438892>
may be helpful.
=head2 This "Generating certificates..." is taking ages!
When starting up ncdc for the first time, it will need to generate a TLS
certificate. If you're on Linux, older versions of GnuTLS may use
C</dev/random> to obtain random bytes. Unfortunately, this can be horribly
slow, and in extreme cases it may take several hours before the certificate has
been generated. GnuTLS does not provide a way to use a faster but less secure
alternative, so here are some tips to speed it up or cheat a little.
B<Speed it up:> If you're on a desktop, the general advise is to do something
else on the background so that Linux can generate more data. For example, move
your mouse around a bit, go do some web surfing or play a game. Any activity
might help. If you're on a server, you could try transferring some large data
over the network.
B<Cheat:> If you have root access, you can probably trick GnuTLS by temporarily
replacing C</dev/random> with something else. For example, run C<mv /dev/random
/dev/random.old && ln /dev/urandom /dev/random> as root, then start ncdc as you
normally would, let it generate the certificates, and then restore your
modifications with C<mv /dev/random.old /dev/random>.
If you're on Linux with ncdc 1.14 or older and a GnuTLS older than 3.0, then
creating the certificates required access to C</dev/random> to obtain random
data. This could take a while to complete, especially on headless servers and
low-end devices. Updating to ncdc 1.15 should fix this.
=head2 Ncdc crashes a lot!
Since version 1.13, the following crash is still possible:
=over
=item * You're using an old GnuTLS version (< 3.0, you can check this with
C<ncdc --version>), and you have tls_policy enabled. To fix this, upgrade
GnuTLS or use C</set tls_policy disabled>. (Bug
L<#11|http://dev.yorhel.nl/ncdc/bug/11>).
=back
If you're running an older version of ncdc, please upgrade! If your ncdc is up
to date and you still have a crash not described here, please report a bug.
Ncdc 1.15 has no known bugs that may cause a crash. If you're running an older
version of ncdc, please upgrade. If your ncdc is up to date and you still have
a crash, please report a bug.
=head2 Ncdc uses too much disk space!