Menu
▾
▴
signserver-develop
You can subscribe to this list here.
| 2008 |
Jan
(1) |
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(4) |
Dec
|
| 2010 |
Jan
(1) |
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
| 2012 |
Jan
(1) |
Feb
(8) |
Mar
(10) |
Apr
|
May
(12) |
Jun
(2) |
Jul
(28) |
Aug
(15) |
Sep
(12) |
Oct
(2) |
Nov
|
Dec
(16) |
| 2013 |
Jan
(30) |
Feb
(1) |
Mar
|
Apr
(11) |
May
(2) |
Jun
(11) |
Jul
(15) |
Aug
(4) |
Sep
(1) |
Oct
(10) |
Nov
(1) |
Dec
(2) |
| 2014 |
Jan
(8) |
Feb
(13) |
Mar
(12) |
Apr
(24) |
May
(2) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(2) |
Oct
(1) |
Nov
(2) |
Dec
(1) |
| 2015 |
Jan
(3) |
Feb
(6) |
Mar
|
Apr
|
May
(7) |
Jun
(7) |
Jul
(3) |
Aug
(5) |
Sep
(1) |
Oct
(8) |
Nov
(6) |
Dec
|
| 2016 |
Jan
|
Feb
(3) |
Mar
(5) |
Apr
(9) |
May
(26) |
Jun
(8) |
Jul
|
Aug
|
Sep
(11) |
Oct
(8) |
Nov
(1) |
Dec
(2) |
| 2017 |
Jan
(4) |
Feb
(7) |
Mar
(7) |
Apr
(4) |
May
(1) |
Jun
(5) |
Jul
(3) |
Aug
(3) |
Sep
(1) |
Oct
(4) |
Nov
(5) |
Dec
(1) |
| 2018 |
Jan
(4) |
Feb
(1) |
Mar
(1) |
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
(1) |
Mar
(2) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(2) |
Dec
|
| 2020 |
Jan
(3) |
Feb
|
Mar
(2) |
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|
From: Marcus L. <mar...@ke...> - 2023-12-07 15:04:47
|
We are pleased to announce the release of SignServer Community 6.2. Release highlights include: REST API for managing workers For more information: Read the full SignServer Community 6.2 Release Notes<https://doc.primekey.com/signserver/signserver-release-information/signserver-release-notes/signserver-community-6-2-release-notes> Visit the SignServer project on signserver.org<https://signserver.org/> Best regards Marcus Lundblad on behalf of the SignServer / Keyfactor Community Team |
|
From: Markus K. <mar...@ke...> - 2023-07-03 13:36:07
|
Hi all, We are pleased to announce the release of SignServer Community 6.0. Release highlights include: * REST Interface * Post-Quantum Readiness * Technology upgrades For more information: Read the full SignServer Community 6.0 Release Notes: https://doc.primekey.com/x/NseKAw Visit the SignServer project on signserver.org: https://signserver.org<https://signserver.org/> Follow us on SignServer Discussions on GitHub for future announcements: https://github.com/Keyfactor/signserver-ce/discussions Best Regards, Markus Kilås, on behalf of the SignServer / Keyfactor Community Team -- Markus Kilås Senior Product Architect M: +46 70 424 94 85 mar...@ke...<https://www.keyfactor.com/> [cid:769...@ke...-1] Identity-first security for every device, workflow, and thing. Follow Keyfactor on LinkedIn<https://linkedin.com/company/wearekeyfactor/> CONFIDENTIALITY NOTICE This communication may contain privileged or other confidential information. If you received this email in error, then please advise the sender by reply email and immediately delete the message and any attachments without copying or disclosing the contents. Thank you. |
|
From: Markus K. <mar...@ke...> - 2022-12-20 16:22:01
|
Hi all, We are pleased to announce the release of SignServer Community 5.11.1. Release highlights include: * Debian package signing * Refreshed UI * Bouncy Castle upgraded to 1.72 For more information: Read the full SignServer Community 5.11.1 Release Notes: https://doc.primekey.com/x/i6uKAw Visit the SignServer project on: https://signserver.org Follow us on SignServer Discussions on GitHub for future announcements: https://github.com/Keyfactor/signserver-ce/discussions Best Regards, Markus Kilås, on behalf of the SignServer / Keyfactor Community Team |
|
From: Markus K. <Mar...@ke...> - 2022-09-29 15:25:36
|
Hi all, We are pleased to announce the release of SignServer Community 5.10.0. Release highlights include: * Java Archive (JAR) File Signing * Post-quantum Signing with upgraded SPHINCS+ Algorithm For more information: Read the full SignServer Community 5.10 Release Notes: https://doc.primekey.com/x/A4_KAw Visit the SignServer project on: https://signserver.org Follow us on SignServer Discussions on GitHub for future announcements: https://github.com/Keyfactor/signserver-ce/discussions Best Regards, Markus Kilås, on behalf of the SignServer / Keyfactor Community Team -- Markus Kilås Senior Product Architect M: +46 (0)70 424 94 85 mar...@ke...<https://www.keyfactor.com/> [KEYFACTOR] Seamless orchestration. Every key, every certificate. Follow Keyfactor on LinkedIn<https://linkedin.com/company/wearekeyfactor/> PrimeKey and Keyfactor merged<https://www.keyfactor.com/press-releases/keyfactor-and-primekey-merge-to-bring-machine-identity-management-to-the-mainstream/> in June 2021. Moving forward, communication will come from Keyfactor. PrimeKey.com<https://www.primekey.com/> will be live throughout 2022. CONFIDENTIALITY NOTICE This communication may contain privileged or other confidential information. If you received this email in error, then please advise the sender by reply email and immediately delete the message and any attachments without copying or disclosing the contents. Thank you. |
|
From: Markus K. <Mar...@ke...> - 2022-06-10 06:43:25
|
Hi all, From now on, our main discussion forum is on GitHub. Please join us there to share knowledge or ask questions to other developers or the product team. SignServer Discussions on GitHub: https://github.com/Keyfactor/signserver-ce/discussions The SourceForge mailing lists will be discontinued during 2022. We also welcome you to sign up for our Newsletter on Keyfactor Community, to stay up to date on the latest news, software updates, hands-on tutorials and user workshops on all our open-source software. Keyfactor Community: https://www.keyfactor.com/community/ Best Regards, Markus Kilås, on behalf of the SignServer / Keyfactor Community Team |
|
From: Markus K. <Mar...@ke...> - 2022-06-01 16:57:54
|
Hi all, We are pleased to announce the release of SignServer Community 5.9.1. Release highlights include: * More frequent releases * Code signing with post-quantum cryptography * Azure Key Vault support * DNSSEC support For more information Read the full SignServer 5.9.1 Release Notes: https://doc.primekey.com/x/GgYVAw Visit the SignServer project on: https://signserver.org From now on, our main discussion forum is on GitHub, see SignServer Discussions on GitHub: https://github.com/Keyfactor/signserver-ce/discussions Best Regards, Markus Kilås, on behalf of the SignServer / Keyfactor Community Team |
|
From: Markus K. <mar...@pr...> - 2021-04-13 12:38:12
|
The PrimeKey SignServer team is pleased to announce that SignServer is available as a Docker container on Docker Hub, built on the SignServer Community 5.2 release. To download SignServer Community Container from Docker Hub, go to https://hub.docker.com/r/primekey/signserver-ce . To review the SignServer Community 5.2 Release Notes, refer to the news post https://sourceforge.net/p/signserver/news/2020/01/signserver-520final-released/ . For download links, documentation, and contact information for the mailing list and discussion forums, see: https://www.signserver.org Best Regards, Markus Kilås, Tech Lead SignServer on behalf of the PrimeKey SignServer Team |
|
From: Markus K. <mar...@pr...> - 2020-04-27 08:38:47
|
On 4/27/20 8:34 AM, Markus Kilås wrote: > It is time to sign the SVN commit protocol for SignServer 5.4.0.Final. > As usual you that have made commits are marked in the document (all of > you this time). > > This time I am proposing that we try to sign the document digitally and > try out an online service for that. Let me know if you do not have > BankID and we figure out something else. > > This is what you need to do if you would like to sign the protocol: > > 1. Obtain the document from https://jira.primekey.se/browse/DSSINTER-491 > 2. Calculate the SHA-256 hash of it: > sha256sum signserver-5.4.0.Final-svn-review-protocol.pdf > 3. Read, understand and carry out whats in the document as usual > 4. Login to sign the hash: > URL: > Passphrase: > BankID: ebox > 5. Click Sign > 6. Compare the SHA-256 you computed with the one displayed in the BankID > app before signing Hi all, This e-mail was intended only to the developers who made commits to the repository for the 5.4.0.Final. If your signature is needed there will be a separate e-mail to you. Everybody else can just ignore it, sorry for spamming you :) Cheers, Markus |
|
From: Markus K. <mar...@pr...> - 2020-04-27 06:35:10
|
Hi all, It is time to sign the SVN commit protocol for SignServer 5.4.0.Final. As usual you that have made commits are marked in the document (all of you this time). This time I am proposing that we try to sign the document digitally and try out an online service for that. Let me know if you do not have BankID and we figure out something else. This is what you need to do if you would like to sign the protocol: 1. Obtain the document from https://jira.primekey.se/browse/DSSINTER-491 2. Calculate the SHA-256 hash of it: sha256sum signserver-5.4.0.Final-svn-review-protocol.pdf 3. Read, understand and carry out whats in the document as usual 4. Login to sign the hash: URL: https://min.ebox.nu/x_zgfyc1iwq Passphrase: KotsinRoggisDacZudQuoobyuirbUcNo BankID: ebox 5. Click Sign 6. Compare the SHA-256 you computed with the one displayed in the BankID app before signing Full instructions are available here: http://confluence.primekey.com/display/DTS/Digitally+Signing+the+SignServer+Release+Protocol?moved=true Cheers, Markus -- Markus Kilås Product Owner SignServer Phone: +46 70 424 94 85 E-mail: mar...@pr... PrimeKey Solutions AB Solna Access, Plan A8 Sundbybergsvägen 1 SE-171 73 Solna, Sweden https://www.primekey.com |
|
From: jose m. <jjm...@gm...> - 2020-04-15 10:14:12
|
Hi!.
I want to understand how workers work with more than one alias=person.
If I have 1000 peoples to sign documents what do I need? do I need a
sigle token with a JKS and 1000 aliases with one pdf signer worker and
select the alias when I sign, or I need 1000 different workrs with one
alias and 1000 pdf signer workesrs?.
In short, what do I need if I want to signs diferent pdf with near 1000
different signers?
Thnks!.
(sorry for my english)
|
|
From: Markus K. <mar...@pr...> - 2020-03-26 12:33:55
|
On 3/25/20 3:09 PM, Arnaud Defos wrote: > Hi everyone, > > The version of iText is very very old ! > > Is there an update scheduled ? It could resolve a lot of bugs and it is > necessary to reduce security issues. > > Thanks ! > > Arnaud Hi Arnaud, SignServer has a fork of the last officially released version of iText (2.1.7) before it switch license model. We can not use the latest versions as they are AGPL licensed and thus not compatible with LGPL. Is there any particular bugs or security issues that you have in mind? Also note that SignServer only uses a small part of the library needed to calculate and insert the signatures. Cheers, Markus |
|
From: Arnaud D. <arn...@gm...> - 2020-03-25 14:09:49
|
Hi everyone, The version of iText is very very old ! Is there an update scheduled ? It could resolve a lot of bugs and it is necessary to reduce security issues. Thanks ! Arnaud |
|
From: Markus K. <mar...@pr...> - 2020-01-22 09:29:56
|
Hi all, The PrimeKey SignServer team is pleased to announce the release of SignServer Community 5.2.0.Final. In total 18 tickets have been resolved since SignServer Enterprise 5.1.0 and 58 tickets since the last community version, highlights mentioned below. New Administration Web The SignServer Administration GUI (AdminGUI) has been replaced with a brand new Administration Web interface, previously only available in SignServer Enterprise. The improved and modern AdminWeb interface eases deploying SignServer by allowing using a Web browser for managing administration tasks instead of the standalone Java desktop application. PGP Signing Support In addition to the support of all X.509 based signers, we have now added support for PGP/GPG signing of software release packages and repositories, or for general signing. The new OpenPGP Signer can produce both detached and clear-text signatures. For step-by-step instructions on configuring and using this new signer, see https://doc.primekey.com/signserver/signserver-operations/setting-up-openpgp-signer See also our previous blog post on PGP signing with SignServer: https://blog.ejbca.org/2019/10/pgp-signing-with-signserver.html Upgrade Information For full details of fixed issues implemented in this release, refer to our JIRA Issue Tracker: https://jira.primekey.se/issues/?filter=14587 For upgrade instructions, review the https://doc.primekey.com/signserver/signserver-installation/upgrade-signserver About this Release For download link, documentation, and contact information for mailing list and discussion forums, see: https://www.signserver.org Best Regards, Markus Kilås, Product Owner SignServer on behalf of the PrimeKey SignServer Team |
|
From: Markus K. <mar...@pr...> - 2020-01-09 07:50:18
|
On 1/8/20 2:46 PM, Kevin DG wrote: > I checked to sign a PDF in version 2.0 > (https://github.com/pdf-association/pdf20examples/blob/master/Simple%20PDF%202.0%20file.pdf) > with worker pdf signer. > > It's works but ... there is always a "but" :-). > > This is a pdfinfo result before the signature: > > > pdfinfo Simple\ PDF\ 2.0\ file\ \(1\).pdf > Tagged: no > UserProperties: no > Suspects: no > Form: none > JavaScript: no > Pages: 1 > Encrypted: no > Page size: 612 x 396 pts > Page rot: 0 > File size: 5207 bytes > Optimized: no > PDF version: 2.0 > > > This is a pdfinfo result after the signature: > > ▶ pdfinfo Simple\ PDF\ 2.0\ file\ \(1\)\ \(1\).pdf > Producer: iText 2.1.7 by 1T3XT > ModDate: Wed Jan 8 14:04:29 2020 CET > Tagged: no > UserProperties: no > Suspects: no > Form: AcroForm > JavaScript: no > Pages: 1 > Encrypted: no > Page size: 612 x 396 pts > Page rot: 0 > File size: 37897 bytes > Optimized: no > PDF version: 1.6 > > > The PDF version is downgrade from 2.0 to 1.6, so it's works but it can > be i think generate problem or lost functionality linked to 2.0 format. > > When we review signserver code, we understand why the downgrade is > processed. Signserver use an old version of iText. > iText handle the PDF version detection in the form of integer (0 => 1.0, > 6 => 1.6, 7 => 1.7), so the PDF in version 2.0 is detected to 0.... > Signserver upgrade the PDF in 1.6 also to handle the digest algorithm > (in my case SHA256). > > Any ideas about that ? Hi Kevin, It is correct that so far only PDF version up to 1.7 is supported and that an older version of iText is used as a base for the signer. Without checking the code now, from your description about it, it sounds to me like maybe we could adjust the PDF version detection to also support version 20 + if needed also the upgrade logic. I have not read up enough on the 2.0 spec to know if anything else changed regarding the signatures or if the above change would be enough. Could be worth trying out at least. Cheers, Markus PrimeKey Solutions |
|
From: Kevin DG <ke...@du...> - 2020-01-08 14:11:59
|
Hello all, I checked to sign a PDF in version 2.0 ( https://github.com/pdf-association/pdf20examples/blob/master/Simple%20PDF%202.0%20file.pdf) with worker pdf signer. It's works but ... there is always a "but" :-). This is a pdfinfo result before the signature: > > pdfinfo Simple\ PDF\ 2.0\ file\ \(1\).pdf > Tagged: no > UserProperties: no > Suspects: no > Form: none > JavaScript: no > Pages: 1 > Encrypted: no > Page size: 612 x 396 pts > Page rot: 0 > File size: 5207 bytes > Optimized: no > PDF version: 2.0 This is a pdfinfo result after the signature: ▶ pdfinfo Simple\ PDF\ 2.0\ file\ \(1\)\ \(1\).pdf > Producer: iText 2.1.7 by 1T3XT > ModDate: Wed Jan 8 14:04:29 2020 CET > Tagged: no > UserProperties: no > Suspects: no > Form: AcroForm > JavaScript: no > Pages: 1 > Encrypted: no > Page size: 612 x 396 pts > Page rot: 0 > File size: 37897 bytes > Optimized: no > PDF version: 1.6 The PDF version is downgrade from 2.0 to 1.6, so it's works but it can be i think generate problem or lost functionality linked to 2.0 format. When we review signserver code, we understand why the downgrade is processed. Signserver use an old version of iText. iText handle the PDF version detection in the form of integer (0 => 1.0, 6 => 1.6, 7 => 1.7), so the PDF in version 2.0 is detected to 0.... Signserver upgrade the PDF in 1.6 also to handle the digest algorithm (in my case SHA256). Any ideas about that ? Regards, |
|
From: Markus K. <mar...@pr...> - 2019-11-25 15:23:56
|
On 11/24/19 10:25 PM, Jaime Hablutzel wrote: > Are there plans to support Azure Key Vault for SignServer in a similar > way that it is now being supported for EJBCA > (https://www.primekey.com/blog/2019/10/22/ejbca-on-azure-keyvault/)?. > > -- > Jaime Hablutzel - +51 994690880 > Hi Jaime, Yes we are planning on adding Azure Key Vault support based on the implementation in EJBCA that you contributed. We already have a ticket for it (https://jira.primekey.se/browse/DSS-2064) and we hope to look into it early next year. Cheers, Markus |
|
From: Jaime H. <hab...@gm...> - 2019-11-24 21:25:59
|
Are there plans to support Azure Key Vault for SignServer in a similar way that it is now being supported for EJBCA ( https://www.primekey.com/blog/2019/10/22/ejbca-on-azure-keyvault/)?. -- Jaime Hablutzel - +51 994690880 |
|
From: Markus K. <mar...@pr...> - 2019-09-26 14:41:15
|
Hi all, The PrimeKey SignServer team is pleased to announce the release of SignServer Community 5.2.0.Beta1. In total 18 tickets have been resolved since SignServer Enterprise 5.1.0 and 58 tickets since the last community version, highlights mentioned below. New Administration Web The SignServer Administration GUI (AdminGUI) has been replaced with a brand new Administration Web interface, previously only available in SignServer Enterprise. The improved and modern AdminWeb interface eases deploying SignServer by allowing using a Web browser for managing administration tasks instead of the standalone Java desktop application. PGP Signing Support In addition to the support of all X.509 based signers, we have now added support for PGP/GPG signing of software release packages and repositories, or for general signing. The new OpenPGP Signer can produce both detached and clear-text signatures. For step-by-step instructions on configuring and using this new signer, see https://doc.primekey.com/signserver/signserver-operations/setting-up-openpgp-signer. Upgrade Information For full details of fixed issues implemented in this release, refer to our JIRA Issue Tracker: https://jira.primekey.se/issues/?filter=14587 For upgrade instructions, review the https://doc.primekey.com/signserver/signserver-installation/upgrade-signserver About this Release This SignServer 5.2.0 Beta release is made available to allow you to test and evaluate the next version of SignServer. Please try out SignServer in your environment and help us make the next release the best ever by reporting issues and any feedback using the mailing list or discussion forums. For download link, documentation, and contact information for mailing list and discussion forums, see: https://www.signserver.org Best Regards, Markus Kilås, Product Owner SignServer on behalf of the PrimeKey SignServer Team |
|
From: Markus K. <mar...@pr...> - 2019-04-26 09:03:31
|
Hi all, The PrimeKey SignServer team is proud to announce the release of SignServer 5.0.0.Final Community edition. SignServer 5 is the next generation SignServer with 48 issues resolved since SignServer Enterprise 4.4.1 and a total of 415 issues resolved since SignServer Community edition 4.0. >From today you will be able to take advantage of the new server failover and load balancing functionality in the SignClient as well as leveraging the client side hashing feature for CMS/PKCS#7 detached signatures. In addition, with SignServer 5 we have done a major technology upgrade. Some more noteworthy updates are listed below: SignClient - Support for server failover and load balancing. - New feature to allow downloading SignClient in the same way as the Admin GUI. Signing - Support for hashing on the client side for CMS/PKCS#7 detached signatures. - Support for configurable content OID in CMS signatures. - Support for DER encoding of CMS signatures. - Performance: Option to disable request hashing in the Plain Signer. Time-stamping - Optional inclusion of IssuerSerial in SigningCertificate in Time- stamp tokens. - Legacy option to encode the time-stamp tokens as before Bouncy Castle 1.50. - Legacy option to not include the RFC#6211 cmsAlgorithmProtection attribute in the token. General - Support for running on WildFly 14 and JBoss EAP 7. - Support for running on Java 11. - Upgraded libraries and dependencies. - Stronger algorithms by default. - Restructured and improved documentation. The full list of fixed issues is available in the issue tracker: https://jira.primekey.se/issues/?filter=14492 For download link, documentation and contact information for mailing list and discussion forums, see: https://www.signserver.org Best Regards, Markus Kilås, Product Owner SignServer on behalf of the PrimeKey SignServer Team |
|
From: Markus K. <mar...@pr...> - 2019-03-06 16:39:47
|
Hi everyone, The PrimeKey SignServer team is pleased to announce the release of SignServer 5.0.0.Beta1 Community Edition. SignServer 5 is the next generation SignServer with 40 issues resolved since SignServer Enterprise 4.4.1 and a total of 407 issues resolved since SignServer Community Edition 4.0, some of the noteworthy listed below: General - Support for running on WildFly 14 and JBoss EAP 7. - Support for running on Java 11. - Upgraded libraries and dependencies. - Stronger algorithms by default. - Restructured and improved documentation. SignClient - Support for server failover and loadbalancing. - New feature to allow downloading SignClient in the same way as the Admin GUI. Signing - Support for hashing on the client side for CMS/PKCS#7 detached signatures. - Support for configurable content OID in CMS signatures. - Support for DER encoding of CMS signatures. - Performance: Option to disable request hashing in the Plain Signer. Time-stamping - Optional inclusion of IssuerSerial in SigningCertificate in Time-stamp tokens. - Legacy option to encode the time-stamp tokens as before Bouncy Castle 1.50. - Legacy option to not include the RFC#6211 cmsAlgorithmProtection attribute in the token. This SignServer 5.0.0 Beta release is made available to allow you to test and evaluate the next major version of SignServer. Please try out SignServer in your environment and help us make the next release the best ever by reporting issues and any feedback using the mailing list or discussion forums. The full list of fixed issues is available in the issue tracker: https://jira.primekey.se/issues/?filter=14491 For download link, documentation and contact information for mailing list and discussion forums, see: https://www.signserver.org Best Regards, Markus Kilås, Product Owner SignServer on behalf of the PrimeKey SignServer Team *Meet us at RSA Conference 2019* San Francisco, March 4-8 Booth #1935 FREE Expo pass code: XEU9PRIMEKEY |
|
From: Markus K. <mar...@pr...> - 2019-03-04 08:30:09
|
On 3/2/19 2:18 PM, Jaime Hablutzel wrote: > On Tue, Feb 26, 2019, 10:34 AM Markus Kilås <mar...@pr... > <mailto:mar...@pr...>> wrote: > > Hi, > > It has been a long time since the release of SignServer 4 and it is now > time for the next major version. > > SignServer 5 has been under development for some time and is progressing > well. > > Besides many of the updates that have already been released as part of > SignServer Enterprise Edition, the major news is the Technology Upgrade > with support for newer Java and application server versions. > > The plan is to have a pre-release available in the beginning of March > for anyone to try out. > > > Regards, > Markus Kilås > on behalf of the SignServer Team > > > _______________________________________________ > SignServer-develop mailing list > Sig...@li... > <mailto:Sig...@li...> > https://lists.sourceforge.net/lists/listinfo/signserver-develop > > Will SignServer CE support AWS CloudHSM as the Enterprise edition does?. > > Sent from Android. > Hi Jaime, That is not planned for 5.0. Actually, the integration with AWS CloudHSM requires a PrimeKey PKCS#11 module that is currently only available with SignServer Enterprise Cloud Edition: https://www.primekey.com/products/cloud/signserver-enterprise-cloud/ Cheers, Markus https://www.primekey.com *Meet us at RSA Conference 2019* San Francisco, March 4-8 Booth #1935 FREE Expo pass code: XEU9PRIMEKEY |
|
From: Markus K. <mar...@pr...> - 2019-02-26 15:34:42
|
Hi, It has been a long time since the release of SignServer 4 and it is now time for the next major version. SignServer 5 has been under development for some time and is progressing well. Besides many of the updates that have already been released as part of SignServer Enterprise Edition, the major news is the Technology Upgrade with support for newer Java and application server versions. The plan is to have a pre-release available in the beginning of March for anyone to try out. Regards, Markus Kilås on behalf of the SignServer Team |
|
From: Tomas G. <to...@pr...> - 2018-06-28 09:55:49
|
*Invitation to PrimeKey Tech Days 2018* 18 - 19 September, Stockholm Sweden We are happy to invite you to PrimeKey Tech Days 2018! PrimeKey Tech Days is our two day tech event featuring speakers in PKI, Crypto, Open Source, eIDAS, Digital Signing and many other interesting topics in IT-Security. https://www.primekey.com/tech-days/ *Join us and listen to distinguished speakers from:* - Google - Ericsson - Legion of the Bouncy Castle - Utimaco - DarkMatter - Siemens - InfoSec Global - Nimbus Technologieberatung GmbH - PrimeKey - ...and more *Develop both your skills and your network* PrimeKey Tech Days is a great chance to learn about what's new in the field, to get inspiration and to network with some of the best PKI, Crypto and IT-Security from around the globe. This is a hard core tech event, so you'll meet engineers, PKI experts, Solution Architects, Developers, and many more skilled IT-Security professionals from all types of companies and organizations. * * *Dinner and boat ride* The agenda on Tuesday includes an evening boat tour of scenic Stockholm, followed by dinner at Fotografiska with a spectacular view of the Stockholm seaside. Fotografiska has recently been awarded “The world’s best museum restaurant”. This evening activity is a great chance for you to expand your network, not only with PrimeKey but with IT-Security professionals from all over the globe. We look forward to seeing you in Stockholm! For continous updates, new speakers and more; follow us on LinkedIn and Twitter. https://www.linkedin.com/company/primekey-solutions-ab https://www.twitter.com/primekeyPKI! <https://www.twitter.com/primekeyPKI%21> We hope to see you in September! / The PrimeKey team Read more and Sign up: https://www.primekey.com/tech-days/ See the event film: https://youtu.be/lNK-w4uKs-E Best regards, *Tomas Gustavsson * -- PrimeKey *Follow PrimeKey* *https://www.linkedin.com/company/primekey-solutions-ab* https://www.twitter.com/primekeyPKI Find PrimeKey on AWS <https://aws.amazon.com/marketplace/seller-profile?id=7edf9048-58e6-4086-9d98-b8e0c1d78fce&ref=dtl_B078PLGJWL> |
|
From: Markus K. <mar...@pr...> - 2018-04-06 07:00:45
|
On 03/29/2018 05:15 PM, Jaime Hablutzel wrote: > What means the "pk1", "pk2", etc, suffix in SVN tags under this > URL, https://svn.cesecore.eu/svn/signserver/tags/?. > > Is it something like RC (release candidate)?. Hi Jaime, Yes, the "-pkX" releases are not official releases. They could be alpha, beta or release candidates. Note that the final release is without the "-pkX" suffix. Cheers, Markus PrimeKey Solutions Save time and money with an Enterprise support subscription. Please see www.primekey.com for more information. https://www.primekey.com/products/software/ |
|
From: Jaime H. <hab...@gm...> - 2018-03-29 15:15:49
|
What means the "pk1", "pk2", etc, suffix in SVN tags under this URL, https://svn.cesecore.eu/svn/signserver/tags/?. Is it something like RC (release candidate)?. Thanks. -- Jaime Hablutzel - RPC 994690880 |
8 messages has been excluded from this view by a project administrator.