Am 31.01.19 um 23:33 schrieb Andrea Pescetti: > On 30/01/2019 Peter Kovacs wrote: >> AFAIK Root cause is that the TLS connection can not be established in >> Version 1.2 due to wrong version on client side. >> The Idea has been to lower security on server back to 1.1 Version for >> now. > > I confirm this is the conclusion we reached, but then we (at least I) > haven't find the time for following up properly. > > Thank you Pedro for the reminder, let's see if time allows for taking > action (server-side) on this soon! But I think there is no code bug to > address in this respect.
In the past month I had about 2 weeks where AOO 4.1.6 on Ubuntu 16.04 had a working connection to the update server. Now it is gone again... :-( So it is clearly no problem in our code in the first place. Also the download statistics show me that a great number of users (from OOo 3.2 to AOO 4.1.5) have gotten the update notification and did update via this channel. > For sure not for 4.2.0-beta where updates would be disabled anyway. I really see no reason for that... At least this was only a suggestion from Marcus and hasn't been discussed further. At the moment Beta builds for 4.2.0 point to https://ooo-updates.apache.org/aoonextbeta/check.Update. This is an empty feed just enough to respond "OpenOffice Beta 4.2.0 is up to date." and it is already working. [1] Regards, Matthias [1] https://home.apache.org/~mseidel/AOO%204.2.0%20Beta%20Update%20feed.png > > Regards, > Andrea. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org >
smime.p7s
Description: S/MIME Cryptographic Signature
