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

ncdc 1.11 released + install instructions for OS X and OpenIndiana

Browse source
This commit is contained in:
Yorhel 2012-05-15 14:50:41 +02:00
parent d1f18971cb
commit e82b277935
9 changed files with 120 additions and 24 deletions
Download patch file Download diff file Expand all files Collapse all files

29
dat/ncdc-faq
View file

@ -30,7 +30,7 @@ full article, and I don't feel like writing that much at this point. >_>
=head2 What protocol features does ncdc support?
For ADC: BASE, RF, TIGR, BZIP, ADCS and KEYP.
For ADC: BASE, RF, TIGR, BZIP, ADCS, KEYP and SUDP.
For NMDC: NoGetINFO, NoHello, UserIP2, MiniSlots, XmlBZList, ADCGet, TTHL and TTHF.
@ -45,6 +45,33 @@ up-to-date client that still uses any of these features.
=head1 Troubleshooting
=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, GnuTLS will use C</dev/random> to obtain
random bytes. Unfortunately, this can be horribly slow, and in extreme cases it
may take up to an hour 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 start transferring some large
data over the network.
B<Cheat:> There is also another way to "generate" randomness without waiting
for too long: You can feed some bytes from C</dev/urandom> back to the system
by running the following command as root: C<dd if=/dev/urandom of=/dev/random
bs=512 count=1>. You might have to run that command multiple times to complete
the certificate generation, but certainly no more than about 5 times or so.
Note that this solution weakens the security of the certificate by a bit. For
ncdc that doesn't matter at all, but if you have other applications reading
from C</dev/random>, then the security of those applications is also affected.
Unless you happen to be running something that absolutely requires ulta-secure
random numbers, this trick should be perfectly fine.
=head2 Ncdc crashes a lot!
Since version 1.10, it shouldn't crash at all. Please report a bug. (If you're