I want to check that a dll is an implementation of pkcs11 version 2.20 or other version. So I find what are difference between pkcs11 version 2.20 and others (specialy version 2.30). Could you give me some suggest?
Thanks in advance!
As per this link
Version 2.30 This is the draft of the v2.30 version of the standard. The RSA PKCS#11 development process did not move this beyond
draft despite the 30 day public final draft review ending 28-Oct-2009.
Many vendors have adopted various portions of the draft version.
This version is the basis of the v2.40 OASIS standard version.
Version 2.20 Published 28 June 2004 this is the most widely used version of the PKCS#11 standard. Most supporting vendors have versions
with various vendor-specific extensions based on v2.20.
And regarding the version, you can use the CK_VERSION to find out the PKCS#11 Implementation version, more [here].
Related
I'd like to use some new features of Dymola 2022, but the commercial library I use runs on Modelica Standard Library 3.2.3(MSL), so I have to replace the Design Library, Optimization Library, etc. with the older version. In the document of Dymola 2022, it gives information about using an older version of MSL, but not the other libraries. My question is:
Is it compatible between Dymola 2022 and the older version of all these libraries?
I have not tried in Dymola 2022, but in Dymola 2021x it was possible to still use MSL 3.2.3 by doing these steps:
Copy the 3.2.3 version of MSL and other libraries from either the .zip installer or from an older Dymola installation to "C:\Program Files\Dymola 2021x\Modelica\Library" or 2022 instead of 2021x.
Change the setting in Dymola as shown below.
If this does not work, please contact your Dymola reseller, they can probably help to get MSL3 running also in Dymola 2022.
As discussed in the comments, parts of TPL are encrypted, so unfortunately you cannot run the conversion script yourself. The next release of TPL is expected in January 2022 and will be based on MSL4 (all Modelon commercial libraries will be based on MSL4 only). If it is urgent to update to MSL4 you can request an alpha version based on MSL4 today, but Modelon is only giving limited support for intermediate versions. Official releases see extended testing. If you are interested, please contact support#modelon.com
Alternatively, you can update your commercial libraries to MSL 4.0.0 and save the converted libraries to a new location. Dymola usually suggests the conversion when you load the libraries.
The newest AnyLogic version is not supported by my current AnyLogic license. The license only supports up to 8.3.3. However, I do wish to install AnyLogic on another computer and activate it with my license. However, surprisingly I could not find downloads of earlier AnyLogic versions. Does anyone know if and where I can find these earlier versions, and whether I perhaps can downgrade a newer AnyLogic version?
https://www.anylogic.com/files/anylogic-professional-8.3.3.exe
For any version, just put the version you want and you will likely be able to download it
if using mac:
https://www.anylogic.com/files/anylogic-professional-8.3.3.dmg
In addition to Felipe's answer, you can always ask
support#anylogic.com
if you need very old versions. I believe that AL7.x is not available online anymore but they happily send the installers if you need them.
We are planning to use Drools in our organisation with Scala/Spark. We have selected Drools Version 5.3.0 and 7.15.0 for our use but we have some stability doubts between them because Version 7.15.0 has recently launched & we are not sure whether it is stable or not.
We have practiced with Version 5.3.0 but we want to know the life cycle of it. What if after some time, Version 5.3.0 will not available for use or some update is brought for this?
So please help us to chose between them which version should we chose for longer use.
Drools 5.3 is outdated version and its not under development. Its better you go with latest release.Drools 7.15 is also stable, but if you are planning to use it for business critical application then I will recommend you to go with enterprise release of Drools 7.x , i.e Red Hat Decision Manager. With enterprise release will get patches for known issue on regular basis and one-off patch for critical issues.
We are considering the adoption of a library to generate and use JSON Web Tokens. Jose4j seems a good choice but library "Dependencies" state that "...Jose4j is compiled with/for Java 7 and will also run on Java 8..." and our current instalation run on Java 6 version (migration to higher versions is out of our reach), so our question is simple.
Is there any chance to integrate Jose4j with Java 6? (not at all, with some limitations, can be achieved in any way by adding some specific libraries, etc.)
Thanks in advance
Getting jose4j to run on Java 6 is (probably) possible but will require recompilation and some code changes.
There have been a couple forks of somewhat older versions that I believe have back-ported to compile and run with Java 6 - https://bitbucket.org/yosef_kitrossky/jose4j-jdk1.6/commits/all is the most recent that I know about and there's also https://bitbucket.org/ijazfx/jose4j/commits/all
You could probably do a back-port of the latest too without too much trouble. The code base uses some multi-catch, diamond, and try-with-resources syntax that will need to be converted to the pre Java 7 equivalents. Somewhat tedious perhaps but not rocket surgery. There are also some algorithms that won't work. Some might just not be available at runtime and some, like all the AES-GCM related bits, will need to be removed from the code to get it to compile.
You'll also want to have the JCE Unlimited Strength Jurisdiction Policy File(s) in place as some of the unit tests use AES keys that are larger than 128 bits http://www.oracle.com/technetwork/java/javase/downloads/jce-6-download-429243.html
I hope this helps. Unfortunately, I just don't have bandwidth to maintain a Java 6 compatible version myself.
Nimbus JOSE + JWT have support for Java 6 since 4.11.1 version.
From documentation, you just need inform the classifier in the dependency:
<dependency>
<groupId>com.nimbusds</groupId>
<artifactId>nimbus-jose-jwt</artifactId>
<classifier>jdk16</classifier>
<version>[ version ]</version>
</dependency>
You can find the available versions here.
This seems like a very basic question, but I searched high and low and have found almost no mention of it anywhere. So, I'll ask it here here.
What is the current plan for supporting Java 8's new language constructs in GWT?
In addition, what subset of the proposed Java 8 libraries are slated for client-side emulation? The Stream API? The new Date/Time API?
And finally, where are the discussions relating this important topic taking place? I'm sure there are many of us who would like to participate in, and potentially contribute to, the effort.
The Java 8 betas have been around for a while now, and there are numerous articles discussing the proposed APIs. It is supposed to be related later this year, so it seems past time to at least be discussing how and when the much-desired language features will make their way into GWT.
My apologies if this question is answered somewhere else, or if I missed some important piece of information related to it. This would be a great place to have a link to such information, even if it has been answered. Thanks!
EDIT GWT 2.8.0 was released on Oct 20, 2016 with support for Java 8 language constructs (lambdas, method references) and emulation of some Java 8 APIs (streams mostly)
EDIT as of Apr 2014, GWT 2.6 supports Java 7, and work is underway to support Java 8 in GWT 2.7, to be released by the summer 2014. GWT 2.7 is likely to only support Java 8 language constructs though, and not emulate any new API (streams, javax.time, etc.)
The plan is to first support Java 7: https://github.com/gwtproject/gwt/labels/java7
This involves updating JDT, and this is being worked on (or alternatively, switch to something else entirely; JetBrains proposed using their parser which already supports Java 8, but GWT also needs a compiler and I don't know what they provide exactly). The next steps are to map new language constructs to JavaScript (strings-in-switch come to mind, as they could directly map to JavaScript without the hashCode-based desugaring that a Java compiler would be doing).
As long as GWT uses JDT for its Java parsing/munging/compiling, Java 8 can only be supported when JDT will support it (at an acceptable level, which is not yet the case AFAICT).
Time to update the answer.
UPDATE (May 13, 2020)
GWT 2.9.0 finally here. Release notes
Able to compile projects with jsinterop-base 1.0.0, elemental2 1.0.0, and jsinterop-annotations 2.0.0. With the exception of #JsAsync and #JsEnum, this brings GWT2 to be compatible across these tools with J2CL.
Added support for Java language levels 9, 10, and 11.
Officially, support is dropped for running the GWT compiler or server-side tooling on Java 7. The GWT distribution is still compiled to run on Java 7 for this release, but no guarantees are made about whether or not this will work. Future versions will compile bytecode for Java 8+. The release was tested and found to work cross platform when run with Java 8, 11, and 14.
UPDATE (October 2017)
GWT 2.8.2 available here. Release notes.
UPDATE (June 2017)
Official GWT 2.8.1 download location.
Release Notes for 2.8.1
UPDATE (October 2016)
GWT 2.8.0 is finally here!
The GWT team has released the 2.8.0 tag on Github. The official GWT website has not been updated yet, but a pull request for the changes on GWT's website is ready and in review process. So very very soon the compiled version will be available for download!
Available for download
UPDATE (September 2016)
Meanwhile, team GWT has tagged GWT 2.8.0 RC3 on GitHub mirror.
The GWT team (Daniel Kurka) has released the GWT 2.8.0 (RC2) version here.
The release notes are available for 2.8.0 (RC2):
Bug fixes
Fix incorrect unusable-by-js warning.
Fix an issue around DevMode server (jetty) restart.
Fix an issue in super dev mode with changing compiler options not triggering full recompiles.
Added missing command line parameters to DevMode entry point
Fixed a performance regression in String.
The release notes from RC1 are available on official website. Here are the most important changes regarding Java 8 support in the upcoming GWT 2.8.0:
Highlights
Partial support for Java 8 standard library APIs (see below for full list).
Fix memory leak with Java 8 compilation.
Source level set to Java 8.
Static and default methods in interfaces aren’t visible to generators. If you want to take advantage of those Java-8isms, you’re encouraged to switch to an annotation processor. This could break existing build if an interface is changed to turn a non-default method into a default method.
JDK 8 emulation support
Emulate java.io.UncheckedIOException.
Emulate Optional and its int, long, double variants.
Emulate Objects.requireNonNull() with message Supplier.
Fix Math.min/max(float/double) emulation behavior.
Emulate Character.isBmpCodePoint().
Emulate CharSequence.chars().
Emulate java.lang.SecurityException.
Emulate Java 8 API of
java.util.Arrays,
java.util.ArrayDeque,
java.math.BigInteger,
java.util.BitSet,
java.util.Comparator,
java.util.function,
java.util.Iterator,
java.lang.Iterable,
java.util.IntSummaryStatistics/LongSummaryStatistics/DoubleSummaryStatistics
java.util.Collection/Lists/Queues,
java.util.Map,
java.util.logging.Logger,
java.util.PrimitiveIterator,
java.util.Spliterator,
java.util.stream,
java.util.StringJoiner
The GWT 2.8.0 RC2 still has some issues, which the GWT team is expected to fix soon. The final release should be coming out soon ("as soon as it is ready").