[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

[Stefan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362938

Stefan  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||ca589ee212d2734b190383969e1
   ||a9fc5d2cd720d
   Version Fixed In||16.08
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

[Stefan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362938

--- Comment #15 from Stefan  ---
Diff added to phabricator

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

[Stefan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362938

--- Comment #14 from Stefan  ---
And adding works also now :)

Believe never the documentation ;)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

[Stefan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362938

--- Comment #13 from Stefan  ---
Reading, deleting and modifying works now. Adding is still a problem. A reason
could be the date format.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

[Stefan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362938

--- Comment #12 from Stefan  ---
Today a was working on the write access. The deletion of an note works now, but
the resource blocks after this operation and is then unusable.

Adding and modifying don't work at the moment. The note data seems not to be
available as payload.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

[Stefan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362938

--- Comment #11 from Stefan  ---
The resource provides a configuration dialog now

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

[Stefan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362938

--- Comment #10 from Stefan  ---
The resource provides read-only access now. The next steps are a network error
handling and a configuration dialog.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

[Stefan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362938

--- Comment #9 from Stefan  ---
I get now also now content and the remote revision. I think that I had not set
everything correctly from the original item, so that the result wasn't
recognized properly. I now doing this:
resultItem = Akonadi::Item(item);

The setPayload part seems to to be invalid, so the note content is not visible
at the moment.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

[Stefan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362938

--- Comment #8 from Stefan  ---
A little update from yesterday: Getting all items with correct id works now.

I have also now a Job class for collections for getting the global sync
revision. This also seems to be working now.

I'm now working on getting the notes content. On the beginning this was a
little confusing because the mime type wasn't correctly, so the corresponding
method wasn't called

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

[Stefan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362938

--- Comment #7 from Stefan  ---
The OAuth authentication works now. Also getting access to seems to be working
(no QNetwork-Reply error).

So the problem now seems to be parsing the JSON data. I think I use
QJsonDocument not correctly.

The KJobs are now asyncron. I have now a new KJob for receiving the
collections. This is needed for receiving the remote id.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

[Stefan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362938

--- Comment #6 from Stefan  ---
I hope I have the right idea now:
KMime::Message::Ptr akonadiNote = KMime::Message::Ptr(new KMime::Message);
akonadiNote->subject(true)->fromUnicodeString( jsonNote["title"].toString(),
"utf-8" );
akonadiNote->contentType()->setMimeType("text/plain");
akonadiNote->contentType()->setCharset("utf-8");
akonadiNote->contentTransferEncoding(true)->setEncoding(KMime::Headers::CEquPr);
akonadiNote->mainBodyPart()->fromUnicodeString(jsonNote["note-content"].toString().toUtf8());
akonadiNote->assemble();
resultItem.setPayload(akonadiNote);

Problem is now the debugging. How can read the debug messages like
qCDebug(log_tomboynotesresource) << "Resource started";

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

[Stefan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362938

--- Comment #5 from Stefan  ---
A little status update:

For OAuth I use now the suggested o2. Because of cmake it was a little bit
difficult getting it working.

I want to use the following KJob classes:
- TomboyJobBase:
  it should provide the full OAuth stuff using the library o2
- TomboyServerAuthenticateJob:
  It's needed for the configuration it should do the OAuth registration process 
getting the client credentials
- TomboyItemsDownloadJob:
  It should retrieve all items
- TomboyItemDownloadJob:
  It should get the specific item
- TomboyItemUploadJob

For the first 3 classes I have a rudimentary implementation now. I use o2 and
KIO::AccessManager (o2 needs a QNetworkAccessManager!) for accessing the
server. I parse the received data with QJsonDocument.

Current question is, how I have to save the notes data in Akonadi::Item. I
studied the code of KJots and I think I have to use KMime:Message, but the
details are still unclear.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

[Stefan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362938

--- Comment #4 from Stefan  ---
Link to the repository:

https://github.com/staeglis/tomboynotes

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

[Stefan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362938

--- Comment #3 from Stefan  ---
Hello,

thank you for your comment.

QOAuth is no option anymore because it's not working properly. Using kQOAuth
could be also problematic because it support only HTTP POST and not HTTP PUT.
The API description is unclear in this point.

So o2 is an interesting option because it does only OAuth and the other stuff
is done directly with QNetworkAccessManager.

But I don't understand how I could use KIO::KJob. Some example resource would
be helpful. But for this I'll write a mail soon.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

[Stefan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362938

--- Comment #1 from Stefan  ---
I need also a library that implements OAuth 1.0. For now I have two candidates:
QOAuth: https://github.com/ayoy/qoauth
kQOAuth: https://github.com/kypeli/kQOAuth

I think the better candidate is QOAuth because it looks lesser dead than the
other. But what think you?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kleopatra] [Bug 363148] Deselecting Signing check box in Advanced Settings - Certificate Usage results in General Error in Kleopatra

[Stefan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363148

Stefan  changed:

   What|Removed |Added

 CC||luke1...@gmx.de

--- Comment #1 from Stefan  ---
Could confirm the issue here --- Win 10, Kleopatra 2.2.0.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kleopatra] [Bug 363154] New: Cannot create certificate with @ in the name field.

[Stefan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363154

Bug ID: 363154
   Summary: Cannot create certificate with @ in the name field.
   Product: kleopatra
   Version: 2.2.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aheine...@intevation.de
  Reporter: luke1...@gmx.de
CC: kdepim-bugs@kde.org, m...@kde.org

Trying to create a new certificate with the @-sign in the name field fails
(unless the @ is used as the first character in the name).
Using gpg directly to create a keypair, this works just fine.

Note that in some cases keys are generated specifying the email address as the
name and as the email address to ensure privacy where the key is used. For
instance the end-to-end-encryption of posteo.de only accepts OpenPGP keys which
comply to that restriction: https://posteo.de/en/help/policies-for-public-keys

Reproducible: Always

Steps to Reproduce:
1. File -> New Certificate -> Create a personal OpenPGP key pair
2. Try to enter the following name: f...@bar.com

Actual Results:  
The @-sign cannot be entered. Trying to enter it results in a noop.

Expected Results:  
The @-sign can correctly be entered.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kleopatra] [Bug 362640] cryptic error message, when using long password to export secret key

[Stefan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362640

--- Comment #1 from Stefan  ---
On a related note: Regardless of the error, the output file is created (it's
empty however, in the error case). It would be better, if the file would either
not be created, if there was an error, or that the file is removed and not
being left behind, if exporting failed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kleopatra] [Bug 362640] cryptic error message, when using long password to export secret key

[Stefan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362640

Stefan  changed:

   What|Removed |Added

 CC||luke1...@gmx.de

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kleopatra] [Bug 362640] New: cryptic error message, when using long password to export secret key

[Stefan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362640

Bug ID: 362640
   Summary: cryptic error message, when using long password to
export secret key
   Product: kleopatra
   Version: 2.2.0
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aheine...@intevation.de
  Reporter: luke1...@gmx.de
CC: kdepim-bugs@kde.org, m...@kde.org

Following the described steps the Kleopatra presents an error message which is
not quite user friendly. In fact it should be possible to use a long password
(as the one given in the repro steps). 

I understand that the issue is that the specified password is too long but
there are several usability glitches here:
1. the input field to set a password to encrypt the keyfile does allow entering
a long password and neither the displayed text hints to any limit there, nor is
there a warning/error displayed when clicking OK after having entered the long
password - at least there should be some mentioning on the restriction.
2. Given that very long passphrases are generally advertised in all docs
related to GnuPG, IMO there should be no character limit for the password here
at all.
3. The displayed error in the end is not quite user friendly. It's so cryptic
and for someone not reading the whole text in detail it won't directly point to
the actual issue (too long password). Such an error should be better presented
to the user IMO. A simple error message would suffice:
"An error occurred while trying to export the secret key.
Error: password too long"

Any additional details are only of interest to developers and should not be
presented to users.


Reproducible: Always

Steps to Reproduce:
1.on an existing X.509 key right click and select: "Export Secret Keys"
2. select an output file and click ok
3. enter the key's passphrase -> press ok
4. enter the following password for the exported key:
0f9guf9dhgsadi90sdg0ßfd0hdgj0df -> press ok
5. enter the same password to confirm it -> press OK

Actual Results:  
The following error is displayed

Title: Secret Key Export Error --- Kleopatra

An error occurred while trying to export the secret key.

The output from E:\Program Files (x86)\GNU\GnuPG\gpgsm.exe was: gpgsm:
gpg-protect-tool: AllowSetForegroundWindow(6380) failed: Access is denied.
gpgsm: gpgsm: gpg-protect-tool: AllowSetForegroundWindow(3692) failed: Access
is denied. gpgsm: gpgsm: gpg-protect-tool: password too long gpgsm:
gpg-protect-tool: password too long gpgsm: gpg-protect-tool: password too long
gpgsm: error running 'E:\Program Files (x86)\GNU\GnuPG\gpg-protect-tool.exe':
exit status 2

Expected Results:  
Password file is generated without errors.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 361503] New: Spam filter (spamassasin) does not work

[Stefan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361503

Bug ID: 361503
   Summary: Spam filter (spamassasin) does not work
   Product: kmail2
   Version: 5.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: misc
  Assignee: kdepim-bugs@kde.org
  Reporter: bugtrac...@losch-spandau.de

Since several months spamassasin did not work at my computer.
Versions:
SpamAssassin version 3.4.1
  running on Perl version 5.18.2
kmail2 5.1.3

No spam was moved from "Posteingang" to "Trash"
Yesterday I found the bug!
The spam filter were not installed properly.

First filter "Spamassasin Check" worked well.
The second filter, which moves spam to trash and marks it as "read" did not.
The filter rule was "X-Spam-Flag" matches regular expression "(yes)|(YES)"
But spamassasin does not create a line "X-Spam-Flag". In teh current version it
creates a line "X-Spam-Level".
So I added a second rule to that filter:
"X-Spam-Level" contains "**"

Works! 

Reproducible: Always

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs