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

Ncdc 1.8 released + various other changes and fixes

Browse source
This commit is contained in:
Yorhel 2012-02-13 10:20:13 +01:00
parent 91863fab76
commit 1d24a2c6bb
12 changed files with 129 additions and 62 deletions
Download patch file Download diff file Expand all files Collapse all files

28
dat/ncdc-faq
View file

@ -47,7 +47,11 @@ up-to-date client that still uses any of these features.
=head2 How do I install ncdc on Ubuntu?
This is for Ubuntu 11.10, but may work for other versions as well. Run the
Try the package from the L<Open Build
Service|http://software.opensuse.org/download.html?project=home:yorhel&package=ncdc>
and follow those instructions.
Alternatively, you can also build directly from the source. To do so, run the
following command:
sudo apt-get install libbz2-dev libsqlite3-dev\
@ -56,6 +60,18 @@ following command:
And then follow the instructions in the README.
=head2 Ncdc crashes a lot!
Make sure client-to-client TLS is disabled:
/set tls_policy disabled
If that doesn't fix it, please report a bug. You may also wish to debug the
problem a bit further yourself, in which case the L<HACKING
file|http://g.blicky.net/ncdc.git/tree/HACKING> will have some valuable
information.
=head2 Ncdc uses too much disk space!
First, look where this disk space goes to (hint: use
@ -111,11 +127,11 @@ L<tmux|http://tmux.sourceforge.net/> or L<dtach|http://dtach.sourceforge.net/>.
=head2 Does ncdc support TLS?
Yes! To make use of this, however, you need to have relatively new version
of glib2. If you're still working with an outdated system, an alternative
is to use L<stunnel|http://www.stunnel.org/> to connect to
TLS-enabled hubs. This trick does not allow encrypted client-to-client
connections, so your file transfers will remain unencrypted.
Yes! To make use of this, however, you need to have a relatively new version of
glib2. If you're still working with an outdated system, an alternative is to
use L<stunnel|http://www.stunnel.org/> to connect to TLS-enabled hubs. This
trick does not allow encrypted client-to-client connections, so your file
transfers will remain unencrypted.
The following example stunnel configuration is what I used to connect to
the DC Development hub before ncdc had native TLS support: