Your message dated Sun, 8 Apr 2018 22:14:28 +0200
with message-id <20180408201426.oncza6pxltem2...@mikejones.breakpoint.cc>
and subject line Re: Bug#895082: sendmail: Please replace 'c_rehash' with 
'openssl rehash'
has caused the Debian Bug report #895082,
regarding sendmail: Please replace 'c_rehash' with 'openssl rehash'
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 ow...@bugs.debian.org
immediately.)


-- 
895082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895082
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sendmail
Version: 8.15.2-11
Severity: normal
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: c_rehash

This package is using the c_rehash command which is part of the
openssl package. The c_rehash script is considered by upstream as a
fallback script and will disappear at some point. The recommended way
is to use the "openssl rehash" command instead which appeared in
1.1.0. Please make sure that this package does not use the c_rehash
command anymore.

The "openssl rehash" command creates half that many symlinks (one per
certificate instead of two) because it uses only the newer hash.
There is also the -compat option which creates both symlinks (and
behaves like c_rehash currently does). The hash changed from md5 to
sha1 during the 0.9.8 to 1.0.0 transition so I doubt that the
"compat" mode will be required.

Should the c_rehash script be mentioned in the source code or script
of this package but is not used during the build process or in the
final package then feel free to close the bug saying so.

Sebastian 

--- End Message ---
--- Begin Message ---
On 2018-04-08 00:56:31 [+0200], Andreas Beckmann wrote:
> The only occurrence I could find is in some documentation:

I'm sorry. I actually tried / intended to skip doc-only packages. Here I
failed.

> ./doc/op/op.me:
> ...
> A better way to do this is to use the
> .b c_rehash
> command that is part of the OpenSSL distribution
> because it handles subject hash collisions
> by incrementing the number in the suffix of the filename of the symbolic
> link,
> e.g.,
> .b \&.0
> to
> .b \&.1 ,
> and so on.
> ...
> 
> Should I change that sentence? How?

        c_rehash -> openssl rehash

but forget about it. I closed the bug. Sorry for the noise.

> Andreas

Sebastian

--- End Message ---

Reply via email to