linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: linux-media@vger.kernel.org
Subject: Re: [ANN] possible LinuxTV.org maintenance on Wednesday (2019-11-20)
Date: Wed, 20 Nov 2019 16:58:08 +0100	[thread overview]
Message-ID: <20191120165808.54ac4b32@infradead.org> (raw)
In-Reply-To: <20191120114131.4000bb1b@infradead.org>

Em Wed, 20 Nov 2019 11:41:31 +0100
Mauro Carvalho Chehab <mchehab@infradead.org> escreveu:

> Em Mon, 18 Nov 2019 11:13:23 +0100
> Mauro Carvalho Chehab <mchehab@infradead.org> escreveu:
> 
> > Hi all,
> > 
> > Just to let you know, we'll be doing a preventive maintenance tomorrow by
> > 1pm-3pm (UTC). 
> > 
> > During that time, we'll be stopping the services (wiki, web, patchwork, git)
> > at *.linuxtv.org.  
> 
> It ends that the upgrade didn't happen yesterday. So, we are trying to
> re-schedule it for today.
> 
> In principle, the maintenance will happen between 1pm-3pm (UTC).

The Maintenance activity is almost finished. 

Developers with git trees hosted at linuxtv.org:

Please notice that we're now using a newer sshd version, with a different
server key.

If you experience troubles while cloning/pushing using SSH, then perhaps
your key is too old and the cryptography algorithm is now considered
unsafe. That applies, for example, for DSS keys:

	https://www.gentoo.org/support/news-items/2015-08-13-openssh-weak-keys.html

If you're using such keys, please re-generate your keys using the current
last practices, and re-send your new public key to me in private.

Thanks


Cheers,
Mauro

      reply	other threads:[~2019-11-20 15:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-18 10:13 [ANN] LinuxTV.org maintenance on Tuesday (2019-11-19) Mauro Carvalho Chehab
2019-11-19  9:57 ` Johannes Stezenbach
2019-11-20 10:41 ` [ANN] possible LinuxTV.org maintenance on Wednesday (2019-11-20) Mauro Carvalho Chehab
2019-11-20 15:58   ` Mauro Carvalho Chehab [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191120165808.54ac4b32@infradead.org \
    --to=mchehab@infradead.org \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).