The site is updated
4.1 binaries are restored
Thanks a lot for the help!
On Thu, 7 Feb 2019 at 23:31, wrote:
>
> OK, I see that the RC2 started in the same day as RC1 was cancelled so
> the dates do make sense.
>
> Sorry for the noise! :/
>
> Best regards.
>
> On 07/02/2019 16:13, thc...@gmail.c
The Apache Commons team is pleased to announce the release of Apache
Commons Collections 4.3. The release is available for download at
http://commons.apache.org/proper/commons-collections/download_collections.cgi
Apache Commons Collections is a project to develop and maintain
collection classes b
aremily commented on issue #92: OpenSSL 1.1.0 updates with backward
compatibility for OpenSSL 1.0.2 and 1.0.1
URL: https://github.com/apache/commons-crypto/pull/92#issuecomment-462013332
Travis is running OpenSSL 1.0.1, correct? I've been developing to 1.0.2
and 1.1.0. I'm guessing tha
aremily commented on issue #92: OpenSSL 1.1.0 updates with backward
compatibility for OpenSSL 1.0.2 and 1.0.1
URL: https://github.com/apache/commons-crypto/pull/92#issuecomment-462010162
It does. Thank you. I ran the build successfully with 1.1.0 on Mac OSX
and 1.0.2 on Ubuntu 16.04, b
I agree it would be best to have people watch the repos they're interested in.
If no one objects, I'll open an infra ticket to remove dev@ from
commons-crypto updates. (Will leave it to others to update other
repos.)
On Fri, Feb 8, 2019 at 1:57 PM Eric Barnhill wrote:
>
> Is it the consensus out
vanzin commented on a change in pull request #91: run time support is added for
openssl 1.0 and 1.1 for UNIX
URL: https://github.com/apache/commons-crypto/pull/91#discussion_r255248729
##
File path: src/main/native/org/apache/commons/crypto/OpenSslInfoNative.c
##
@@ -75,38
vanzin commented on a change in pull request #91: run time support is added for
openssl 1.0 and 1.1 for UNIX
URL: https://github.com/apache/commons-crypto/pull/91#discussion_r255250233
##
File path: src/main/native/org/apache/commons/crypto/cipher/OpenSslNative.c
##
@@ -43
vanzin commented on a change in pull request #91: run time support is added for
openssl 1.0 and 1.1 for UNIX
URL: https://github.com/apache/commons-crypto/pull/91#discussion_r255249458
##
File path: src/main/native/org/apache/commons/crypto/OpenSslInfoNative.c
##
@@ -75,38
Is it the consensus outcome for the dev list, that we all receieve a large
amount of GitBox postings? Wouldn't it be better to leave it to individuals
to track the projects they want to track? I know I do this.
Apologies if I missed any prior discussions.
Eric
vanzin closed pull request #90: commons-crypto OpenSSL's to support both 1.0
and 1.1
URL: https://github.com/apache/commons-crypto/pull/90
This is an automated message from the Apache Git Service.
To respond to the message,
vanzin commented on issue #90: commons-crypto OpenSSL's to support both 1.0
and 1.1
URL: https://github.com/apache/commons-crypto/pull/90#issuecomment-461959113
I assume this is superseded by #91.
This is an automated messag
vanzin closed pull request #79: Added Support for both OpenSSL version 1.0 and
1.1
URL: https://github.com/apache/commons-crypto/pull/79
This is an automated message from the Apache Git Service.
To respond to the message, pl
vanzin closed pull request #78: adding support for openssl 1.1.0g in common
crypto
URL: https://github.com/apache/commons-crypto/pull/78
This is an automated message from the Apache Git Service.
To respond to the message, pl
vanzin commented on issue #78: adding support for openssl 1.1.0g in common
crypto
URL: https://github.com/apache/commons-crypto/pull/78#issuecomment-461958902
I assume this is superseded by #91.
This is an automated message f
vanzin commented on issue #79: Added Support for both OpenSSL version 1.0 and
1.1
URL: https://github.com/apache/commons-crypto/pull/79#issuecomment-461958976
I assume this is superseded by #91.
This is an automated message f
rhenwood-arm commented on a change in pull request #91: run time support is
added for openssl 1.0 and 1.1 for UNIX
URL: https://github.com/apache/commons-crypto/pull/91#discussion_r255215704
##
File path: src/main/native/org/apache/commons/crypto/OpenSslInfoNative.c
##
@@
rhenwood-arm commented on a change in pull request #91: run time support is
added for openssl 1.0 and 1.1 for UNIX
URL: https://github.com/apache/commons-crypto/pull/91#discussion_r255216767
##
File path: src/main/native/org/apache/commons/crypto/cipher/OpenSslNative.c
##
rhenwood-arm commented on a change in pull request #91: run time support is
added for openssl 1.0 and 1.1 for UNIX
URL: https://github.com/apache/commons-crypto/pull/91#discussion_r255215438
##
File path: src/main/native/org/apache/commons/crypto/OpenSslInfoNative.c
##
@@
rhenwood-arm commented on a change in pull request #91: run time support is
added for openssl 1.0 and 1.1 for UNIX
URL: https://github.com/apache/commons-crypto/pull/91#discussion_r255217195
##
File path:
src/main/native/org/apache/commons/crypto/random/OpenSslCryptoRandomNative.c
rhenwood-arm commented on a change in pull request #91: run time support is
added for openssl 1.0 and 1.1 for UNIX
URL: https://github.com/apache/commons-crypto/pull/91#discussion_r255215197
##
File path: pom.xml
##
@@ -146,8 +146,8 @@ The following provides more details o
rhenwood-arm commented on a change in pull request #91: run time support is
added for openssl 1.0 and 1.1 for UNIX
URL: https://github.com/apache/commons-crypto/pull/91#discussion_r255214849
##
File path: pom.xml
##
@@ -116,7 +116,7 @@ The following provides more details o
rhenwood-arm commented on a change in pull request #91: run time support is
added for openssl 1.0 and 1.1 for UNIX
URL: https://github.com/apache/commons-crypto/pull/91#discussion_r255216439
##
File path: lib/include/config.h
##
@@ -24,7 +24,8 @@
#elif defined(MAC_OS)
luyseyal commented on issue #36: [CSV-234] Add support for java.sql.Clob
URL: https://github.com/apache/commons-csv/pull/36#issuecomment-461918544
:100:
This is an automated message from the Apache Git Service.
To respond to
-1
It hangs on my machine when built from the git tag:
mvn -version
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-17T19:33:14+01:00)
Maven home: /usr/local/apache-maven-3.5.4
Java version: 1.8.0_191, vendor: Oracle Corporation, runtime:
/usr/lib/jvm/java-8-openjdk-amd6
Le ven. 8 févr. 2019 à 12:36, sebb a écrit :
>
> -1 to the release:
The Javadoc does not mention that "SecureRandom" is used
by default.
And... where is the branch?
Gilles
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apac
I’m a -1 as well. I have some ideas here and will wok on those going forward.
-Rob
> On Feb 8, 2019, at 6:41 AM, Gary Gregory wrote:
>
> Whatever we do, let's document it as best we can in places users will find
> it.
>
> Gary
>
>> On Fri, Feb 8, 2019, 06:36 sebb >
>> -1 to the release:
>> I
Whatever we do, let's document it as best we can in places users will find
it.
Gary
On Fri, Feb 8, 2019, 06:36 sebb -1 to the release:
> I don't think we can release the code as is; it is bound to cause
> significant delays on some systems.
>
> I think we need to establish whether using 'new Sec
-1 to the release:
I don't think we can release the code as is; it is bound to cause
significant delays on some systems.
I think we need to establish whether using 'new SecureRandom()'
instead of SecureRandom.getInstanceStrong() makes the long delays go
away.
Then we need to establish whether we
On Fri, Feb 8, 2019, 03:58 Gilles Sadowski Hello Bruno.
>
> Le ven. 8 févr. 2019 à 02:54, Bruno P. Kinoshita a
> écrit :
> >
> > Hi,
> >
> > Had a bit of spare time to investigate this one (almost end of Friday
> for me anyway, hooray!).
> >
> > There are two unit tests in Sha512 hanging for me i
Le ven. 8 févr. 2019 à 11:24, Bruno P. Kinoshita a écrit :
>
> Ah, good point. If you prefer to use the gitbox interface, it's available
> here too.
>
> https://gitbox.apache.org/repos/asf?p=commons-codec.git;a=blob;f=src/main/java/org/apache/commons/codec/digest/B64.java;h=4396eccbb8021164340341
Ah, good point. If you prefer to use the gitbox interface, it's available here
too.
https://gitbox.apache.org/repos/asf?p=commons-codec.git;a=blob;f=src/main/java/org/apache/commons/codec/digest/B64.java;h=4396eccbb80211643403419b22715b033015e452;hb=1884dc028bce8094e8ddd7a9fc192a107a64527a#l77
T
Hi.
Le ven. 8 févr. 2019 à 10:13, Bruno P. Kinoshita a écrit :
>
> Hi Gilles,
> Sorry, forgot to mention I was talking about the code in the tag for the
> release.
The link which I provided is also supposed to be the
code-to-be-released (branch "1_12").
Incriminated code does not appear there.
Hi Gilles,
Sorry, forgot to mention I was talking about the code in the tag for the
release.
The random is created here
https://github.com/apache/commons-codec/blob/1884dc028bce8094e8ddd7a9fc192a107a64527a/src/main/java/org/apache/commons/codec/digest/B64.java#L77
And used here
https://github.c
Hello Bruno.
Le ven. 8 févr. 2019 à 02:54, Bruno P. Kinoshita a écrit :
>
> Hi,
>
> Had a bit of spare time to investigate this one (almost end of Friday for me
> anyway, hooray!).
>
> There are two unit tests in Sha512 hanging for me in Eclipse,
> testSha512CryptExplicitCall and testSha512Cryp
34 matches
Mail list logo
