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

Bug#986830: marked as done (ITP: sscg -- simple SSL certificate generator)

Your message dated Mon, 23 Aug 2021 12:05:38 +0200
with message-id <YSNy8vgkNaPVbTZC@piware.de>
and subject line Re: Bug#986830: ITP: sscg -- simple SSL certificate generator
has caused the Debian Bug report #986830,
regarding ITP: sscg -- simple SSL certificate generator
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
986830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986830
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist
Owner: Martin Pitt <mpitt@debian.org>

* Package name    : sscg
  Version         : 2.6.2
  Upstream Author : Stephen Gallagher <sgallagh@redhat.com>
* URL             : https://github.com/sgallagher/sscg/
* License         : GPL-3+ with OpenSSL exception
  Description     :
   sscg is a utility to aid in the creation of more secure "self-signed"
   certificates. The certificates created by this tool are generated in a
   way so as to create a CA certificate that can be safely imported into a
   client machine to trust the service certificate without needing to set
   up a full PKI environment and without exposing the machine to a risk of
   false signatures from the service certificate.

See this blog post for details:
https://sgallagh.wordpress.com/2016/05/02/self-signed-ssltls-certificates-why-they-are-terrible-and-a-better-alternative/

Cockpit's web server makes use of sscg if it is available, as a slightly better
alternative than direct self-signed certificates.

CC'ing upstream author Stephen for questions about the functionality.

I recently sent the Debian packaging to the upstream project, where it will run
in CI for each PR: https://github.com/sgallagher/sscg/pull/22

Thanks,

Martin

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Version: 3.0.0-2

Martin Pitt [2021-04-20 14:01 +0200]:
> Control: tag -1 pending
> 
> Martin Pitt [2021-04-12 16:23 +0200]:
> > * Package name    : sscg
> 
> I packaged this at https://salsa.debian.org/debian/sscg and uploaded to
> experimental. It's in the NEW queue now:
> https://ftp-master.debian.org/new/sscg_2.6.2-1.html

This took one more round, 3.0.0-1 got accepted into experimental yesterday [1],
and I uploaded it into unstable now [2]. Unfortunately I forgot to use -v, so
closing this bug manually.

Martin

[1] https://tracker.debian.org/news/1249886/accepted-sscg-300-1-source-amd64-into-experimental-experimental/
[2] https://tracker.debian.org/news/1250666/accepted-sscg-300-2-source-into-unstable/

--- End Message ---
Reply to: