[Expired for evolution (Ubuntu) because there has been no activity for
60 days.]
** Changed in: evolution (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.
[Expired for gnome-online-accounts (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: gnome-online-accounts (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution
[Expired for gnutls28 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gnutls28 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.la
The issue there seems to be with the servers not up to current standard
and what gnutls enforce, is there anything that needs to be done from
the online accounts or evolution?
** Changed in: gnome-online-accounts (Ubuntu)
Importance: Undecided => Low
** Changed in: evolution (Ubuntu)
Import
This worked for me! Thank you.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1860461
Title:
libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client
with error "Erro
Oops, it should have been LOW, not LEGACY. Here it is again to avoid any
confusion:
As a workaround, can you try lowering the profile from MEDIUM [1] to LOW
[2]:
sudo mkdir /etc/gnutls
cat << EOF | sudo tee -a /etc/gnutls/config
[overrides]
default-priority-string =
NORMAL:-VERS-ALL:+VERS-TLS1.3
As a workaround, can you try lowering the profile from MEDIUM [1] to
LEGACY:
sudo mkdir /etc/gnutls
cat << EOF | sudo tee -a /etc/gnutls/config
[overrides]
default-priority-string =
NORMAL:-VERS-ALL:+VERS-TLS1.3:+VERS-TLS1.2:+VERS-DTLS1.2:%PROFILE_LEGACY
EOF
1:
https://git.launchpad.net/ubuntu/
** This bug is no longer a duplicate of bug 1872778
update-crypto-policies not affecting Gnome Online Accounts
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1860461
Title:
li
*** This bug is a duplicate of bug 1872778 ***
https://bugs.launchpad.net/bugs/1872778
** This bug has been marked a duplicate of bug 1872778
update-crypto-policies not affecting Gnome Online Accounts
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, w
Sorry for pushing on this yet again, but since using the LEGACY setting
does not resolve the issue, could the real bug possibly be that Online
Accounts are not respecting that setting (which would be a big deal)?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bug
I have the same problem with my company's email which uses the Rackspace
Outlook 2016 Exchange service. Rackspace told me that they cannot change
the DH key to a value higher than 1024 bits (which I don't believe) and
they suggested that instead the company upgrades to some Office 365
service which
Thank you for the testing link.
https://www.ssllabs.com/ssltest/analyze.html?d=shibboleth.nyu.edu&hideResults=on
This server supports weak Diffie-Hellman (DH) key exchange parameters.
This server does not support Forward Secrecy with the reference browsers.
This server supports TLS 1.0 and TLS 1.
My University Account (NYU) uses Shibboleth. I was able to add that
account to Online Accounts in 19.10 but it fails with this error in
20.04.
Are you saying that the minimal level of crypto changed between 19.10
and 20.04?
--
You received this bug notification because you are a member of Ubuntu
There is no easy way to gracefully handle weak crypto. It has been known
for more than five years that 1024 bit (or rather <2048 bit) DH primes
need to be considered weak and should not be used - https://weakdh.org/
- GnuTLS > 3.2 does the right thing in having services which still have
not taken a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: evolution (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-online-accounts (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.laun
** Also affects: gnome-online-accounts (Ubuntu)
Importance: Undecided
Status: New
** Also affects: evolution (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in U
17 matches
Mail list logo