Results 1 to 2 of 2

Thread: K-Gpg in KDE4.82 broken or change in signature defaults of Kgpg-agent/gpg.conf?

  1. #1
    Join Date
    Jan 2009
    Location
    Somewhere in Fictionland
    Posts
    1,479

    Question K-Gpg in KDE4.82 broken or change in signature defaults of Kgpg-agent/gpg.conf?

    I generated today a new DSA/Elgamal key for my father.
    The interesting result was 3072/1024 DSA/Elgamal compared to the usual 1024/4096 as of before with KDE 4.7.2
    Now, this might be an error of the packages in KS48 repos (in this case a bugreport is needed) or this can be another way of doing the notation or this is actually another cryptographic approach.
    DSA for long time was limited for GPG compatibility to DSA 1024 keys and these where "hardwired" to SHA1 (which was considered broken - although more theoretically AFAIK). Now a DSA3072 will be probably another SHA key lenght and therefore Elgamal is held lower (1024) for an overall key-lenght of 4096.
    That should be than equally safe, if not safer then the previous DSA/Elgamal settings. Alternative would be the MIT RSA keys with 4096 but I see on my machines the very difference of reckoning power since these ones are really very long. And well, DSA in that setting may be even more difficult to crack (always theoretically).

    Can somebody delight me with some source of info about this change, or some link where the decision was discussed. Not that a man cannot "Google" as sharp minded people and friends of the un-useful redundancy are not tired to repeat in those cases. But I would like to have a bit less hardship in searching if by chance somebody already knows.

    Thanks in advance


    P.S. The feature request (as of signature) has reached quota 56. Good prospects. Keep on for a better safety.
    Just "clicking away" security warnings about a change in repo signature ? Not able to control?
    Then please vote for
    https://features.opensuse.org/312047
    openSUSE should have an efficient web of trust.

  2. #2
    Join Date
    Jan 2009
    Location
    Somewhere in Fictionland
    Posts
    1,479

    Default Re: K-Gpg in KDE4.82 broken or change in signature defaults of Kgpg-agent/gpg.conf?

    Some updates about this problem:
    Yes, in 4.8.2 the "create a signature" function is apparently broken. I updated to 4.8.3 where it works (at least in expert mode) but then I have a problem sending mail. These problem seem all Kgpg and KDE - Pim related.
    It seams that the akonadi driven database of personal contacts is not "seen" by kmail. I did already report as a bug that kmail does not honor the settings for encryption (e.g. mandatory encryption for a certain user) given in the "personal kontakts". Now with the update of 4.8.3 I encounter that the whole contact is seen as "unknown" so it asks after giving the password whether I "want to give what name in the database to this contact". Once you deny this (cancel), you are coming back to the dialogue and you can then tell to send. But sending fails with "general error in the creation of the mail". This is with a 4096 RSA key. I will try now with an El Gamal to see weather the problem is RSA related.
    Just "clicking away" security warnings about a change in repo signature ? Not able to control?
    Then please vote for
    https://features.opensuse.org/312047
    openSUSE should have an efficient web of trust.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •