Re: Email address to be used when requesting SSL cert?

On Wed, 8 Jan 2020 at 01:34, Sam Ruby wrote: > On Tue, Jan 7, 2020 at 8:26 PM sebb wrote: > > > > What email address should be used when requesting an SSL cert as per > > DEPLOYMENT.md? > > > > Would private@whimsical.a.o be suitable? > > Yes. That's what I used last time. See: > > Just tried

Re: Email address to be used when requesting SSL cert?

On Tue, Jan 7, 2020 at 8:26 PM sebb wrote: > > What email address should be used when requesting an SSL cert as per > DEPLOYMENT.md? > > Would private@whimsical.a.o be suitable? Yes. That's what I used last time. See: /etc/letsencrypt/accounts/acme-v01.api.letsencrypt.org/directory/902441c9c01

Email address to be used when requesting SSL cert?

What email address should be used when requesting an SSL cert as per DEPLOYMENT.md? Would private@whimsical.a.o be suitable? Sebb

Re: mail not working on whimsy-vm5

Mail can now be received. The class postfix::server is needed in the main YAML file. It looks like this was included by default in the ubuntu parent files in previous version of Puppet. Sending email to @a.o addresses half works - it's rejected by the mail relay server. AFAICT this is defined in d

SHA-1 security issues, GPG update mitigation

https://sha-mbles.github.io/ Simply put, SHA-1 is about as insecure as MD5. GPG 2.2.18 contains a fix for this to ignore SHA-1-based identity signatures for keys created after 19 Jan 2019. I'm not sure if we have a link to documentation for users about proper use of GPG/PGP, though it might be ha

Re: mail not working on whimsy-vm5

On Tue, 7 Jan 2020 at 13:38, Sam Ruby wrote: > Not sure that this is the answer, but by default mail sent from within > the infrastructure can only go to @apache.org email addresses. The > infrastructure team has to make some change to allow whimsy to send > email to other addresses. > > It does

Re: Migrate to whimsy-vm5?

On Tue, Jan 7, 2020 at 3:47 AM sebb wrote: > > On Tue, 7 Jan 2020 at 02:01, Sam Ruby wrote: > > > On Mon, Jan 6, 2020 at 1:48 PM sebb wrote: > > > > > > On Mon, 6 Jan 2020 at 18:32, Sam Ruby wrote: > > > > > > > On Mon, Jan 6, 2020 at 8:21 AM sebb wrote: > > > > > > > > > > Do we want to start

Re: mail not working on whimsy-vm5

Not sure that this is the answer, but by default mail sent from within the infrastructure can only go to @apache.org email addresses. The infrastructure team has to make some change to allow whimsy to send email to other addresses. - Sam Ruby On Tue, Jan 7, 2020 at 6:38 AM sebb wrote: > > Not s

Re: Puppet bootstrap issue?

Ignore this. bundler would have been installed by rvm (currently commented out) I've added it as a separate package. rake update does not need wunderbar. On Tue, 7 Jan 2020 at 11:36, sebb wrote: > whimsy-vm5 does not currently have bundler installed (it has rake) > This is needed for rake upda

Re: mail not working on whimsy-vm5

It looks like postfix is not running, but I cannot work out what is supposed to start it On Tue, 7 Jan 2020 at 11:37, sebb wrote: > Not sure why, but inbound and outbound mail are not working on whimsy-vm5. > > Any ideas? >

mail not working on whimsy-vm5

Not sure why, but inbound and outbound mail are not working on whimsy-vm5. Any ideas?

Puppet bootstrap issue?

whimsy-vm5 does not currently have bundler installed (it has rake) This is needed for rake update. Nor does it have wunderbar, which I think is also needed for rake update. Maybe these need to be added as package (provider: gem) items? Sebb.

Re: Migrate to whimsy-vm5?

On Tue, 7 Jan 2020 at 02:01, Sam Ruby wrote: > On Mon, Jan 6, 2020 at 1:48 PM sebb wrote: > > > > On Mon, 6 Jan 2020 at 18:32, Sam Ruby wrote: > > > > > On Mon, Jan 6, 2020 at 8:21 AM sebb wrote: > > > > > > > > Do we want to start the process of migrating to whimsy-vm5? > > > > > > Setup need