Page 1 of 2 12 LastLast
Results 1 to 10 of 18

Thread: S/MIME public beta now available!

  1. #1

    S/MIME public beta now available!

    The first S/MIME public beta is here

    Dear community, partners and friends,

    It is time for another (beta) release! In the past couple of months we have shown you more and more details about the S/MIME implementation for WebApp, and we are happy to announce the first public beta of this WebApp plugin package.

    What is in this package?

    The S/MIME plugin for WebApp is an easy to use tool that helps the user secure email with minimal effort. It provides message signing for sender and content authentication and encryption for privacy which can be activated at the click of a button. Public certificates are automatically imported from incoming signed email messages and can be used to encrypt outgoing email messages on demand.

    You can on this product page. On this page you will read how the S/MIME plugin helps users to share information easy but yet secure!

    New in this open BETA: the certificate manager!

    If you are familiar with the first private beta packages you have already been using this functionality. This new version introduces the certificate manager: a user friendly tool to check and delete the certificates that have been imported for you.

    We need your feedback!

    Our S/MIME beta test group provided us with useful input and certificate examples after the first (closed) beta packages became available. The feedback has allowed us to provide you with a better S/MIME experience. We were also able to add extensive support for different certificate types.

    Now that we’ve introduced the new certificate manager and released this public beta package we’re looking forward to more feedback! Questions about the certificate manager or having an issue with a specific type of certificate? Let us know so we can improve.

    Have you been using the earlier beta packages?

    With the introduction of the certificate manager we have also changed the way certificates are stored and handled in the background. If you’ve been part of the beta test group and want to use the certificate manager, you will need to clear out the certificate cache and re-import your own private certificate.

    Getting the package

    You can grab this beta release .
    Regards,

    Martyn

  2. #2
    Senior Member
    Join Date
    Feb 2008
    Location
    Leonberg, Germany
    Posts
    273
    I know this is a beta release, and I did only some smoke testing so far, but I still wonder a bit why I did not see any warning before uploading my private key via a plaintext (HTTP) connection. Yes, a user should be able to figure out itself whether the connection is HTTP or HTTPS, but from my point of view, the user should explicitly confirm this before uploading the private key. Note that some (even European) countries treat a valid digital signature as a legally binding confirmation, thus leaking a private key accidentally could have heavy impacts for an individual user.
    I install, configure, customize, integrate and maintain Zarafa setups in different environments since 2007. If you want my full attention, please send me a private message and ask for paid support.

  3. #3
    Zarafa Development

    Join Date
    Mar 2014
    Posts
    49
    Thanks for the feedback, we recommend using the WebApp only over HTTPS, which means that the S/MIME plugin functionality also works over HTTPS. We will take adding a warning about non-HTTPS connection in consideration.

  4. #4
    Junior Member
    Join Date
    Mar 2015
    Posts
    6
    It is very nice that s / mime now available.
    Yesterday I made some test and it went very well.
    However, some questions.
    First I imported my .p12 file.
    This worked well.
    Then I tried the public key from a signed mail imported.
    This only seems to work if the sender is not from the same domain as my own ?

    My questions:
    - There is another way to import public keys?
    - Where the keys of the users are stored? (I used Samba4 AD for user management)
    - Can the stored keys are also used by Outlook or z-push?

    Thank you for the good work.

    Rainer

  5. #5
    Hi Rainer,

    Thanks for the feedback. We've read it.
    Let me get back to you regarding these questions.

    Cheers,
    Regards,

    Martyn

  6. #6

    Exclamation

    Hi,

    i just installed the S/MIME-Plugin. When i tried to upload my .p12-file i always got an "error decrypting certificate". After some time playing around i changed the password. Now it works. Please check if some special characters cause problems.

    Thank you for the Plugin!

  7. #7
    Junior Member
    Join Date
    Aug 2012
    Posts
    7
    Same result with my tests. Special characters e.g. ! or ? doesn't work

  8. #8
    Hi,
    @Balou, Mitchel
    Thanks for the feedback.
    That ticket is already created.

    @Rainer,

    It shouldn't matter if a sender is outside your domain.
    Regards,

    Martyn

  9. #9
    Zarafa Development

    Join Date
    Mar 2014
    Posts
    49
    The public keys are stored in either MAPI (User Store) or LDAP/AD. Note that there is a bug with sending email with a key from LDAP/AD.
    There is no other import functionality then the auto-import at the moment, although it is possible to write a Python/PHP script to achieve this.

    The stored keys in MAPI can not be used in Outlook or z-push since it's not aware that they are stored there. But with AD/LDAP it might be possible to deploy the public keys to z-push and WebApp (if I recall correctly it supports this functionality).
    For LDAP the field would be 'userCertificate;binary'.

  10. #10
    Junior Member
    Join Date
    May 2015
    Posts
    6
    Great Plugin, thanks a lot for this work, I have been waiting for SMIME support for quite some time.

    I'm currently trying to use smime beta 3 but I seem to have the same problems mentioned here before:
    - Certificate/Key Import (PKCS12 / P12 bundle) only worked after I used a password without special characters
    - currently I can't use (unlock) my private key, it always says wrong password, I assume this is because of special characters in passphrase too. :-(

Page 1 of 2 12 LastLast

Similar Threads

  1. S/MIME and WebAccess 7.1.10
    By bauer40 in forum WebAccess
    Replies: 3
    Last Post: 26-11-2014, 11:34 AM
  2. S/mime
    By xthbx in forum WebApp
    Replies: 0
    Last Post: 28-06-2013, 06:13 AM
  3. S/mime Certificate in GAL ?
    By RainerR in forum Outlook client
    Replies: 0
    Last Post: 30-11-2012, 07:02 PM
  4. S/MIME and Chromium
    By novetica in forum WebAccess usage Archives
    Replies: 3
    Last Post: 18-12-2010, 05:42 PM
  5. S/MIME in Webaccess
    By mvanvoorden in forum WebAccess usage Archives
    Replies: 6
    Last Post: 27-09-2010, 08:16 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •