[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#261189: marked as done (ITP: libsrs -- official ANSI C sender rewriting scheme (SRS) library)



Your message dated Thu, 22 Sep 2005 17:17:46 -0600
with message-id <E1EIaK2-0006ku-00@merkel.debian.org>
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)

--------------------------------------
Received: (at submit) by bugs.debian.org; 24 Jul 2004 08:05:05 +0000
>From madduck@cirrus.madduck.net Sat Jul 24 01:05:05 2004
Return-path: <madduck@cirrus.madduck.net>
Received: from armagnac.ifi.unizh.ch (albatross.madduck.net) [130.60.75.72] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1BoHWi-0007fP-00; Sat, 24 Jul 2004 01:05:04 -0700
Received: from localhost (albatross.madduck.net [127.0.0.1])
	by albatross.madduck.net (postfix) with ESMTP id BCE78ACC9
	for <submit@bugs.debian.org>; Sat, 24 Jul 2004 10:05:03 +0200 (CEST)
Received: from localhost (80-219-170-226.dclient.hispeed.ch [80.219.170.226])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "cirrus.madduck.net", Issuer "madduck.net CA" (verified OK))
	by albatross.madduck.net (postfix) with ESMTP id 46FFDA386
	for <submit@bugs.debian.org>; Sat, 24 Jul 2004 10:05:03 +0200 (CEST)
Received: by localhost (Postfix, from userid 1000)
	id 8BCE1212E9E; Sat, 24 Jul 2004 10:04:57 +0200 (CEST)
Date: Sat, 24 Jul 2004 10:04:57 +0200
From: martin f krafft <madduck@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: ITP: libsrs -- official ANSI C sender rewriting scheme (SRS) library
Message-ID: <20040724080457.GA26819@cirrus.madduck.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="4Ckj6UjgE2iN1+kY"
Content-Disposition: inline
X-Reportbug-Version: 2.63
X-Debbugs-Cc: debian-devel@lists.debian.org
Organization: Debian GNU/Linux
X-OS: Debian GNU/Linux testing/unstable kernel 2.6.7-1-k7 i686
X-Motto: Keep the good times rollin'
X-Subliminal-Message: debian/rules!
User-Agent: Mutt/1.5.6+20040523i
X-Virus-Scanned: by albatross.madduck.net
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-11.0 required=4.0 tests=BAYES_00,HAS_PACKAGE,
	X_DEBBUGS_CC autolearn=ham version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 


--4Ckj6UjgE2iN1+kY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Package: wnpp
Severity: wishlist

* Package name    : libsrs
  Version         : 1.0.0 rc1
  Upstream Author : James Couzens <jcouzens@codeshare.ca>
* URL             : http://www.librs.org
* License         : see below
  Description     : official ANSI C sender rewriting scheme (SRS) library

libSRS is an ANSI[0] C implementation of one proposed solution to the
SPF[1] ("Sender Policy Framework") forwarding problem.  Through the very
nature of forwarding SPF checks fail when a forwarder does its intended
job because the Email is now literally being forged, or to be more
politically correct, "delivered on behalf of" :-).  libSRS attempts to
implement a solution for this using strong cryptographic HMAC's embedded
within the local-part (hence the name "rewriting scheme") to enable
messages to change hands and still retain information stored in a secure
fashion so as to faciliate the passing of SPF checks when the message
does finally arrive at its destination.

libSRS is currently in the "Release Client" stage on its way to a STABLE
version.  Previous to recently, no code was changed since early 2004,
and only recently relating to changes in the specification.  The
development branch of libSRS contains feature enhancements such as an
independent hashing algorithm designed to act as an alternative to the
reliable but somewhat slow OpenSSL (although to be perfectly honest,
OpenSSL is MORE than adequate for this purpose, is better then any
hashing implementation I'm ever to likely write, and is readily
available everywhere).

[0] to support the method of debugging employed in libSRS the library
looses its C/89 compliance to take advantage of Variadic Arguments
(__VA_VARARGS__) which are taken from the ISO C/99 C standard.  Any
stable branch of libSRS will loose the debugging code and reclaim C/89
compliant status.

[1] SPF is formerly known as Sender Permitted From

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (600, 'testing'), (98, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.7-1-k7
Locale: LANG=3Den_GB.UTF-8, LC_CTYPE=3Den_GB.UTF-8

--=20
Please do not CC me when replying to lists; I read them!
=20
 .''`.     martin f. krafft <madduck@debian.org>
: :'  :    proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
=20
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!

--4Ckj6UjgE2iN1+kY
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBAhgpIgvIgzMMSnURAlgeAJ4u4btY0yE1YUw/5NsZe/zXJmuP/wCfdLx5
+lFVl9cp40bpioxD9DctuSg=
=2bNP
-----END PGP SIGNATURE-----

--4Ckj6UjgE2iN1+kY--

---------------------------------------
Received: (at 261189-done) by bugs.debian.org; 22 Sep 2005 23:17:46 +0000
>From damog@merkel.debian.org Thu Sep 22 16:17:46 2005
Return-path: <damog@merkel.debian.org>
Received: from merkel.debian.org [192.25.206.16] (mail)
	by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
	id 1EIaK2-0000yR-00; Thu, 22 Sep 2005 16:17:46 -0700
Received: from damog by merkel.debian.org with local (Exim 3.36 1 (Debian))
	id 1EIaK2-0006ku-00; Thu, 22 Sep 2005 17:17:46 -0600
To: 261189-done@bugs.debian.org
Subject: WNPP bug closing
Message-Id: <E1EIaK2-0006ku-00@merkel.debian.org>
From: David Moreno Garza <damog@merkel.debian.org>
Date: Thu, 22 Sep 2005 17:17:46 -0600
Delivered-To: 261189-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-5.0 required=4.0 tests=BAYES_00,VALID_BTS_CONTROL 
	autolearn=no version=2.60-bugs.debian.org_2005_01_02

Hello,

This is an automatic mail sent to close the ITP you have reported or 
are involved with.

Your ITP 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 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 ITP 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 control@bugs.debian.org
with a body text like this:

reopen 261189
thanks bts

Further comments on the work done in the bug sent to
261189@bugs.debian.org 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: <damog@debian.org>.

This is the second massive wnpp closing that is being done. The next close
will be done on inactive ITPs older than 365 days and finally, an automatic
script will close, by default, *inactive* ITPs when they reach one year of
inactivity.

A similar process is being applied to other kind of wnpp bugs.

Thanks for your cooperation,

 -- David Moreno Garza <damog@debian.org>  Thu, 22 Sep 2005 17:06:42 -0500



Reply to: