Your message dated Mon, 24 Apr 2006 11:59:53 -0600
with message-id <[EMAIL PROTECTED]>
and subject line WNPP bug closing
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: wnpp
Severity: wishlist
* Package name : cryptknock
Version : 1.0.1
Upstream Author : <[EMAIL PROTECTED]>
* URL : http://sourceforge.net/projects/cryptknock
* License : GPL
Description : Encrypted port knocking daemon with high security
(Include the long description here.)
Cryptknock is an encrypted port knocking tool. Unlike other port
knockers which use TCP ports or other protocol information to signal
the knock, an encrypted string is used as the knock. This makes it
extremely difficult for an evesdropper to recover your knock (unlike
other port knockers where tcpdump can be used to discover a port
knock).
Encryption of the knock string is performed with RC4 using a secret
key derived from a Diffie-Hellman key agreement. The entire process
takes 3 UDP packets. Data is read using libpcap, so no UDP or TCP
ports need to be in a listening state for the program to work.
The daemon records successful and failed knocks via syslog.
Download:
(Link was at the end of page http://cryptknock.sourceforge.net/ )
http://cryptknock.sourceforge.net/cryptknock-1.0.1.tar.gz
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US)
--- End Message ---
--- Begin Message ---
Hello,
This is an automatic mail sent to close the RFP you have reported or
are involved with.
Your RFP wnpp bug is being closed because of the following reasons:
- It is, as of today, older than 365 days.
- It hasn't had any activity recently.
As this is an automatic procedure, it could of course have something
wrong and probably it would be closing some bugs that are not
intended by owners and submitters (like you) to be closed, for
example if the RFP is still of your interest, or there has been
some kind of activity around it. In that case, please reopen the
bug, do it, DO IT NOW! (I don't want to be blamed because of
mass closing and not let people know that they can easily reopen
their bugs ;-).
To re-open it, you simply have to mail [EMAIL PROTECTED]
with a body text like this:
reopen 305587
thanks bts
Further comments on the work done in the bug sent to
[EMAIL PROTECTED] would be truly welcomed.
Anyway, if you have any kind of problems when dealing with
the BTS, feel free to contact me and I'd be more than happy to help
you on this: <[EMAIL PROTECTED]>.
A similar process is being applied to other kind of wnpp bugs.
Thanks for your cooperation,
-- David Moreno Garza <[EMAIL PROTECTED]>.
--- End Message ---
