191–200 of 200 posts
Oof, unfortunately the Alfredo license kills a lot of use-cases for this project.
can you please elaborate which use-cases? - maybe that's something that actually can be possible by splitting some parts of the project into MIT licensed dependencies?
Earlier quoted context omitted.
As always, it depends on the jurisdiction. The EU has the eIDAS [1] which allows simple signatures such as these for most form-free-contracts (the majority). There are however some, which need a digital cert and have to be encrypted. [1] https://en.wikipedia.org/wiki/EIDAS
And Switzerland ZertES: https://en.wikipedia.org/wiki/ZertES - There are not normally various levels of trust with afaik only QES (Qualified Electronic Signature), the highest level to legally be on the same level as a hand signature.
Earlier quoted context omitted.
One of the tough things about a party-controlled, self-hosted e-signature is that it becomes easier to repudiate because a party to the contract has custody of the platform. The non-custodial party can claim they never signed, and when the custodial party produces evidence of IP address and timestamp, the non-custodial party may have a credible argument that they are faked and the person asserting those authenticated…
If only someone would invent a public nonrepudiatable ledger.
Earlier quoted context omitted.
can be self-hosted on-premises This kills it as a viable alternative to DocuSign. The point of Docusign is that it is an independent third party that maintains custody of the signed contract and proof of acceptance (i.e., digital signatures) by all parties to the contract. A self-hosted digital signature system isn't worth anything in court; the other parties will simply reject the authenticity of any data held withi…
>A self-hosted digital signature system isn't worth anything in court; the other parties will simply reject the authenticity of any data held within it and the amount you'd have to spend to get that data into evidence would probably pay for several centuries of DocuSign's enterprise edition. When self-hosting it - you can integrate it with AWS s3 Azure or Google Cloud files storage - those are the trustworthy third p…
Hi everyone, my name is Alex and I'm the creator of DocuSeal. I was not happy with the existing mainstream document signing solutions so I decided to create an open-source alternative. I've been working on this project since the middle of May and here is what the tool can do so far: - PDF form fields builder - 10 field types available (Signature/Date/File/Checkbox etc) - Multiple submitters per document - Automated e…
I love the fact that this exists, however my major concern is that because this is self-hosted, in the event of a dispute, the other party can claim that I forged the document. In such a scenario, how would I ever prove that I didn't?
https://en.wikipedia.org/wiki/Merkle_tree
Alternatively I'm thinking about adding a third party AWS QLDB integration - QLDB allows to maintain an immutable, cryptographically verifiable log of data changes.
Hi everyone, my name is Alex and I'm the creator of DocuSeal. I was not happy with the existing mainstream document signing solutions so I decided to create an open-source alternative. I've been working on this project since the middle of May and here is what the tool can do so far: - PDF form fields builder - 10 field types available (Signature/Date/File/Checkbox etc) - Multiple submitters per document - Automated e…
It's not perfect for a single person just using it for themselves (a lot of workflows seems very company/team oriented), but it's still better than nothing which is what I had before. Thank you for open sourcing it, this will absolutely help me :)
Hi everyone, my name is Alex and I'm the creator of DocuSeal. I was not happy with the existing mainstream document signing solutions so I decided to create an open-source alternative. I've been working on this project since the middle of May and here is what the tool can do so far: - PDF form fields builder - 10 field types available (Signature/Date/File/Checkbox etc) - Multiple submitters per document - Automated e…
This looks great. What's the best way to contribute a translation? I think a great feature would be an email with a confirmation link after the pdf gets signed to ensure the owner of the email was the person who signed the document, if the link share option is used.
Earlier quoted context omitted.
IP addresses and browser User Agent strings are stored for each signature/submission - those are the only measures for 'non-repudiation' currently available. but i think it doens't differ from other mainstream SaaS solutions - if you read through their terms of services - they put 'non-repudiation' liability on users of their services
Another method you might consider implementing would be identity verification via SMS code. I've experienced this with docusign: https://support.docusign.com/s/document-item?language=en_US&... It requires you to know the phone number of the signer, but for important stuff you typically do.
How do these electronic signatures work? Is it PGP? Where does one store the secret (e.g. private key) and how can someone prove that it is really my signature?
Earlier quoted context omitted.
>A self-hosted digital signature system isn't worth anything in court; the other parties will simply reject the authenticity of any data held within it and the amount you'd have to spend to get that data into evidence would probably pay for several centuries of DocuSign's enterprise edition. When self-hosting it - you can integrate it with AWS s3 Azure or Google Cloud files storage - those are the trustworthy third p…
How do you prove who actually signed the document? Docusign does this by only sending the signing link to the signer’s email. I don’t see how you could prove that no one else had access to that link if you’re self hosting.