[Kde-pim] Review Request 127181: Add a 'trust owner' dialog for newly imported secret keys

Andre Heinecke aheinecke at intevation.de
Tue Mar 1 16:05:42 GMT 2016


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/127181/#review93010
-----------------------------------------------------------




kleopatra/commands/importcertificatescommand.cpp (line 411)
<https://git.reviewboard.kde.org/r/127181/#comment63438>

    Space after braces still a style issue in this patch.
    You can also use longer lines.
    
    Sorry if this appears to be annoying but if we afterwards run tools on this to unify coding style this breaks history so new commits should follow coding style guidelines.



kleopatra/commands/importcertificatescommand.cpp (line 428)
<https://git.reviewboard.kde.org/r/127181/#comment63447>

    Woops, have not noticed that in the first review. This should not be a warning. Importing S/MIME keys is a standard usecase.
    
    Just remove the message and return.



kleopatra/commands/importcertificatescommand.cpp (line 432)
<https://git.reviewboard.kde.org/r/127181/#comment63444>

    Please reduce this to the fingerprint and pretty (name and email) user ID's but all UID's and not just the first one.
    
    Fingerprint first and most prominent below UID's without caption.
    
    See utils/formatting.cpp Formatting::prettyUserID.
    
    Create a string list of prettyUserID's join them with \n and insert in the string.
    
    This should come closest to the info available on the command line.
    
    Btw. although GnuPG does not allow this, Keys without any UID are OpenPGP compliant and this could also happen when you import an ECC key using GnuPG 2.0 as GnuPG only handles UID's with a valid selfsig and GnuPG 2.0 can't handle ECC Signatures.


- Andre Heinecke


On March 1, 2016, 3:16 p.m., Sean Engelhardt wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/127181/
> -----------------------------------------------------------
> 
> (Updated March 1, 2016, 3:16 p.m.)
> 
> 
> Review request for KDEPIM and Andre Heinecke.
> 
> 
> Repository: kdepim
> 
> 
> Description
> -------
> 
> When importing a new secret key in Kleopatra, a dialog-window will pop up to determinate if the owner of the newly imported key should be trusted or not.
> Since imported secret keys are usually the own ones it would make sense to enhance the trusting-process.
> 
> 
> Diffs
> -----
> 
>   kleopatra/commands/importcertificatescommand.cpp 18a65d1 
> 
> Diff: https://git.reviewboard.kde.org/r/127181/diff/
> 
> 
> Testing
> -------
> 
> Imported newly generated keys to determinate if the script gets triggered and works as requested.
> 
> -edited version after the 1. reviewing process. Changed according to the requests. Propably found a bug in kleo.
> 
> 
> Thanks,
> 
> Sean Engelhardt
> 
>

_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/


More information about the kde-pim mailing list