wok rev 24944

updated n2n (2.4 -> 3.0)
author Hans-G?nter Theisgen
date Fri Apr 22 16:44:33 2022 +0100 (2022-04-22)
parents 810e3d0a38f7
children 584e67527789
files n2n/description.txt n2n/receipt
line diff
     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/n2n/description.txt	Fri Apr 22 16:44:33 2022 +0100
     1.3 @@ -0,0 +1,27 @@
     1.4 +n2n is a layer-two peer-to-peer virtual private network (VPN)
     1.5 +which allows users to exploit features typical of P2P
     1.6 +applications at network instead of application level.
     1.7 +This means that users can gain native IP visibility (e.g. two
     1.8 +PCs belonging to the same n2n network can ping each other)
     1.9 +and be reachable with the same network IP address regardless
    1.10 +of the network where they currently belong.
    1.11 +In a nutshell, as OpenVPN moved SSL from application (e.g. used
    1.12 +to implement the https protocol) to network protocol, n2n moves
    1.13 +P2P from application to network level.
    1.14 +
    1.15 +The main n2n design features are:
    1.16 +
    1.17 +- An n2n is an encrypted layer two private network based on a
    1.18 +  P2P protocol.
    1.19 +- Encryption is performed on edge nodes using open protocols
    1.20 +  with user-defined encryption keys: you control your security
    1.21 +  without delegating it to companies as it happens with Skype
    1.22 +  or Hamachi.
    1.23 +- Each n2n user can simultaneously belong to multiple networks
    1.24 +  (a.k.a. communities).
    1.25 +- Ability to cross NAT and firewalls in the reverse traffic
    1.26 +  direction (i.e. from outside to inside) so that n2n nodes are
    1.27 +  reachable even if running on a private network. Firewalls no
    1.28 +  longer are an obstacle to direct communications at IP level.
    1.29 +- n2n networks are not meant to be self-contained: it is possible
    1.30 +  to route traffic across n2n and non-n2n networks.
     2.1 --- a/n2n/receipt	Wed Apr 20 16:57:09 2022 +0000
     2.2 +++ b/n2n/receipt	Fri Apr 22 16:44:33 2022 +0100
     2.3 @@ -1,7 +1,7 @@
     2.4  # SliTaz package receipt.
     2.5  
     2.6  PACKAGE="n2n"
     2.7 -VERSION="2.4"
     2.8 +VERSION="3.0"
     2.9  CATEGORY="network"
    2.10  SHORT_DESC="A Layer Two Peer-to-Peer VPN."
    2.11  MAINTAINER="pascal.bellard@slitaz.org"
    2.12 @@ -12,7 +12,7 @@
    2.13  WGET_URL="https://github.com/ntop/$PACKAGE/archive/$VERSION.tar.gz"
    2.14  
    2.15  DEPENDS=""
    2.16 -BUILD_DEPENDS="openssl-dev"
    2.17 +BUILD_DEPENDS="automake libcap-dev openssl-dev"
    2.18  
    2.19  current_version()
    2.20  {
    2.21 @@ -23,15 +23,14 @@
    2.22  # Rules to configure and make the package.
    2.23  compile_rules()
    2.24  {
    2.25 -	make PREFIX=/usr &&
    2.26 -	make DESTDIR=$DESTDIR install
    2.27 +	./autogen.sh &&
    2.28 +	./configure --prefix=/usr &&
    2.29 +	make &&
    2.30 +	make install DESTDIR=$DESTDIR
    2.31  }
    2.32  
    2.33  # Rules to gen a SliTaz package suitable for Tazpkg.
    2.34  genpkg_rules()
    2.35  {
    2.36 -	mkdir -p $fs/usr
    2.37 -
    2.38 -#	cp -a $install/usr/bin	$fs/usr
    2.39 -	cp -a $install/usr/sbin	$fs/usr
    2.40 +	cook_copy_folders	sbin
    2.41  }