RE: key data is not secure

From: Murray S. Kucherawy <msk_at_cloudmark.com>
Date: Wed, 12 Jan 2011 15:24:58 -0800

> -----Original Message-----
> From: opendkim-users-bounce_at_lists.opendkim.org [mailto:opendkim-users-bounce_at_lists.opendkim.org] On Behalf Of Steve Jenkins
> Sent: Wednesday, January 12, 2011 3:09 PM
> To: 'Chris'
> Cc: opendkim-users_at_lists.opendkim.org
> Subject: RE: key data is not secure
>
> Murray: If you want to include an RHEL/CentOS startup script in the
> OpenDKIM 2.3 packages, I'd suggest just using v1.1 that I emailed last
> night, since 2.3 can "handle" the reload handler.

Are there Linuxes where this script won't work? If not, we could call this opendkim.linux.init.

I like Todd's idea of putting the Solaris stuff into its own directory, but I'm also wondering if we shouldn't have some topic-like structure below that, e.g.:

contrib/
  Makefile.am
  Makefile.in
  README
  convert/
    Makefile.am
    Makefile.in
    convert_keylist.sh
  init/
    Makefile.am
    Makefile.in
    opendkim.generic.init
    opendkim.linux.init
    solaris/
      Makefile.am
      Makefile.in
      (Gary's stuff here)
  rpm/
    Makefile.am
    Makefile.in
    opendkim.spec.in
  stats/
    Makefile.am
    Makefile.in
    README.opendkim-reportstats
    opendkim-reportstats

Some of those Makefiles don't do anything interesting and are only there to ensure the files in those directories are included in the package tarball when preparing a release.
Received on Wed Jan 12 2011 - 23:25:06 PST