Hello,

The package figure in the repository of Kali distribution.
I don’t think that Debian security need it.


Regards,

On Mon, Aug 3, 2020 at 21:45 Alejo Marín <jamari...@gmail.com> wrote:

> Package: sponsorship-requests
> Severity: normal
>
> Dear mentors,
>
> I am looking for a sponsor for my package "sslscan":
>
>  * Package name    : sslscan
>    Version         : 2.0.0-1
>    Upstream Author : rbsec <ro...@rbsec.net>
>  * URL             : https://github.com/rbsec/sslscan
>  * License         : GPL-3.0+ with OpenSSL exception
>  * Vcs             : [fill in URL of packaging vcs]
>    Section         : utils
>
> It builds those binary packages:
>
>   sslscan - Fast SSL scanner
>
> To access further information about this package, please visit the following 
> URL:
>
>   https://mentors.debian.net/package/sslscan/
>
> Alternatively, one can download the package with dget using this command:
>
>   dget -x 
> https://mentors.debian.net/debian/pool/main/s/sslscan/sslscan_2.0.0-1.dsc
>
> Changes since the last upload:
>
>  sslscan (2.0.0-1) unstable; urgency=medium
>  .
>    * New upstream release.
>    * New maintainer. (Closes: #952385)
>    * Update debian/watch.
>    * Remove debian/compat.
>    * debian/rules
>      + Remove override_dh_auto_install.
>      + add override_dh_auto_build.
>      + Remove innecesary "--parallel" from "dh $@".
>    * debian/control
>      + Update Standard-Version to 4.5.0.
>      + Set myself as Maintainer.
>      + debhelper bump level to 13.
>      + Update priority to optional.
>      + Mark Rules-Requires-Root: no as we don't need root for building.
>    * debian/copyright
>      + Update my email address.
>      + Extend debian copyright holder years.
>      + Update Upstream-Contact.
>      + Update License to GPL-3.0+.
>      + Update description license.
>    * debian/upstream/metadata
>      + Add Bug-Database and Bug-Submit fields.
>    * debian/patches
>      + Add 01_spelling_sslscanc.diff patch.
>
> Regards,
> --*Jhon Alejandro Marín Rodríguez - *jamarin90
>
>
>

Reply via email to