1.09.2014

using gmail smtp with redmine 2.4.1

It took me forever to get redmine emails working with gmail's smtp server.  After perusing the ruby action mailer website, I set up my redmine configuration.yml to look like this:

# default configuration options for all environments

default:
  # Outgoing emails configuration (see examples above)
  email_delivery:
    delivery_method: :smtp
    smtp_settings:
      address: 'smtp.gmail.com'
      port: 587
      domain: 'pickemupproductions.com'
      user_name: 'redmine@pickemupproductions.com'
      password: '****'
      authentication: 'plain'
      enable_starttls_auto: true

obviously replace password with your actual password.  Also, I'm using google apps with my wife's business domain.  So my username and domain are a bit differnet than what you would use for regular gmail (gmail.com).

1.03.2014

Installing new CA certs on ubuntu for chrome or firefox

I recently needed to install a new CA cert into my ubuntu VM.  There are lots of tutorials out there that show how to use

sudo dpkg-reconfigure ca-certificates

This is all well and good if you want to install the CA into the global openssl store for things like git, wget, and apt.  However, if you want Chrome or Firefox to be able to trust the new CA, you need to install the CA cert into the NSS database.  (?!).

This SO article saved me about a day of frustration and sadly I don't have enough rep to upvote Johann's answer:

http://superuser.com/questions/437330/how-do-you-add-a-certificate-authority-ca-to-ubuntu/657177#657177?newreg=ad85846ee69249969b698b48bda371c3

Basically, you need to download the NSS client tools and use them to install the CA (the same one you put in openssl's store) into the backend NSS.  Chromium has the process documented here:

https://code.google.com/p/chromium/wiki/LinuxCertManagement

To install a new cert using the NSS client tools, do this:

certutil -d sql:$HOME/.pki/nssdb -A -t "C,," -n <certificate nickname> -i <certificate filename>

<certificate nickname> can be anything.  <certificate filename> is the full path to your PEM file (*.crt or *.cer).