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

ncdc 1.10 released + added installation instructions

Browse source
This commit is contained in:
Yorhel 2012-05-04 16:27:45 +02:00
parent e11c9d17e6
commit d1f18971cb
10 changed files with 254 additions and 70 deletions
Download patch file Download diff file Expand all files Collapse all files

54
dat/ncdc-faq
View file

@ -45,31 +45,10 @@ up-to-date client that still uses any of these features.
=head1 Troubleshooting
=head2 How do I install ncdc on Ubuntu?
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\
libncursesw5-dev libxml2-dev libglib2.0-dev
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.
Since version 1.10, it shouldn't crash at all. Please report a bug. (If you're
running an older version, please upgrade!)
=head2 Ncdc uses too much disk space!
@ -96,15 +75,6 @@ L<this is the script I use|http://p.blicky.net/s7132>, which is run as a
monthly cron job.
=head2 I'm getting the error "No PEM-encoded private key found" on startup
(This issue should be fixed since 1.6) Most likely this is caused by a
L<bug in glib-networking|https://bugzilla.gnome.org/show_bug.cgi?id=664321>. To
get around it, install the "certtool" utility that comes with gnutls (package
"gnutls-bin" on Ubuntu), delete the old certificates (C<rm ~/.ncdc/cert/*>),
and then start ncdc again.
=head1 Can ncdc...
@ -125,26 +95,6 @@ L<GNU screen|http://www.gnu.org/s/screen/>,
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 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:
[dcdev]
client = yes
accept = 127.0.0.1:16591
connect = hub.dcbase.org:16591
The URL C<adc://127.0.0.1:16591/> can then be used to connect to the hub from
within ncdc.
=head2 Does ncdc support UPnP?
Not natively. However, it is possible to use L<this