https://bugs.kde.org/show_bug.cgi?id=446549
johnathan <testing1237...@yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |testing1237...@yahoo.com
--- Comment #10 from johnathan <testing1237...@yahoo.com> ---
if i can give my 2 cents. what we call a "digital certificate" as was pointed
out is usally something like a hardware token like a yubikey or similar or a
certificate like PFX or even what you'd get from
https://www.openpgp.org/software/kleopatra/
which uses pgp to sign with your public and private key.
https://github.com/intoolswetrust/jsignpdf
this is how you properly sign a pdf. this uses certificates and "time stamping
authority" to verify that you, the user with the public key signed the
document. it has nothing to do with squigly line sign that you can do.
what was done in the video is "pseudo sign". this isn't really much to it
because anyone can do this anytime.
https://helpx.adobe.com/reader/using/sign-pdfs.html
read how adobe reader does this. they allow users to "draw" a signature but
also "secured signs" using signatures and those signatures would be the above,
pfx or the likes so we do need to update the UI, give the option like adobe
reader.
you can also look at how libreoffice handles digitally signing a document.
--
You are receiving this mail because:
You are the assignee for the bug.
