Ubuntu
libtest-taint-perl package

libtest-taint-perl 1.06-1 source package in Ubuntu

Changelog

libtest-taint-perl (1.06-1) unstable; urgency=low


  [ Nathan Handler ]
  * debian/watch: Update to ignore development releases.

  [ Pierre Neyron ]
  * debian/copyright: Update Copyright format.

  [ Ansgar Burchardt ]
  * debian/control: Convert Vcs-* fields to Git.

  [ gregor herrmann ]
  * debian/control: update {versioned,alternative} (build) dependencies.

  [ Salvatore Bonaccorso ]
  * Change Vcs-Git to canonical URI (git://anonscm.debian.org)
  * Change search.cpan.org based URIs to metacpan.org based URIs

  [ Florian Schlichting ]
  * Import Upstream version 1.06.
  * Bump Standards-Version to 3.9.4 (update to copyright-format 1.0).
  * Switch dh compatibility to level 9 to enable passing of hardening flags.
  * Switch to source format 3.0 (quilt).
  * Switch to short-form debian/rules.
  * Add myself to uploaders and copyright.

 -- Florian Schlichting <email address hidden>  Sat, 10 Aug 2013 15:32:50 +0200

Upload details

Uploaded by:
Debian Perl Group
Uploaded to:
Sid
Original maintainer:
Debian Perl Group
Architectures:
any
Section:
perl
Urgency:
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Trusty release main perl

Downloads

File Size SHA-256 Checksum
libtest-taint-perl_1.06-1.dsc 2.1 KiB 151a1e007e55ea27b76ff3c345c89579ea28c06d8f51645c0e17760eadf9f7c2
libtest-taint-perl_1.06.orig.tar.gz 13.0 KiB 721b51ca91d248ea5ff4f99ca49c05a080e6f0fc9f7983e96121b7775ab93107
libtest-taint-perl_1.06-1.debian.tar.gz 2.1 KiB 39ddf50eb01bb76528393133003cb9827528424064f92d26c1c254732ffad4fd

No changes file available.

Binary packages built by this source

libtest-taint-perl: Module to test taintedness

 The Test::Taint module provides tools to test taintedness.
 Tainted data is data that comes from an unsafe source, such as the
 command line, or, in the case of web apps, any GET or POST transactions.
 Read the perlsec man page for details on why tainted data is bad,
 and how to untaint the data.
 .
 When you're writing unit tests for code that deals with tainted data,
 you'll want to have a way to provide tainted data for your routines to
 handle, and easy ways to check and report on the taintedness of your data,
 in standard Test::More style.