[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app

2019-12-16 Thread Nicholas Sushkin
https://bugs.kde.org/show_bug.cgi?id=404990

--- Comment #95 from Nicholas Sushkin  ---
Google is disabling password access altogether

I got the following email yesterday:


From:   The G Suite Team 

Beginning June 15, 2020, non-Google apps that use only a password to access  
Google accounts will no longer be supported.

Starting February 15, 2021, G Suite accounts will only allow access to apps  
using OAuth. Password-based access will no longer be supported.

Dear Administrator,

We're constantly working to improve the security of your organization's  
Google accounts. As part of this effort, and in consideration of the  
current threat landscape, we'll be turning off access to less secure apps  
(LSA) — non-Google apps that can access your Google account with only a  
username and password, without requiring any additional verification steps.  
Access through only a username and password makes your account more  
vulnerable to hijacking attempts. Moving forward, only apps that support a  
more modern and secure access method called OAuth will be able to access  
your G Suite account.

Access to LSAs will be turned off in two stages:


June 15, 2020 - Users who try to connect to an LSA for the first time will  
no longer be able to do so. This includes third-party apps that allow  
password-only access to Google calendars, contacts, and email via protocols  
such as CalDAV, CardDAV and IMAP. Users who have connected to LSAs prior to  
this date will be able to continue using them until usage of all LSAs is  
turned off.
February 15, 2021 - Access to LSAs will be turned off for all G Suite  
accounts.

What do I need to do?

To continue using a specific app with your G Suite accounts, users in your  
organization must switch to a more secure type of access called OAuth. This  
connection method allows apps to access accounts with a digital key instead  
of requiring a user to reveal their username and password. We recommend  
that you share the user instructions (included below) with individuals in  
your organization to help them make the necessary changes. Alternatively,  
if your organization is using custom tools, you can ask the developer of  
the tool to update it to use OAuth. Developer instructions are also  
included below.

MDM configuration

If your organization uses a mobile device management (MDM) provider to  
configure CalDAV, CardDAV, and Exchange ActiveSync (Google Sync) profiles,  
these services will be phased out according to the timeline below:


June 15, 2020 - MDM push of IMAP, CalDAV, CardDAV, and Exchange ActiveSync  
(Google Sync) will no longer work for new users.
February 15, 2021 - MDM push of IMAP, CalDAV, CardDAV, and Exchange  
ActiveSync (Google Sync) will no longer work for existing users. Admins  
will need to push a Google Account using their MDM provider, which will  
re-add their Google accounts to iOS devices using OAuth.

Other less secure apps


For any other LSA, ask the developer of the app you are using to start  
supporting OAuth.
If you use other apps on iOS or MacOS that access your G Suite account  
information through only a password, most access issues can be resolved by  
removing then re-adding your account. When you add it back, make sure to  
select Google as the account type to automatically use OAuth.

Scanners and other devices

No change is required for scanners or other devices using simple mail  
transfer protocol (SMTP) or LSAs to send emails. If you replace your  
device, look for one that sends email using OAuth.

User instructions

If you are using an app that accesses your Google account with only a  
username and password, take one of the following actions to switch to a  
more secure method and continue to access your email, calendar, or  
contacts. If you do not take one of the following actions, when LSA access  
is discontinued after February 15, 2021, you will begin receiving an error  
message that your username-password combination is incorrect.

Email


If you are using stand-alone Outlook 2016 or earlier, move to Office 365 (a  
web-based version of Outlook) or Outlook 2019, both of which support OAuth  
access. Alternatively you can use G Suite Sync for Microsoft Outlook.
If you are using Thunderbird or another email client, re-add your Google  
Account and configure it to use IMAP with OAuth.
If you are using the mail app on iOS or MacOS, or Outlook for Mac, and use  
only a password to login, you'll need to remove and re-add your account.  
When you add it back, select “sign in with Google” to automatically use  
OAuth.


Mac OS iOS


mail app view Mac OS

mail app view iOS



Calendar


If you use CalDAV to give an app or device access to your calendar, switch  
to a method that supports OAuth. We recommend the Google Calendar app  
[Web/iOS/Android] as the most secure app to use with your G Suite account.
If your G Suite account is linked to the calendar app in iOS or MacOS and  
use

[kopete] [Bug 411392] New: In Kopete 1.13 "View History" action is gone from menu and toolbars

2019-08-28 Thread Nicholas Sushkin
https://bugs.kde.org/show_bug.cgi?id=411392

Bug ID: 411392
   Summary: In Kopete 1.13 "View History" action is gone from menu
and toolbars
   Product: kopete
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: History Plugin
  Assignee: kopete-bugs-n...@kde.org
  Reporter: nsush...@sushkins.net
  Target Milestone: ---

SUMMARY
After upgrading to Kopete 1.13, "View History" menu has disappeared. I can
still view history via keyboard shortcut Ctrl-H, but the action is not
available in any toolbar or menu and does not appear in "Available actions" in
Configure Toolbars. Kopete Handbook specifies that View History should be in
the Edit menu

STEPS TO REPRODUCE
1. In Settings/Configure, Plugins, enable History plugin
2. Click Edit menu, list menu items
3. Click Settings/Configure Toolbars 
4. Browser "Available actions:" list, there is no "View History" action

OBSERVED RESULT
In Edit menu there is no "View History" menu item
In "Available actions", there is no "View History" action

EXPECTED RESULT
In Edit menu there should be "View History" menu item
In "Available actions", there should be "View History" action


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Kubuntu 19.04
(available in About System)
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2

ADDITIONAL INFORMATION
Operating System: Kubuntu 19.04
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2
Kernel Version: 5.0.0-25-generic
OS Type: 64-bit
Processors: 2 × Intel® Core™ i7-3520M CPU @ 2.90GHz
Memory: 9.8 GiB of RAM

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app

2019-08-20 Thread Nicholas Sushkin
https://bugs.kde.org/show_bug.cgi?id=404990

Nicholas Sushkin  changed:

   What|Removed |Added

 CC||nsush...@sushkins.net

--- Comment #53 from Nicholas Sushkin  ---
(In reply to Daniel Vrátil from comment #50)
> I've now did the necessary changes and filed a request to have the login
> enabled again.

Hi, Daniel,

Are you expecting that Google will notify when your request has been processed?

I am still seeing "Sign in with Google temporarily disabled for this app" when
Akonadi is trying to log into my MFA enabled GMail account.

Thanks

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 396850] Incorrect RFC822 timezone parsing in mail Date field

2018-07-25 Thread Nicholas Sushkin
https://bugs.kde.org/show_bug.cgi?id=396850

--- Comment #1 from Nicholas Sushkin  ---
Created attachment 114119
  --> https://bugs.kde.org/attachment.cgi?id=114119&action=edit
email message whose date is displaying incorrectly

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 396850] New: Incorrect RFC822 timezone parsing in mail Date field

2018-07-25 Thread Nicholas Sushkin
https://bugs.kde.org/show_bug.cgi?id=396850

Bug ID: 396850
   Summary: Incorrect RFC822 timezone parsing in mail Date field
   Product: kmail2
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: message list
  Assignee: kdepim-b...@kde.org
  Reporter: nsush...@sushkins.net
  Target Milestone: ---

I received an email with Date header in the following format:

Date: Wed, 25 Jul 2018 10:55:49 CDT

In message list and message view, the email date is displayed as 6:55 AM. I am
in in US Eastern time zone. The proper date in EDT is 11:55 AM.

I looked at all other messages whose date is displayed correctly and their date
header has timezone in ("+" / "-") 4DIGIT format. Is it possible kmail2 has
parsing issues with timezone specified as CDT? After all, "Wed, 25 Jul 2018
10:55:49 +" is 6:55AM EDT.

RFC 822 allows CDT as a time zone, see
https://tools.ietf.org/html/rfc822#section-5.1


This is Ubuntu 16.04.5 LTS, KMail 5.1.3

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 375186] Add Clip: Clip is invalid

2017-02-12 Thread Nicholas Sushkin
https://bugs.kde.org/show_bug.cgi?id=375186

Nicholas Sushkin  changed:

   What|Removed |Added

 CC|nsush...@sushkins.net   |

--- Comment #2 from Nicholas Sushkin  ---
A reboot fixed the issue for me.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 375186] Add Clip: Clip is invalid

2017-02-10 Thread Nicholas Sushkin
https://bugs.kde.org/show_bug.cgi?id=375186

Nicholas Sushkin  changed:

   What|Removed |Added

 CC||nsush...@sushkins.net

-- 
You are receiving this mail because:
You are watching all bug changes.