ubuntu@ubuntu-bionic:~$ grep mkcert /etc/dovecot/conf.d/10-ssl.conf
# root. Included doc/mkcert.sh can be used to easily generate self-signed
ubuntu@ubuntu-bionic:~$ locate mkcert.sh
/usr/share/dovecot/mkcert.sh
Originally reported issue appears to be fixed now.
** Changed in: dovecot (Ubuntu)
/etc/dovecot/conf.d/10-ssl.conf, ll. 11-12: Included doc/mkcert.sh can be used
to easily generate self-signed certificate [...]
At the very least, the comment in the conf should be fixed. The way it is, I
read that, locate'd unsuccessfully, scratched my head, did a web search and...
here I am.
/etc/dovecot/conf.d/10-ssl.conf, ll. 11-12: Included doc/mkcert.sh can be used
to easily generate self-signed certificate [...]
At the very least, the comment in the conf should be fixed. The way it is, I
read that, locate'd unsuccessfully, scratched my head, did a web search and...
here I am.
I'll throw my weight behind adding mkcert.sh to the package. The
rationale is that if you google for dovecot ssl you'll be presented
with the dovecot.org wiki pages that describe using mkcert.sh. So
naturally you're going to want to try that simple approach and will fail
on Ubuntu.
Simple
I'll throw my weight behind adding mkcert.sh to the package. The
rationale is that if you google for dovecot ssl you'll be presented
with the dovecot.org wiki pages that describe using mkcert.sh. So
naturally you're going to want to try that simple approach and will fail
on Ubuntu.
Simple
** Changed in: dovecot (Ubuntu)
Importance: Medium = Wishlist
--
mkcert.sh dovecot-openssl.cnf
https://bugs.launchpad.net/bugs/59642
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in ubuntu.
--
Ubuntu-server-bugs mailing
** Changed in: dovecot (Ubuntu)
Importance: Medium = Wishlist
--
mkcert.sh dovecot-openssl.cnf
https://bugs.launchpad.net/bugs/59642
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
you asked for examples of where your argument the current solution is
adequate if not even a plus is not valid - creating certificates for
use with cacert.org. I thought you agreed to this in comment 7.
If I am mistaken, then please tell me how you think one should go about
creating and
On Mon, Aug 27, 2007 at 09:00:38AM -, Rolf Leggewie wrote:
you asked for examples of where your argument the current solution is
adequate if not even a plus is not valid - creating certificates for
use with cacert.org. I thought you agreed to this in comment 7.
You've completely lost me
There is a similar issue with apache2: See bug 77675.
One suggestion could be to add a shell script to replace mkcert.sh that
just tells the user to use the ssl-cert package. That way, all the
documentation that refers to mkcert,sh is still valid and a pointer is
given to use a better solution.
On Wed, Aug 01, 2007 at 02:58:02PM -, Rolf Leggewie wrote:
Setting to won't fix. Rationale given a few comments up.
What? How come you all of the sudden completely forgot about comment
6 and 7? Reopening.
What makes you think I forgot about them? In comment 5, I said: Unless
someone has
Setting to won't fix. Rationale given a few comments up.
What? How come you all of the sudden completely forgot about comment 6
and 7? Reopening.
** Changed in: dovecot (Ubuntu)
Assignee: Soren Hansen = (unassigned)
Status: Won't Fix = Confirmed
--
mkcert.sh dovecot-openssl.cnf
Setting to won't fix. Rationale given a few comments up.
** Changed in: dovecot (Ubuntu)
Status: Confirmed = Won't Fix
--
mkcert.sh dovecot-openssl.cnf
https://bugs.launchpad.net/bugs/59642
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
We have the ssl-cert package to provide simple SSL-certificates. It also
allows you to regenerate them easily (see the man page for make-ssl-
cert). In my opinion, providing simple means for making self-signed
certificates with custom information in it will just provide a false
sense of security.
I think I ran into this issue when trying to set up a certificate with
cacert.org (you have to create it yourself). No need to set up my own
CA for that which I think is over the top whether or not there are
howtos floating around. I am not a security expert, but I was looking
for an unobtrusive
Rolf, you are completely right. cacert.org is definitely a really good
way to go about this. I can't believe I didn't think of it.
--
mkcert.sh dovecot-openssl.cnf
https://bugs.launchpad.net/bugs/59642
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
I've copied it from fedora, it works fine.
--
mkcert.sh dovecot-openssl.cnf
https://bugs.launchpad.net/bugs/59642
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Just had the same problem. Setting to confirmed.
** Changed in: dovecot (Ubuntu)
Importance: Undecided = Medium
Status: Unconfirmed = Confirmed
--
mkcert.sh dovecot-openssl.cnf
https://bugs.launchpad.net/bugs/59642
You received this bug notification because you are a member of Ubuntu
/usr/share/doc/dovecot-common/configuration.txt.gz is also less than
optimally worded to reflect the situation. Why first say do x and
then unless you are on Debian. Well, we are on Ubuntu anyway ;-)
--
mkcert.sh dovecot-openssl.cnf
https://bugs.launchpad.net/bugs/59642
You received this bug
I have the same problem, the only difference is that I don't have
dovecot-openssl.cnf on my system, dpkg -L on
dovecot-(common|imapd|pop3d) do not show mkcert.sh and dovecot-
openssl.cnf.
This is annoying when you want to setup dovecot with SSL and there are
no means to accomplish this with the
20 matches
Mail list logo
