[Akonadi] [Bug 423406] /usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_X put my cpu at 100%

2020-06-24 Thread David Jarvie
https://bugs.kde.org/show_bug.cgi?id=423406

--- Comment #1 from David Jarvie  ---
Did a single akonadi_kalarm_resource process use 100% CPU? If so, the stack
trace doesn't help to find out why, since it gives no indication of where in
the KAlarmResource it is hogging the CPU.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[kmail2] [Bug 423367] Subject and sender field interpret formatting characters

2020-06-24 Thread Frank Steinmetzger
https://bugs.kde.org/show_bug.cgi?id=423367

--- Comment #3 from Frank Steinmetzger  ---
Due to your question I looked at the mail in detail, especially once I noticed
that it also appears in the Breeze window title.

There are no actual underscores, but it is a typical unicode „attack“. I pasted
the text into vim to use its unicode character query. It tells me they are a
combination of the normal character plus ' ̲' U+0332 Dec:818 COMBINING LOW LINE

So I’m afraid this makes this bug report invalid. :-T

For completeness, I attach the mail anyway.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 423367] Subject and sender field interpret formatting characters

2020-06-24 Thread Frank Steinmetzger
https://bugs.kde.org/show_bug.cgi?id=423367

--- Comment #2 from Frank Steinmetzger  ---
Created attachment 129641
  --> https://bugs.kde.org/attachment.cgi?id=129641=edit
mbox of the mail

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 423246] Obvious phishing URLs are not recognized

2020-06-24 Thread David Hurka
https://bugs.kde.org/show_bug.cgi?id=423246

--- Comment #4 from David Hurka  ---
I was thinking that usually URLs are written in their ascii form. If you send a
link which is intended to have a non-ascii domain, it will be marked as
phishing. Every domain that is actually like höhö.com will be a false positive,
but I think these are rare.

Of course my idea is to check only the domain name, not the whole URL.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 423426] POP3 setup wizard defaults to unencrypted connections.

2020-06-24 Thread Damian Poddebniak
https://bugs.kde.org/show_bug.cgi?id=423426

--- Comment #2 from Damian Poddebniak <93s4m32gd2ab8...@mailbox.org> ---
Related: https://bugs.kde.org/show_bug.cgi?id=389427 (but for IMAP)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 423246] Obvious phishing URLs are not recognized

2020-06-24 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=423246

--- Comment #3 from Laurent Montel  ---
"What do you mean with false results?" if we check each char to compare to no
ascii it will signal all utf8 url even if it's not a phishing link.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 423426] POP3 setup wizard defaults to unencrypted connections.

2020-06-24 Thread Damian Poddebniak
https://bugs.kde.org/show_bug.cgi?id=423426

--- Comment #1 from Damian Poddebniak <93s4m32gd2ab8...@mailbox.org> ---
This is also related to https://bugs.kde.org/show_bug.cgi?id=423423 as the POP3
setup will not set "Server requires authentication" per default.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 423426] New: POP3 setup wizard defaults to unencrypted connections.

2020-06-24 Thread Damian Poddebniak
https://bugs.kde.org/show_bug.cgi?id=423426

Bug ID: 423426
   Summary: POP3 setup wizard defaults to unencrypted connections.
   Product: kmail2
   Version: 5.13.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: 93s4m32gd2ab8...@mailbox.org
  Target Milestone: ---

The setup wizard in kmail defaults to unencrypted connections. When the user
clicks on "Check Mail" after the setup, the username and password are sent in
the clear. I have not found a way to tell kmail in the manual configuration to
use implicit TLS or STARTTLS. 

What is even worse: assuming you know about that and try to configure STARTTLS
directly after the setup. In this case it happens that future connections still
happen unencrypted, even though the UI tells otherwise. I clicked on "Restart"
in the UI several times and also restarted Akonadi and KMail. In this case, I
found that POP3 was once even reset back to "Unencrypted". After few more tries
it seems to have settled down to use STARTTLS.

I am using NixOS with kmail2 5.13.3 (19.12.3).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 423424] Kmail "forces" the user to accept invalid TLS certificates.

2020-06-24 Thread Damian Poddebniak
https://bugs.kde.org/show_bug.cgi?id=423424

--- Comment #1 from Damian Poddebniak <93s4m32gd2ab8...@mailbox.org> ---
This also applies in a limited form (dialogs show up slower) for SMTP.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 423424] New: Kmail "forces" the user to accept invalid TLS certificates.

2020-06-24 Thread Damian Poddebniak
https://bugs.kde.org/show_bug.cgi?id=423424

Bug ID: 423424
   Summary: Kmail "forces" the user to accept invalid TLS
certificates.
   Product: kmail2
   Version: 5.13.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: 93s4m32gd2ab8...@mailbox.org
  Target Milestone: ---

When the IMAP TLS certificate is bad, i.e. self-signed, kmail shows a warning
with three buttons: "Details", "Continue" and "Cancel". When the user clicks on
"Cancel", kmail repeats the login process and shows the warning again
immediately. This process continues in a loop, which can not be canceled by the
user when clicking on "Cancel" (the only secure option).

The only way to "escape" from this loop is to click on "Continue.", which might
reveal the username and password.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 423423] New: STARTTLS is ignored when "Server requires authentication" not checked in UI

2020-06-24 Thread Damian Poddebniak
https://bugs.kde.org/show_bug.cgi?id=423423

Bug ID: 423423
   Summary: STARTTLS is ignored when "Server requires
authentication" not checked in UI
   Product: kmail2
   Version: 5.13.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: 93s4m32gd2ab8...@mailbox.org
  Target Milestone: ---

The STARTTLS option of SMTP is ignored, when "Server requires authentication"
is not checked. In this case kmail will send any mail in cleartext.

Tested with kmail2 5.13.3 (19.12.3).

-- 
You are receiving this mail because:
You are the assignee for the bug.