Projet

Général

Profil

« Précédent | Suivant » 

Révision 19b58bab

Ajouté par Remy Menard il y a plus de 11 ans

Version 1.9

  • All:
    - use TLS for secured links
    - SigMa is now fully functionnal
    - completed documention
    - a lot of bugs fixed!
  • SigMa:
    - signature creation from the canonical form of the event
    - signature creation using ECDSA algorithm
    - signature is correctly verified
  • ETa:
    - manage the extension identifying the owner of the event
    - if no identity is provided, the identity of the certificate is used
  • EpcisPHi:
    - access to the web interface of policy management is made by
    certificate
  • OMeGa:
    - if no identity is provided, the identity of the certificate is used
  • IoTa-Installer:
    - create and use certificates for TLS
    - configure Apache Tomcat for TLS
  • Greyc letters figures:
    - show SigMa library (SigMa-Commons)

Voir les différences:

SigMa/SigMa-Commons/README
- epcis-commons
- bouncycastle
- commons-logging
- xmlsec
Usage:
The signature is created and inserted in the event with an
extension (see Mu for name and namespace of this extension).
A second extension, the alias of the public key used to sign,
is added at the same time. This extension is used by SigMa
to get the right public key.
The alias must be the same that DN (Distinguished Name) of
the certificate used to sign.

Formats disponibles : Unified diff