Re: Planning the removal of c_rehash | mass bug filling

On 2018-04-25 15:44:33 [-0700], Brian Murray wrote: > I thought it was worth mentioning that the behavior of 'openssl rehash' > when encountering a duplicate certificate was to return 1 while > 'c_rehash' would return 0. I say was because I filed an upstream bug[1] > about it which was resolved. >

Planning the removal of c_rehash | mass bug filling

> Hi, > > the openssl package provides the c_rehash script which creates the links > from .Y to the actual certificate in /etc/ssl/certs/. During the > transition from 0.9.8 to 1.0.0 the hash (for the X part) changed from > md5 to sha1. Since that transition in Debian the c_rehash script

Re: Planning the removal of c_rehash | mass bug filling

On 04/09/2018 05:34 PM, Sebastian Andrzej Siewior wrote: > On 2018-04-09 15:55:14 [-0500], Michael Shuler wrote: >> It was purely a conservative duplication of existing symlinks. I can >> drop the old md5 symlinks, if there's a consensus that they are no >> longer needed in unstable. > > Based

Re: Planning the removal of c_rehash | mass bug filling

On 2018-04-09 15:55:14 [-0500], Michael Shuler wrote: > It was purely a conservative duplication of existing symlinks. I can > drop the old md5 symlinks, if there's a consensus that they are no > longer needed in unstable. Based on my research I think you can drop the old links since they were

Re: Planning the removal of c_rehash | mass bug filling

On 04/09/2018 03:21 PM, Sebastian Andrzej Siewior wrote: > On 2018-04-06 10:05:35 [-0500], Michael Shuler wrote: >> If you could go ahead and file this bug for ca-certificates, I'd like to >> include the bug number in the changelog for this commit on the next >> upload, which should be soon. >> >>

Re: Planning the removal of c_rehash | mass bug filling

On 2018-04-06 10:05:35 [-0500], Michael Shuler wrote: > If you could go ahead and file this bug for ca-certificates, I'd like to > include the bug number in the changelog for this commit on the next > upload, which should be soon. > >

Re: Planning the removal of c_rehash | mass bug filling

On Fri, Apr 06, 2018 at 12:22:12AM +0200, Sebastian Andrzej Siewior wrote: > Hi, > > the openssl package provides the c_rehash script which creates the links > from .Y to the actual certificate in /etc/ssl/certs/. During the > transition from 0.9.8 to 1.0.0 the hash (for the X part)

Re: Planning the removal of c_rehash | mass bug filling

On 04/05/2018 05:22 PM, Sebastian Andrzej Siewior wrote: > Hi, > > the openssl package provides the c_rehash script which creates the links > from .Y to the actual certificate in /etc/ssl/certs/. During the > transition from 0.9.8 to 1.0.0 the hash (for the X part) changed from > md5 to

Re: Planning the removal of c_rehash | mass bug filling

On Fri, Apr 06, 2018 at 12:22:12AM +0200, Sebastian Andrzej Siewior wrote: > Hi, > > the openssl package provides the c_rehash script which creates the links > from .Y to the actual certificate in /etc/ssl/certs/. During the > transition from 0.9.8 to 1.0.0 the hash (for the X part)

Re: Planning the removal of c_rehash | mass bug filling

On 5 April 2018 at 23:22, Sebastian Andrzej Siewior wrote: > > Hi, > > the openssl package provides the c_rehash script which creates the links > from .Y to the actual certificate in /etc/ssl/certs/. During the > transition from 0.9.8 to 1.0.0 the hash (for the X

Planning the removal of c_rehash | mass bug filling

Hi, the openssl package provides the c_rehash script which creates the links from .Y to the actual certificate in /etc/ssl/certs/. During the transition from 0.9.8 to 1.0.0 the hash (for the X part) changed from md5 to sha1. Since that transition in Debian the c_rehash script provides