DSS-P.Client
Metadata
| Authors | Egelke BVBA,e-Contract.be BVBA |
|---|---|
| Copyrights | 2014 © Egelke BVBA and e-Contract.be BVBA |
| Description | Client for the "Digital Signature Service Protocol" as offered by e-Contract.be |
| IconUrl | https://egelke-web.sharepoint.com/SiteImages/File-Ok-icon.png |
| LicenseUrl | http://www.gnu.org/licenses/lgpl.html |
| Owners | Egelke BVBA,e-Contract.be BVBA |
| ProjectUrl | http://www.e-contract.be/ |
| ReleaseNotes | Upgrade to 1.2.0 specs of DSSP by e-Contract.be |
| RequireLicenseAcceptance | False |
| Summary | The new Digital Signature Service creates PAdES LTV signatures using the eID card according to the latest ETSI PAdES Baseline Profile version 2.2.2. This standard is being pushed by the EC e-Signatures Expert Group to guarantee maximum recognition and interoperability of signed documents between EU member states. Furthermore the Digital Signature Service product is not limited to PDF signatures. It also support XAdES-X-L and ETSI XAdES Baseline Profile version 2.1.1 signatures (LT-Level compliance). The new DSS is the only solution today on the market offering such compliance. The new Digital Signature Service comes with a new and highly secure Digital Signature Service Protocol. This protocol is a derivative of work that we performed within the OASIS DSS-X group and offers maximum protection against various types of attacks. From a security point of view, this new protocol is just it. The old protocol, as implemented in the original eID DSS, could easily be integrated in an insecure way by the developer. For the new protocol, this is no longer possible given the design of the protocol. As we all know that protocols (and their implementation, especially authentication protocols) are very vulnerable to attacks, this new protocol is a huge step forward. This makes the new Digital Signature Service truly unique compared to other solutions. |
| Tags | e-Contract.be DSS eSigning eID |
| Title | Digital Signature Service Protocol Client |
| PackageSize | 587548 |
| PackageHashAlgorithm | SHA512 |
| PackageHash | YQySBi6IRikSLVzJl+xBfz3f1o30e5KyX1suIZpdpeHFbifxblWasr3hs6utF+INqe6zviSTrEuWcOwZRNFdNA== |
| DownloadCount | 000000 |
| CreatedDate | 2014-10-06T19:48:15 |
Access
You can access data for this project using the tools and addresses described below.
NuGet (nuget.exe)
- Installing the package (HTTP Basic authentication):
-
nuget install DSS-P.Client -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
nuget install DSS-P.Client -Source http://nuget.gw.symbolsource.org/Public/%login%/%key%/NuGet/FeedService.mvc
NuGet (Package Manager Console)
- Installing the package (search all configured feeds):
-
Install-Package DSS-P.Client
- Installing the package (HTTP Basic authentication):
-
Install-Package DSS-P.Client -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
Install-Package DSS-P.Client -Source http://nuget.gw.symbolsource.org/Public/%login%/%key%/NuGet/FeedService.mvc
- Uinstalling the package:
-
Uninstall-Package DSS-P.Client
OpenWrap
- Installing the package:
-
o add-wrap DSS-P.Client
- Uninstalling the package:
-
o remove-wrap DSS-P.Client
Versions
A version is snapshot of a project's source code. It does not need to follow the Major.Minor.Revision.Build numbering pattern. It can be an arbitrary string of text that identifies a release or a build, in particular including meaningful words like beta, RC or RTM.