[Akonadi] [Bug 406505] one problem (refused login) result in duzends of identical info dialogs that grab focus
https://bugs.kde.org/show_bug.cgi?id=406505 --- Comment #1 from Achim Bohnet --- Created attachment 119402 --> https://bugs.kde.org/attachment.cgi?id=119402=edit picture of the duzends akonadi dialogs -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 406505] New: one problem (refused login) result in duzends of identical info dialogs that grab focus
https://bugs.kde.org/show_bug.cgi?id=406505 Bug ID: 406505 Summary: one problem (refused login) result in duzends of identical info dialogs that grab focus Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: IMAP resource Assignee: kdepim-bugs@kde.org Reporter: a...@mpe.mpg.de Target Milestone: --- akonadi 5.10.3 (version listed in bugzilla) SUMMARY: unfortunately due to massive problems with akonadi in the last weeks (multiple merge candidate, several sync of same collection ~ 30 sec) I had to fallback to use thunderbird someties -> ~ doubling the # of IMAP collections. This triggers akonadi 'Informational' dialog: ... A02 NO Maximum number of connections from user+IP exceeded ( mail_max_userip_connections=10 ) [ UNAVAILABLE ] STEPS TO REPRODUCE 1. start several akonadi sessions/thunderbirds/macmail... in parallel (laptop, desktop, vbox ...) 2. when 'N' the max # of imap connection on the imap server is reached: 3. duzends of informational akonadi dialogs appear that grap focus OBSERVED RESULT * a new dialog appear (every few seconds a new one). I had 23 of them * they needlessly grab be focus -> e.g. kicker and krunner are closed * After ~ 15 min the latest dialog starts to grab the focus as soon another window is aktivated. (only workaround is to close all the dialogs) EXPECTED RESULT * Only one dialog instead of a two duzend dialogs. * As it's only informational there no need to grab the focus * prefered would be one standard Plasma notification instead of a dialog window SOFTWARE/OS VERSIONS: Linux/KDE Plasma: kde neon user (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks 5.56.0 Qt 5.12.0 (kompiliert gegen 5.12.0) Das xcb Fenstersystem -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 404698] Decryption Oracle based on replying to PGP or S/MIME encrypted emails
https://bugs.kde.org/show_bug.cgi?id=404698 --- Comment #7 from Jens Mueller --- Exactly that's the problem. Note that not only one message, but hundreds of captured messages can be wrapped and leaked with one single reply. Traditional message takeover attacks under a new identity (C) are considered as an acceptable risk in email e2e encryption because it is assumed that given the context of the message (e.g.,“Hi A, [...] Yours, B”) B can tell that this message is not originally from C and could easily discover the deception. However, using MIME wrapping, C can make a different content being displayed to B (if B does not carefully scroll down the whole message conversation) and therefore potentially trick B into replying to C. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 404698] Decryption Oracle based on replying to PGP or S/MIME encrypted emails
https://bugs.kde.org/show_bug.cgi?id=404698 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #6 from Albert Astals Cid --- I am not sure I understand where the problem is, potentially means you need to explain it in simpler words (or that i need to learn how to read long sentences :D) Is this problem? * A sends encrypted email to B * C intercepts that email * C resends the email modified to B (adding his own reply address and some plain text) * B answers to C * C can see the original email -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28
https://bugs.kde.org/show_bug.cgi?id=256034 Patrick changed: What|Removed |Added CC||patr...@noxs.nl --- Comment #42 from Patrick --- Created attachment 119395 --> https://bugs.kde.org/attachment.cgi?id=119395=edit Invalid date test feed This is what happens (Akregator 5.10.3): In Akregator::Feed::appendArticles fetched items are processed. All items are stored in the feed's archive. Only new items which have a publication date newer than the expiration date, will be appended to the feed's article list. The next time the feed is fetched, all items which were processed earlier but were not added to the article list and haven't changed since then, will be processes as new items. That's when the problems start on these two lines: Article mya(*it, this); mya.offsetPubDate(nudge); The (private) constructor of Article creates an object with an invalid publication date (the default QDateTime constructor) because the item was already stored in the feed's archive and it hasn't changed. On the next line the publication date is updated, but based on the invalid publication date. This causes the invalid date to be written to the feed's archive. It's easy to reproduce with the attached feed: 1. Add the feed to Akregator. 2. Fetch the feed. The article first appears as a blank line, but after restarting Akregator the invalid is shown. -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #13 from Laurent Montel --- Yep I will test it for sure :) But I am not sure to testing it this WE. But for sure I will do next week :) Thanks for motivating dev to implement it :) -- You are receiving this mail because: You are the assignee for the bug.
