Bug#543150: ITP: pdkim -- cryptographically identify the sender of email
Package: wnpp Severity: wishlist Owner: Magnus Holmgren * Package name: pdkim Version : 1.0 Upstream Author : Tom Kistner * URL : http://duncanthrax.net/pdkim/ * License : GPL Programming Lang: C Description : cryptographically identify the sender of email PDKIM is another DKIM (RFC4871) library written by Tom Kistner because libdkim was lacking some functionality needed in Exim and the developers are unresponsive. Its main virtues are: * Self-contained, no dependencies (except libc), thanks to code included from the PolarSSL project. * Cross-Platform. Works on Unix™ and Windows™. * Straightforward API * Small size * GPL license -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#543150: ITP: pdkim -- cryptographically identify the sender of email
On måndagen den 24 augusti 2009, Andreas Metzler wrote: > On 2009-08-23 Magnus Holmgren wrote: > > On lördagen den 22 augusti 2009, Aaron M. Ucko wrote: > >> Magnus Holmgren writes: > >>> * Self-contained, no dependencies (except libc), thanks to code > >>> included from the PolarSSL project. > >> > >> From a Debian perspective, that's a policy violation, not a feature! > >> > >> Please arrange for it to use an external PolarSSL installation. > > > > I know and agree and will talk to Tom about this. PolarSSL currently only > > provides a static library however, which is also not good. > > I am somehow also not happy with a situation where any given exim > installation would end linked dynamically (indirectly) against at least > two full blown ssl libraries (OpenSSL or GnuTLS for STARTTLS, polarssl > for DKIM). > > On a sidenote, is the cause for this ITP just exim or is general > interest in this library? Primarily for Exim. Also because I already maintain a couple of DKIM-related packages. Did you want it? -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#411685: Package removed (pike7.7)
reopen 411685 retitie 411685 ITP: pike7.8 -- Powerful interpreted programming language, development version owner ! On torsdagen den 1 maj 2008, you stated the following: > pike7.7 was removed from the archive (see #477137). pike7.7 was intended to be renamed pike7.8 anyway, because that's what the stable release will eventually be called. Since I maintain pike7.6 I also intend to maintain pike7.8. Since there hs never been a pike7.8 package in Debian yet, I call this an ITA, but since it's essentially the same package as pike7.7 I reuse this bug. -- Magnus Holmgren[EMAIL PROTECTED] Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#373213: RFP: libmail-domainkeys-perl -- Perl DomainKeys implementation
Package: wnpp Severity: wishlist See http://antispam.yahoo.com/domainkeys for a description of DomainKeys. SpamAssassin could use this package, for example. Source available from http://killa.net/infosec/Mail-DomainKeys/ (also distributed through CPAN). Depends on libcrypt-openssl-*-perl, which are in the process of being packaged. See also bug #352653. I'm interested in packaging this myself, if anyone is willing to sponsor me. -- Magnus Holmgren[EMAIL PROTECTED] (No Cc of list mail needed, thanks) pgp7asj0E2akC.pgp Description: PGP signature
Bug#352653: RFP: libdomainkeys
retitle 352653 ITP: libdomainkeys -- DomainKeys reference implementation tags 352653 patch waits-for-sponsor owner 352653 [EMAIL PROTECTED] thanks I have created a set of packages available from http://www.kibibyte.se/download/debian/. As a proof of concept, this mail is DK-signed using it (and a custom Exim package). However, there seems to be some confusion as to copyright and licences. http://antispam.yahoo.com/domainkeys states that "Yahoo!'s DomainKeys Intellectual Property may be licensed under either of the following terms: * Yahoo! DomainKeys Patent License Agreement [v1.2] * GNU General Public License version 2.0 (and no other version)." But the license included in the source tarball is "Yahoo! DomainKeys Public License Agreement v1.1". There is also no mention of GPL. I guess that the *patents* are licenced separately from the reference *implementation*. If so, there seems to be no clear copyright statement in the tarball (the "Copyright (c) 2004, Yahoo! Inc." in softwarelicense1-1.html appears to refer to the license text itself, I mean, it's meant to used for redistributions with additions and modifications as well). So in debian/copyright I wrote "Copyright (c) 2004-2006, Yahoo! Inc. and contributors." and a reference to the HTML file. The Makefile was very simple and only built a static library, so I manually "libtoolized" it quite a bit. Next I'll create a pkg-config file. -- Magnus Holmgren[EMAIL PROTECTED] [EMAIL PROTECTED] (No Cc of list mail needed, thanks) pgptt8nPb95aH.pgp Description: PGP signature
Bug#373213: RFP: libmail-domainkeys-perl -- Perl DomainKeys implementation
retitle 373213 ITP: libmail-domainkeys-perl -- Perl DomainKeys implementation tags 373213 patch I should provide the standard template info... * Package name: libmail-domainkeys-perl Version : 0.80 Upstream Author : Anthony D. Urso * URL : http://killa.net/infosec/Mail-DomainKeys/ * License : Perl license (Artistic or GPL) Programming Lang: Perl Description : Perl module providing an implementation of DomainKeys. Unfortunately the modules only implement draft 03, but let's worry about that when DomainKeys/DKIM reaches Standards Track. :-) My packages can be found at http://www.kibibyte.se/download/debian Sponsoring, anyone? -- Magnus Holmgren[EMAIL PROTECTED] (No Cc of list mail needed, thanks) pgpAUgj8JiJg3.pgp Description: PGP signature
Bug#440911: ITP: policyd-spf-fs -- Postfix policy server for SPF checking
Package: wnpp Severity: wishlist Owner: Magnus Holmgren <[EMAIL PROTECTED]> * Package name: policyd-spf-fs Version : 0+svn21 Upstream Author : Matthias Cramer <[EMAIL PROTECTED]> * URL : http://www.freestone.net/software/policyd-spf-fs/ * License : LGPL 2.1 and/or 2-clause BSD Programming Lang: C Description : Postfix policy server for SPF checking policyd-spf-fs is a simple Sender Policy Framework (SPF) policy engine for the Postfix MTA, written in C. Postfix SMTP Access Policy Delegation is described at http://www.postfix.org/SMTPD_POLICY_README.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#422151: RFP: libspf2-policyd
I've filed a separate ITP for policyd-spf-fs; it's bug #440911. -- Magnus Holmgren [EMAIL PROTECTED] [EMAIL PROTECTED] pgpYzE3kqajt3.pgp Description: PGP signature
Bug#440911: ITP: policyd-spf-fs -- Postfix policy server for SPF checking
On Wednesday 05 September 2007 22:53, Bernd Zeimetz wrote: > we have > 0 [EMAIL PROTECTED]:$ apt-cache search postfix spf policyd > postfix-policyd-spf-perl - pure-Perl Postfix policy server for SPF checking > python-policyd-spf - pure-Python Postfix policy daemon for SPF checking > > do we really need another one? Well, this one is written in C, so it should be slightly more lightweight, shouldn't it? -- Magnus Holmgren pgpG3qBDDkILw.pgp Description: PGP signature
Bug#456227: sphinx, sphinx-search -- same thing
Marco Rodrigues <[EMAIL PROTECTED]> wrote: > * Package name: sphinx > Version : 0.9.7 > Upstream Author : Andrew Aksyonoff <[EMAIL PROTECTED]> > * URL : http://www.sphinxsearch.com > * License : GPL-2 > Programming Lang: C++ > Description : Free SQL full-text search engine Monty Taylor <[EMAIL PROTECTED]> submitted: > Sphinx can be downloaded from http://www.sphinxsearch.com > > Debian packages are being developed out of > http://launchpad.net/pkg-sphinx and have a package repository at: > > deb http://ppa.launchpad.net/pkg-sphinx/ubuntu gutsy main > deb-src http://ppa.launchpad.net/pkg-sphinx/ubuntu gutsy main Monty, Marco, I think you may be working on the same piece of software without being aware of it. Perhaps you can cooperate. -- Magnus Holmgren[EMAIL PROTECTED] (No Cc of list mail needed, thanks) signature.asc Description: This is a digitally signed message part.
Bug#458000: sphinx, sphinx-search -- same thing
owner 458000 Monty Taylor <[EMAIL PROTECTED]>, Marco Rodrigues <[EMAIL PROTECTED]> thanks On torsdagen den 3 januari 2008, Monty Taylor wrote: > As the ITP says, I've got some debs over at launchpad you can look at. > It turns out we might want to file yet-one-more ITP and retire these. No need to file a new ITP; you can always retitle the existing one(s). You *should* send a complete copy to debian-devel, however. I wonder if a bug can have multiple owners, even though the documentation doesn't say so... -- Magnus Holmgren[EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part.
Bug#429873: RFH: kradio -- Comfortable Radio Application for KDE
On Wednesday 20 June 2007 23:15, Steffen Joeris wrote: > I request assistance with maintaining the kradio package. > Right now I do not have a working card anymore, which makes it hard to > test it properly. I use kradio and I have a card (the TV tuner doesn't function properly anymore, but the radio works). What do you need help with? There are no open bugs ATM. -- Magnus Holmgren[EMAIL PROTECTED] (No Cc of list mail needed, thanks) pgpt01tWYT5tK.pgp Description: PGP signature
Bug#434357: RFA: xinetd -- replacement for inetd with many enhancements
I was interested in xinetd too, but I forgot to check this spot before diving
in. Please consider starting from the attached Debian diff, which does the
following:
* Use dpatch to organise patches.
* Get rid of config.{guess,sub} from Debian diff by using files from
autotools-dev (see 01_autotools-dev.dpatch).
Thomas, what does the remaining diff in 01_debian-patch.dpatch (touching
service.c) do?
--
Magnus Holmgren[EMAIL PROTECTED]
xinetd_2.3.14-2.diff.gz
Description: GNU Zip compressed data
pgp4oBOh6OofG.pgp
Description: PGP signature
Bug#411684: ITA pike packages
retitle 411684 ITA: pike7.6 -- Powerful interpreted programming language, stable version owner 411684 ! retitle 411685 ITA: pike7.7 -- Powerful interpreted programming language, development version owner 411685 ! thanks After discussion with upstream, I intend to adopt the pike packages together with Henrik Andreasson <[EMAIL PROTECTED]>. Bertrand LUPART <[EMAIL PROTECTED]> also offered help. -- Magnus Holmgren[EMAIL PROTECTED] [EMAIL PROTECTED] pgpNSLoei7Onz.pgp Description: PGP signature
Bug#537259: O: skencil -- Interactive vector drawing program for X11
On torsdagen den 16 juli 2009, you stated the following: > I'm orphaning skencil due to lack of interest in this package. > > If there is no new maintainer within about a month, I'm going to > request its removal. So...? :-) -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#378046: ITP: libmail-dkim-perl -- Create and verify DKIM (DomainKeys Identified Mail) signatures
Package: wnpp Severity: wishlist Owner: Magnus Holmgren <[EMAIL PROTECTED]> * Package name: libmail-dkim-perl Version : 0.18 Upstream Author : Jason Long <[EMAIL PROTECTED]> * URL : http://jason.long.name/ * License : "Same as Perl" Programming Lang: Perl Description : Create and verify DKIM (DomainKeys Identified Mail) signatures DomainKeys Identified Mail (DKIM) provides a method for validating an identity that is associated with a message, during the time it is transferred over the Internet. That identity then can be held accountable for the message. See http://www.dkim.org/ This is a Perl implementation created by Jason Long of Messiah College. It performs signing as well as signature verification. The library is largely based on Mail::DomainKeys. For those who don't know, DKIM is a merge of Yahoo!'s [1]DomainKeys and Cisco's [2]Internet Identified Mail. An IETF [3]working group has been chartered with the goal of creating standards-track specifications. Because of Yahoo!'s DomainKeys patents, they have made the following IPR disclosure: https://datatracker.ietf.org/public/ipr_detail_show.cgi?ipr_id=716 where they repeat the statement from [1] that they license the Necessary Patent Claims under either of the DomainKeys Patent License Agreement (v1.2) and the GPL v2.0. We need to determine exactly what it means to license patents under the GPL. [1] http://antispam.yahoo.com/domainkeys [2] http://www.identifiedmail.com/ [3] http://ietf.org/html.charters/dkim-charter.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#378863: ITP: libcsoap1-dev -- library in C for SOAP network protocol (SOAP is a form of RPC) development
On Wednesday 19 July 2006 14:06, Rudi Cilibrasi took the opportunity to write: > Package: wnpp > Severity: wishlist > Owner: Rudi Cilibrasi <[EMAIL PROTECTED]> > > > * Package name: libcsoap1-dev > Version : 1.047 You need only post one ITP bug per source package. And AFAICS there is just one which builds both the library and the development files. BTW, isn't the version number of the latest stable release 1.0.4? -- Magnus Holmgren[EMAIL PROTECTED] (No Cc of list mail needed, thanks) pgpfp5nFnZVP9.pgp Description: PGP signature
Bug#352653: RFP: libmail-domainkeys-perl -- Perl DomainKeys implementation
On Monday 14 August 2006 16:19, gregor herrmann took the opportunity to say: > Anything new regarding libmail-domainkeys-perl? I'd really like to > see this module in Debian. Stuck on legal issues. See http://lists.debian.org/debian-legal/2006/06/msg00292.html and http://lists.debian.org/debian-legal/2006/07/msg00149.html. So far there have been few real signs of interest, so your input is welcome. If more people show interest the Debian folks might spend some time helping to resolve the issues. -- Magnus Holmgren[EMAIL PROTECTED] (No Cc of list mail needed, thanks) pgpeByLZ0Zzyh.pgp Description: PGP signature
Bug#352533: ITA: sa-exim -- use SpamAssassin at SMTP time with the Exim v4 MTA
What's happening here? I can take it if Anand lost interest or time. -- Magnus Holmgren[EMAIL PROTECTED] (No Cc of list mail needed, thanks) pgpmd6IbtXQdr.pgp Description: PGP signature
Bug#352533: ITA: sa-exim -- use SpamAssassin at SMTP time with the Exim v4 MTA
(Trying this address instead.) Hi Anand! Are you still intending to adopt sa-exim? If you feel satisfied with your 26 packages I'm interested in maintaining it (I only have one so far (as [EMAIL PROTECTED] (my own domain))). -- Magnus Holmgren[EMAIL PROTECTED] pgpqsFddVnJ9o.pgp Description: PGP signature
Bug#392823: ITP: prayer -- fast IMAP-based web mail system with few dependencies
On Tuesday 31 October 2006 10:21, Jonathan McDowell wrote: > I hacked Prayer to work with Dovecot in a saner fashion; see: > > http://www.earth.li/~noodles/blog/webmail-sucks.html Interesting; thanks. A big step in the right direction, but still won't recognise folders with subfolders. I think I have to read the IMAP RFC thoroughly. -- Magnus Holmgren[EMAIL PROTECTED] (No Cc of list mail needed, thanks) pgpdcrRwx3Xc3.pgp Description: PGP signature
Bug#392823: ITP: prayer -- fast IMAP-based web mail system with few dependencies
retitle 392823 ITP: prayer -- fast IMAP-based web mail system with few dependencies owner 392823 Magnus Holmgren <[EMAIL PROTECTED]> thanks I've sent some questions and comments upstream. Most notably, * Prayer assumes that folders can't contain other folders, even if the IMAP server supports it. It appears that Dovecot with Maildir doesn't work very well with Prayer - all folders are treated as directories. Directories are containers for folders and other directories, but can't contain any mail. I don't know if this is an unavoidable problem with libc-client, or just a design mistake in Prayer. Anyway Prayer probably works best with UW-imapd. * Currently, there is no IPv6 support. However, prayer-session uses libc-client to connect to the IMAP server, and IPv6 support can be acheived there by building with the version of libc-client currently in experimental. * The modified UTF-7 encoding isn't supported, which means that non- ASCII characters in folder names won't work. -- Magnus Holmgren[EMAIL PROTECTED] (No Cc of list mail needed, thanks) pgpxw2jOiz3A6.pgp Description: PGP signature
Bug#352653: libdomainkeys in non-free?
On Tuesday 31 October 2006 19:42, paul cannon took the opportunity to say: > Have you considered simply putting this package in non-free? When and if > the legal questions are further resolved, transition it to main. Hmm, yes, I think so, although the naming issue has since been cleared. The biggest (only) problem is the choice of venue clause, which can be considered to make the package unsuitable for distribution - at least theoretically. -- Magnus Holmgren [EMAIL PROTECTED] [EMAIL PROTECTED] pgpDjIcMFnCXP.pgp Description: PGP signature
Bug#686448: ITA: uw-imap -- c-client library for mail protocols - development files
retitle 686448 ITA: uw-imap -- c-client library for mail protocols - development files thanks I could take this. I at least manage a package that depends on it. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#578563: Looking for a new sponsor for FriBID
On tisdagen den 11 oktober 2011, you stated the following: > My prospective sponsor won't be able to sponsor for some time. If anyone > else can offer sponsoring (or even review the packaging), please leave a > message. I just sent an annoyed message to my bank support, but I guess I should just forget about the official BankID client and look into this instead at the earliest opportunity. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#392823: RFC: ITP: prayer -- fast IMAP-based web mail system with few dependencies
I have dug even deeper in the source code of Prayer, added IPv6 support, got a reply from upstream maintainer David Carter, and thought about it. The question is: Will the (additional) effort needed to produce and maintain a Debian package of good enough quality be worth it, considering the following? 1. Prayer is geared towards large-scale, perhaps even *very* large-scale installations. It offers speed and low resource usage at the expense of flexibility. Most admins probably will want to use an Apache-based package, such as Squirrelmail. 1a. About the flexibility: Changing the appearance is rather hard and, except for some colours, requires recompilation. Prayer produces HTML4 Transitional, full of , etc. It should preferably be changed to use CSS. 2. Support for other character sets than ISO-8859-1 is non-existant. Conversion of various mail text to UTF-8 has to be added. 3. Prayer isn't prepared for l10n. All UI strings have to be gone through and wrapped in gettext calls. 4. The code is a bit messy in the sense that there are many almost-similar variants of the same functions. It would do well with some restructuring. 5. At least minimal man pages have to be written. 6. And last but not least, Prayer is practically dead upstream. David Carter says that the purpose of Prayer was to fit on top of UW-based mail systems which really weren't designed to run Webmail. Now, after 5 years, they don't need it anymore. No more releases are planned. To all this there is the problem with combined folders/directories already mentioned. Comments are welcome, especially from the original requester. How many do you think will find Prayer useful? (It's not that I want to give up, but it's a bit silly to maintain a package nobody uses.) -- Magnus Holmgren[EMAIL PROTECTED] (No Cc of list mail needed, thanks) pgpf2Y6Xyb57T.pgp Description: PGP signature
Bug#392823: RFC and preliminary RFS: prayer webmail
I have now created a working prayer package. It's not finished, but good enough to show you, fellow list subscribers. You can find it at: http://www.kibibyte.se/download/debian/ Please see the ITP at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=392823 for the full story. The source package builds two packages: prayer and, for completeness, prayer-accountd, although the latter is still pretty useless outside Cambridge. Note: the prayer binary package uses libc-client2006b from experimental, but the dependency is missing from the control file. You will probably want to build the source package, after inspecting it, anyway. > 2. Support for other character sets than ISO-8859-1 is non-existant. > Conversion of various mail text to UTF-8 has to be added. I have now addressed this as well as modified UTF-7 encoding and decoding. See README.Debian. > 5. At least minimal man pages have to be written. I have not addressed this yet. Please disregard for now. Something I've been thinking about: If two packages share a /var/(lib|run|log) subdirectory, how do you know when to remove it? I reckon that it should be removed when the last of the packages has been purged. Both packages place files there at runtime, so dpkg won't remove it since it's nonempty. But you can't just remove it in postrm if it's empty. Do you: a) leave it alone; let root delete it manually when it's no longer needed b) use dpkg -S to see if it's still in use c) use dpkg -l to see if the other package is still installed d) avoid sharing directories under /var e) do something else? Thank you for your interest! -- Magnus Holmgren[EMAIL PROTECTED] (No Cc of list mail needed, thanks) pgpKqbPPLNvXm.pgp Description: PGP signature
Bug#352533: Hijacking ITA: sa-exim
owner 352533 ! thanks All right, in reference to http://lists.debian.org/debian-devel/2006/12/msg2.html, I take over this operation now. :-) -- Magnus Holmgren[EMAIL PROTECTED] / [EMAIL PROTECTED] (No Cc of list mail needed, thanks) pgpvY4tZJZiEQ.pgp Description: PGP signature
Bug#409405: ITP: quadkonsole -- QuadKonsole embeds Konsole kparts in a grid layout.
retitle 409405 ITP: quadkonsole -- embeds Konsole kparts in a grid layout. thanks The single line synopsis should not include the name of the package or the software. See http://www.debian.org/doc/debian-policy/ch-binary.html#s-synopsis I'll help you out by changing the bug title. -- Magnus Holmgren[EMAIL PROTECTED] pgplXnAyrEPYh.pgp Description: PGP signature
Bug#410829: ITP: libdkim -- cryptographically identify the sender of email
Package: wnpp Severity: wishlist Owner: Magnus Holmgren <[EMAIL PROTECTED]> * Package name: libdkim Version : 1.0.12 Upstream Author : Alt-N Technologies <http://www.altn.com> * URL : http://libdkim.sourceforge.net/ * License : Apache 2.0 Programming Lang: C, C++ Description : cryptographically identify the sender of email DomainKeys Identified Mail (DKIM) defines a domain-level authentication framework for email using public-key cryptography and key server technology to permit verification of the source and contents of messages by either Mail Transport Agents (MTAs) or Mail User Agents (MUAs). libdkim is a C++ library which allows incorporating DKIM into an existing MTA or other application. It provides full support for signing, verifying, and SSP. It is compliant with the allman-01 set of base and ssp drafts. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#411677: ITA: nettle -- low level cryptographic library
retitle 411677 ITA: nettle -- low level cryptographic library owner 411677 Magnus Holmgren <[EMAIL PROTECTED]> thanks Yoink! I think I should be able to handle this, and I'm acquainted with upstream too. -- Magnus Holmgren[EMAIL PROTECTED], [EMAIL PROTECTED] pgpgz0bdtCP0P.pgp Description: PGP signature
Bug#373213: DomainKeys obsolete, abandoning ITPs
retitle 373213 RFP: libmail-domainkeys-perl -- Perl DomainKeys implementation noowner 373213 tags 373213 + wontfix retitle 352653 RFP: libdomainkeys -- DomainKeys reference implementation noowner 352653 tags 352653 + wontfix thanks With DomainKeys being superseded by DKIM, the licensing of libdomainkeys unclear, Etch frozen, and additionally libmail-dkim-perl including support for DomainKeys, I suggest that these two WNPP bugs be closed. -- Magnus Holmgren [EMAIL PROTECTED] / [EMAIL PROTECTED] pgpzPgPh72faj.pgp Description: PGP signature
Bug#372629: ITA/RFS: libspf2 -- Sender Policy Framework library, written in C
retitle 372629 ITA: libspf2 -- Sender Policy Framework library, written in C owner 372629 [EMAIL PROTECTED] thanks I have created a new version of libspf2 and intend to adopt it if I can find a sponsor (and/or co-maintainer). It fixes (hopefully) all outstanding bugs except one. 20_64bit_types.patch may need some testing. I hope that some DD is interested enough in SPF to take the time, and that he or she will find the package satisfactory. The dsc, for download with e.g. dget, is at ftp://ftp.kibibyte.se/debian/pool/main/libs/libspf2/libspf2_1.2.5.dfsg-1.dsc Description: Sender Policy Framework library, written in C libspf2 implements the Sender Policy Framework, a part of the SPF/SRS protocol pair. libspf2 is a library which allows email systems such as Sendmail, Postfix, Exim, Zmailer and MS Exchange to check SPF records and make sure that the email is authorized by the domain name that it is coming from. This prevents email forgery, commonly used by spammers, scammers and email viruses/worms. Homepage: http://www.libspf2.org/ License: GPL/BSD Changelog entry: * New maintainer (Closes: #372629). * Repacked .orig.tar.gz without non-free (and obsolete) IETF Internet Draft (Closes: #393390). * Merge updates from Ubuntu: - Add debian/compat and Build-depend on debhelper >= 5. - Add alternatives handling for /usr/bin/spfquery (Closes: #306875). - Conflict on libmail-spf-query-perl << 1:1.999.1-3. - Add postinst and prerm scripts. - debian/copyright: update author address. - debian/control: add final newline. * debian/control: * Change description of spfquery (Closes: #410592). * Add homepage to package descriptions. * Reduce Debian diff by changing line endings with sed instead. * Further reduce Debian diff by eliminating config.sub and config.guess from there. Build-depend on autotools-dev to ensure up-to-date versions instead. * The autogenerated spf_lib_version.h was put in the wrong directory, while there was a static spf_lib_version.h in the right directory. Fix that with some rules in debian/rules. * Use simple-patchsys.mk to manage patches. * Apply 20_64bit_types.patch to hopefully prevent segfaults on 64-bit architectures (Closes: #392793). Thanks to Thomas Jacob, Carsten Koch-Mauthe and Herbert Straub. * debian/watch: added. * Update Standards-Version to 3.7.2 without changes. * Apply 20_spf_dns_include_std_headers.patch: Include arpa/nameser.h and netdb.h from spf_dns.h instead of defining the constants needed unless certain HAVE_ macros are defined (Closes: #405885). -- Magnus Holmgren[EMAIL PROTECTED] (No Cc of list mail needed, thanks) pgpR0cnUh0QGF.pgp Description: PGP signature
Bug#372629: ITA/RFS: libspf2 -- Sender Policy Framework library, written in C
On Friday 23 March 2007 20:53, Mike Hommey wrote: > On Fri, Mar 23, 2007 at 08:23:38PM +0100, Magnus Holmgren > <[EMAIL PROTECTED]> wrote: (...) > > Have not taken a look at the package, but does the short description > > > Description: Sender Policy Framework library, written in C > > really have to say "written in C" ? Perhaps not. But it was like that when I got it. :-) Possibly it should say what it does instead of simply what SPF stands for. -- Magnus Holmgren[EMAIL PROTECTED] (No Cc of list mail needed, thanks) pgpoYH5tySF7T.pgp Description: PGP signature
Bug#504134: ITP: ssvnc -- Enhanced TightVNC viewer with SSL/SSH tunnel helper
Package: wnpp Severity: wishlist Owner: Magnus Holmgren <[EMAIL PROTECTED]> * Package name: ssvnc Version : 1.0.20 Upstream Author : Karl J. Runge <[EMAIL PROTECTED]> * URL : http://www.karlrunge.com/x11vnc/ssvnc.html * License : GPL 2 Programming Lang: C, Shell, Java Description : Enhanced TightVNC viewer with SSL/SSH tunnel helper VNC stands for Virtual Network Computing. It is, in essence, a remote display system which allows you to view a computing `desktop' environment not only on the machine where it is running, but from anywhere on the Internet and from a wide variety of machine architectures. SSVNC is two things: - An enhanced version of the TightVNC client with support for more encodings and color modes, support for x11vnc and UltraVNC extensions, dynamic screen resizing, an improved popup menu, etc. - A GUI that helps set up an SSL (using stunnel) or SSH tunnel to connect to the VNC server through, as well as forwarding of ports for audio (esound/aRts), SMB, CUPS etc. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#902280: ITP: libnet-dns-resolver-mock-perl -- Mock a DNS Resolver object for testing
Package: wnpp Severity: wishlist Owner: Magnus Holmgren * Package name: libnet-dns-resolver-mock-perl Version : 1.20171219 Upstream Author : Marc Bradshaw * URL : https://metacpan.org/pod/Net::DNS::Resolver::Mock * License : Perl Programming Lang: Perl Description : Mock a DNS Resolver object for testing A subclass of Net::DNS::Resolver which parses a zonefile for it's data source. Primarily for use in testing. Specifically used by the tests of Mail::DKIM (libmail-dkim-perl), maintained by the same author upstream.
Bug#935791: ITP: libmail-authenticationresults-perl -- object oriented Authentication-Results email headers
Package: wnpp Severity: wishlist Owner: Magnus Holmgren * Package name: libmail-authenticationresults-perl Version : 1.20180923 Upstream Author : Marc Bradshaw * URL : https://metacpan.org/release/Mail-AuthenticationResults * License : Artistic or GPL 1+ Programming Lang: Perl Description : object oriented Authentication-Results email headers This is a separate package required by Mail::DKIM 0.55 and later. See also https://bugs.debian.org/927005 and https://bugs.debian.org/927002. Description from upstream: This parser copes with most styles of Authentication-Results header seen in the wild, but is not yet fully RFC7601 compliant Differences from RFC7601 key/value pairs are parsed when present in the authserv-id section, this is against RFC but has been seen in headers added by Yahoo!. Comments added between key/value pairs will be added after them in the data structures and when stringified. It is a work in progress..
Bug#951837: netdata-go.d
Hi! I was wondering about the progress on packaging the plugins for netdata written in Go. We're interesting in using those plugins at my workplace, so I might be able to help on paid time. -- Magnus Holmgren Debian Developer
