Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Rommel <rommel@layer-7.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] knock: new package
Date: Fri, 30 Aug 2013 23:47:16 +0200	[thread overview]
Message-ID: <1377899236-1659-1-git-send-email-rommel@layer-7.net> (raw)

Hi,

sorry for the last post, where I combined two separate packages in one
submission. I now moved them to different branches, cleaned up the 72
char line break as suggested in the other replies to submissions and
this hopefully is more in line with what you expect. Altered title as
well. The pyzmq package will follow shortly.

Cheers,

  Michael.


A port knocking implementation with daemon and user application.

Signed-off-by: Michael Rommel <rommel@layer-7.net>
---
 package/Config.in       |    2 ++
 package/knock/Config.in |   13 +++++++++++++
 package/knock/knock.mk  |   15 +++++++++++++++
 3 files changed, 30 insertions(+)
 create mode 100644 package/knock/Config.in
 create mode 100644 package/knock/knock.mk

diff --git a/package/Config.in b/package/Config.in
index 97cd7da..2f636b6 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -363,6 +363,7 @@ source "package/python-protobuf/Config.in"
 source "package/python-pygame/Config.in"
 source "package/python-pyparsing/Config.in"
 source "package/python-pyro/Config.in"
+source "package/python-pyzmq/Config.in"
 source "package/python-serial/Config.in"
 source "package/python-setuptools/Config.in"
 source "package/python-thrift/Config.in"
@@ -754,6 +755,7 @@ source "package/ipset/Config.in"
 source "package/iptables/Config.in"
 source "package/iw/Config.in"
 source "package/kismet/Config.in"
+source "package/knock/Config.in"
 source "package/lighttpd/Config.in"
 source "package/linknx/Config.in"
 source "package/links/Config.in"
diff --git a/package/knock/Config.in b/package/knock/Config.in
new file mode 100644
index 0000000..f02ecc0
--- /dev/null
+++ b/package/knock/Config.in
@@ -0,0 +1,13 @@
+config BR2_PACKAGE_KNOCK
+	bool "knock"
+	select BR2_PACKAGE_LIBPCAP
+	help
+	  A port knocking implementation.
+	  Provides a daemon and a user application. Port knocking can be
+	  used to run an arbitrary application, once the daemon detects
+	  a predefined sequence of incoming TCP/UDP packets on a network
+	  interface. This can be used, e.g. to open up ports in a
+	  firewall.
+
+	  See also: http://www.zeroflux.org/projects/knock
+
diff --git a/package/knock/knock.mk b/package/knock/knock.mk
new file mode 100644
index 0000000..4483e8f
--- /dev/null
+++ b/package/knock/knock.mk
@@ -0,0 +1,15 @@
+##########################################
+#
+# knock
+#
+##########################################
+
+KNOCK_VERSION=7666f2e86e18d482eaad5fe1fea46d87d80b0555
+KNOCK_SITE=https://github.com/jvinet/knock/tarball/master
+KNOCK_LICENSE = GPLv2
+KNOCK_LICENSE_FILES = COPYING
+KNOCK_AUTORECONF = YES
+KNOCK_INSTALL_TARGET_OPT = DESTDIR=$(TARGET_DIR) install-sbinPROGRAMS
+
+$(eval $(autotools-package))
+
-- 
1.7.9.5

             reply	other threads:[~2013-08-30 21:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30 21:47 Michael Rommel [this message]
2013-08-31  8:56 ` [Buildroot] [PATCH 1/1] knock: new package Thomas De Schampheleire
2013-08-31 11:50 ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1377899236-1659-1-git-send-email-rommel@layer-7.net \
    --to=rommel@layer-7.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox