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

ncdc 1.12 released.

Browse source
This commit is contained in:
Yorhel 2012-07-10 15:17:53 +02:00
parent e82b277935
commit 1ac0600f93
10 changed files with 109 additions and 24 deletions
Download patch file Download diff file Expand all files Collapse all files

2
dat/ncdc
View file

@ -10,7 +10,7 @@ ncurses interface.
=item Latest version
1.11 ([dllink ncdc-1.11.tar.gz download]
1.12 ([dllink ncdc-1.12.tar.gz download]
- L<changes|http://dev.yorhel.nl/ncdc/changes>
- L<mirror|https://sourceforge.net/projects/ncdc/files/ncdc/>)

18
dat/ncdc-changelog
View file

@ -1,3 +1,21 @@
1.12 - 2012-07-10
- Don't follow symlinks in share by default
- Added 'share_symlink' option
- Added bell notification and 'notify_bell' option
- Added 'sudp_policy' setting
- List all configured hubs on '/open'
- Added '/delhub' command to remove hub configuration
- Added filtering options to connections tab
- Added TLS support indication to user list
- Added Alt+a key to cycle through tabs with recent activity
- Allow binding to ports below 1024
- Add space after autocompleting a command
- Fix uploading chunks of 2GiB and larger (bug #12)
- Fix bug with duplicate directory detection in '/share'
- Fix display of timer on search tab
- ADC: Use shorter search token to save some bandwidth
- Various attempts at cleaning up some code
1.11 - 2012-05-15
- Drop libxml2 in favour of custom XML parser & writer
- Allow using a single listen port for TCP and TLS

38
dat/ncdc-faq
View file

@ -34,7 +34,7 @@ For ADC: BASE, RF, TIGR, BZIP, ADCS, KEYP and SUDP.
For NMDC: NoGetINFO, NoHello, UserIP2, MiniSlots, XmlBZList, ADCGet, TTHL and TTHF.
ncdc also support TLS-enabled connections for both hub connections and
ncdc also supports TLS-enabled connections for both hub connections and
client-to-client connections on both ADC and NMDC protocols. Note that ncdc
does not support some of the older NMDC protocol features, like $Get,
$GetZBlock, $CHUNK, $Cancel or non-XML file lists. I am not aware of an other
@ -48,11 +48,11 @@ up-to-date client that still uses any of these features.
=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.
certificate. If you're on Linux, some 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 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
@ -74,8 +74,26 @@ 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
running an older version, please upgrade!)
Since version 1.10, the following crashes are possible:
=over
=item * You're using an old GnuTLS version (< 2.10 or so, you can check this
with C<ncdu --version>), and you have tls_policy enabled. To fix this, upgrade
GnuTLS or C</set tls_policy disabled>. (Bug L<#11|http://dev.yorhel.nl/ncdc/bug/11>).
=item * You're running ncdc on an old system. FreeBSD <= 8.0 and Mac OS X <=
10.5 are known to be problematic. To get around this, upgrade your system or
bug me hard enough to come with a fix within ncdc. (Bug
L<#14|http://dev.yorhel.nl/ncdc/bug/14>).
=item * You were typing a C</search> command but forgot to provide a query.
This crash will be fixed soonish.
=back
If you're running an older version of ncdc, please upgrade! If your ncdc is up
to date and still have a crash not described here, please report a bug.
=head2 Ncdc uses too much disk space!
@ -110,7 +128,9 @@ monthly cron job.
No, ncdc uses its own configuration and hash storage directory. However, on
popular demand I could write a conversion utility to transfer the hash data
from other clients to ncdc's format.
from other clients to ncdc's format. (Contrary to my expectations, there hasn't
been much interest in such a tool ever since I wrote this FAQ entry a year ago.
So I guess this isn't really a FAQ).
=head2 Can ncdc run in the background / as a daemon?

24
dat/ncdc-install
View file

@ -38,9 +38,11 @@ compiling and/or installing it, I also offer statically linked binaries:
=over
=item * L<Linux, 64-bit|http://dev.yorhel.nl/download/ncdc-linux-x86_64-1.11.tar.gz>
=item * L<Linux, 64-bit|http://dev.yorhel.nl/download/ncdc-linux-x86_64-1.12.tar.gz>
=item * L<Linux, 32-bit|http://dev.yorhel.nl/download/ncdc-linux-i386-1.11.tar.gz>
=item * L<Linux, 32-bit|http://dev.yorhel.nl/download/ncdc-linux-i386-1.12.tar.gz>
=item * L<Linux, ARM|http://dev.yorhel.nl/download/ncdc-linux-arm-1.12.tar.gz> (Only tested on some devices, may not work on all)
=back
@ -117,9 +119,9 @@ First install some required packages (as root):
Then, fetch the ncdc source tarball, extract and build as follows:
wget http://dev.yorhel.nl/download/ncdc-1.11.tar.gz
tar -xf ncdc-1.11.tar.gz
cd ncdc-1.11
wget http://dev.yorhel.nl/download/ncdc-1.12.tar.gz
tar -xf ncdc-1.12.tar.gz
cd ncdc-1.12
export PATH="$PATH:/usr/perl5/5.10.0/bin"
./configure --prefix=/usr LDFLAGS='-L/usr/gnu/lib -R/usr/gnu/lib'
make
@ -167,9 +169,9 @@ required libraries:
Then run the following commands to download and install ncdc:
wget http://dev.yorhel.nl/download/ncdc-1.11.tar.gz
tar -xf ncdc-1.11.tar.gz
cd ncdc-1.11
wget http://dev.yorhel.nl/download/ncdc-1.12.tar.gz
tar -xf ncdc-1.12.tar.gz
cd ncdc-1.12
./configure --prefix=/usr
make
sudo make install
@ -209,8 +211,8 @@ website|http://cygwin.com/> and use it to install the following packages:
Then open a Cygwin terminal and run the following commands to download,
compile, and install ncdc:
wget http://dev.yorhel.nl/download/ncdc-1.11.tar.gz
tar -xf ncdc-1.11.tar.gz
cd ncdc-1.11
wget http://dev.yorhel.nl/download/ncdc-1.12.tar.gz
tar -xf ncdc-1.12.tar.gz
cd ncdc-1.12
./configure --prefix=/usr
make install

29
dat/ncdc-man
View file

@ -130,6 +130,10 @@ See the /open command for more information.
Open the connections tab.
=item B</delhub> <name>
Remove a hub from the configuration
=item B</disconnect>
Disconnect from a hub.
@ -188,9 +192,9 @@ Send a private message to a user on the currently opened hub. If no message is g
Alias for `/hset nick' on hub tabs, and `/set nick' otherwise.
=item B</open> [-n] <name> [<address>]
=item B</open> [-n] [<name>] [<address>]
Opens a new tab to use for a hub. The name is a (short) personal name you use to identify the hub, and will be used for storing hub-specific configuration.
Without arguments, list all hubs known by the current configuration. Otherwise, this opens a new tab to use for a hub. The name is a (short) personal name you use to identify the hub, and will be used for storing hub-specific configuration.
If you have specified an address or have previously connected to a hub from a tab with the same name, /open will automatically connect to the hub. Use the `-n' flag to disable this behaviour.
@ -471,6 +475,16 @@ The maximum size of a file that may be downloaded using a `minislot', in KiB. Se
Your nick. Nick changes are only visible on newly connected hubs, use the `/reconnect' command to use your new nick immediately. Note that it is highly discouraged to change your nick on NMDC hubs. This is because clients downloading from you have no way of knowing that you changed your nick, and therefore can't immediately continue to download from you.
=item B<notify_bell> <disable|low|medium|high>
When enabled, ncdc will send a bell to your terminal when a tab indicates a notification. The notification types are:
high - Messages directed to you (PM or highlight in hub chat),
medium - Regular hub chat,
low - User joins/quits, new search results, etc.
How a "bell" (or "beep" or "alert", whatever you prefer to call it) manifests itself depends on your terminal. In some setups, this generates an audible system bell. In other setups it can makes your terminal window flash or do other annoying things to get your attention. And in some setups it is ignored completely.
=item B<password> <string>
Sets your password for the current hub and enables auto-login on connect. If you just want to login to a hub without saving your password, use the `/password' command instead. Passwords are saved unencrypted in the config file.
@ -491,6 +505,10 @@ Any file or directory with a name that matches this regular expression will not
Whether to share hidden files and directories. A `hidden' file or directory is one of which the file name starts with a dot. (e.g. `.bashrc'). A file list refresh is required for this setting to be effective.
=item B<share_symlinks> <boolean>
Whether to follow symlinks in shared directories. When disabled (default), ncdc will never share any files outside of the directory you specified. When enabled, any symlinks in your shared directories will be followed, even when they point to a directory outside your share.
=item B<show_joinquit> <boolean>
Whether to display join/quit messages in the hub chat.
@ -499,6 +517,12 @@ Whether to display join/quit messages in the hub chat.
The number of upload slots. This determines for the most part how many people can download from you simultaneously. It is possible that this limit is exceeded in certain circumstances, see the `minislots' setting and the `/grant' command.
=item B<sudp_policy> <disabled|allow|prefer>
Set the policy for sending or receiving encrypted UDP search results. When set to `disabled', all UDP search results will be sent and received in plain text. Set this to `allow' to let ncdc reply with encrypted search results if the other client requested it. `prefer' will also cause ncdc itself to request encryption.
Note that, regardless of this setting, encrypted UDP search results are only used on ADCS hubs. They will never be sent on NMDC or non-TLS ADC hubs. Also note that, even if you set this to `prefer', encryption is still only used when the client on the other side of the connection also supports it.
=item B<tls_policy> <disabled|allow|prefer>
Set the policy for secure client-to-client connections. Setting this to `disabled' disables TLS support for client connections, but still allows you to connect to TLS-enabled hubs. `allow' will allow the use of TLS if the other client requests this, but ncdc itself will not request TLS when connecting to others. Setting this to `prefer' tells ncdc to also request TLS when connecting to others.
@ -536,6 +560,7 @@ C</help keys> command, and is reproduced below.
Alt+k Open next tab.
Alt+h Move current tab left.
Alt+l Move current tab right.
Alt+a Move tab with recent activity.
Alt+<num> Open tab with number <num>.
Alt+c Close current tab.
Alt+n Open the connections tab.

2
dat/sqlaccess
View file

@ -18,7 +18,7 @@ responsive and handling most of the network interaction. Overall responsiveness
of the program would significantly improve when the threads could access the
database without involvement of the main thread.
Which brings us to the following question: What solutions are available for
Which brought me to the following questions: What solutions are available for
providing multi-threaded access to an SQLite database? What problems may I run
in to? I was unable to find a good overview in this area on the net, so I wrote
this article with the hope to improve that situation.