e352
Cipher AES/CTR/NoPadding instance created OK:
org.apache.commons.crypto.cipher.OpenSslCipher@673c4f6e
On Tue, Nov 14, 2023 at 8:27 AM sebb wrote:
> On Tue, 14 Nov 2023 at 13:17, Alex Remily wrote:
> >
> > That's fantastic. I read that there were big API changes with the move
>
That's fantastic. I read that there were big API changes with the move to
OpenSSL 3, but maybe those changes were not in the functionality that
commons crypto exposes. Have you merged into master yet? I look forward
to playing around with it.
Alex
On Wed, Nov 8, 2023 at 7:12 PM sebb wrote:
Or something else?
> >
> > Note I am not suggesting dropping support for 1.1.0 yet, but for
> > versions before that, i.e. 1.0.x.
> >
> > > Gary
> > >
> > > On Sun, Oct 29, 2023 at 8:49 PM Alex Remily
> wrote:
> > > >
> > > &g
Does anyone have a working debug config for the commons-crypto project? I
had one for Eclipse a few years ago but I blew it away and now recreating
it is getting to be a time sink. I'm looking to be able to step from the
Java code to the native code. I use Eclipse, but I'm also comfortable with
I believe it is for cross compilation, owing to the comments in the
makefile:
# for cross-compilation on Ubuntu, install the g++-mingw-w64-x86-64 package
# for cross-compilation on Ubuntu, install the g++-arm-linux-gnueabi package
# for cross-compilation on Ubuntu, install the
The supported architectures documentation is limited to the discussion on
this distribution list. At least, that's my recollection and
understanding. I agree that this should be documented at least in the
release notes and web site. Users shouldn't need to crack open the jar to
figure that out.
Good question. I've asked it myself. I've been planning on doing an
upgrade to support OpenSSL 3.X.+ that maintains support for 1.1.X. That
said, it's been at least a year and I haven't gotten around to it, and I'm
not firmly committed to the idea of maintaining backwards compatibility. I
How to reproduce these test failures?
On Sat, Sep 9, 2023 at 12:33 PM sebb wrote:
> Some of the test runs fail when testing with the class:
>
> org.apache.commons.crypto.jna.OpenSslJna
>
> It looks like all the OSes complete the test OK if the default JNA
> library is used.
>
> However for some
Gary,
Can you have a look at this?
https://github.com/apache/commons-crypto/pull/242
Alex
On Sun, Aug 27, 2023 at 8:38 AM Gary Gregory wrote:
> On Fri, Aug 25, 2023 at 9:48 PM Alex Remily wrote:
> >
> > Breakup
> > the current module into different maven modu
/source/
Thoughts?
Alex
On Sun, Aug 27, 2023 at 8:38 AM Gary Gregory wrote:
> On Fri, Aug 25, 2023 at 9:48 PM Alex Remily wrote:
> >
> > Breakup
> > the current module into different maven modules? Not support both?>
> >
> > Agreed. Just to provide some hist
:21 PM Gary Gregory
wrote:
> That would be great. I think this is worth the effort. A big item to
> consider is if and how 1.1 vs 3.0 should be handled. Breakup the current
> module into different maven modules? Not support both?
>
> Gary
>
> On Wed, Aug 23, 2023, 8:37
Implementing the OpenSSL 3 API and exposing OpenSSL HMAC functionality in
commons-crypto are things I've wanted to engage on for a while now. I was
involved in the commons-crypto OpenSSL 1.1.x upgrade so I have some
familiarity with the code base, albeit dated. The reason that neither the
I've been meaning to add openssl3 support to common crypto for a while
now. Maybe this will give me the push that I need. I'm on my phone now
without access to the branch, but I recall a docker file that provided a
lot of build information on the main branch. You may consider having a
look if
Gary,
A few years ago I migrated commons crypto onto Java 11 in my local
environment. I haven't kept the code, but it wasn't a heavy lift and I'm
happy to do it again for the community version. Let me know how you'd like
me to proceed.
Alex
On Sun, Apr 23, 2023 at 9:47 AM Gary Gregory wrote:
Please remind me how the vote process works. Do I just reply to this email?
On Fri, Jan 20, 2023 at 7:01 AM Gary Gregory wrote:
> We need more reviews and votes please.
>
> Gary
>
> On Tue, Jan 17, 2023, 10:12 Gary Gregory wrote:
>
> > Ping to PMC members.
> >
> > Gary
> >
> > On Sat, Jan 14,
lInfoNative.c#L74
> >
> > It might also help to remove the global flag to avoid re-exports?
>
> Not sure that would make a difference here.
>
> > Whats the lib filename constant in above line in your case?
> >
> > Gruss
> > Bernd
> > --
> >
I tinkered with the same issues today and have come to the
same conclusion. We may want to consider optionally prepending a path to
the COMMONS_CRYPTO_OPENSSL_LIBRARY to specify a specific libcrypto.
On Thu, Jun 30, 2022 at 5:35 PM sebb wrote:
> On Thu, 30 Jun 2022 at 16:21, Alex Remily wr
ski
wrote:
> Le jeu. 30 juin 2022 à 23:35, sebb a écrit :
> >
> > On Thu, 30 Jun 2022 at 16:21, Alex Remily wrote:
> > >
> > > > > loading the dll, whereas Java apparently does not.>
> > >
> > > I experience the same behavior. Wha
idea why yet, but it behaves differently from basically the same
> code when run via JNI.
>
> For example, the standalone code takes note of LD_LIBRARY_PATH when
> loading the dll, whereas Java apparently does not.
>
> On Thu, 30 Jun 2022 at 13:22, Alex Remily wrote:
> >
> >
/local/Cellar/openjdk@8/1.8.0+322/include" -O2 -fPIC
> > > > -mmacosx-version-min=10.7 -fvisibility=hidden -I/usr/local/include
> > > > -I/usr/local/opt/openssl/include -Ilib/include -I/usr/include
> > > > -I"/usr/local/Cellar/openjdk@8
> /1.8.0+322/lib
urrently use a small proportion of them.
> > > > >
> > > > > > I have not followed all the branches and commits, so I'm not
> sure what
> > > > > the
> > > > > > current problems are, but I know I was able to release all OSs
> last go
> &
ether this needs to
> be done for the current or a later release. If we don't fix this
> release, obviously it needs some mention in the release notes.
>
> Sebb
> https://github.com/apache/commons-crypto/actions/runs/2586011129
> > Gary
> >
> > On Wed, Jun 29, 20
How do we do release planning here? I think the next major release should
support OpenSSL 3.0.X and 1.1.1x and perhaps include Blake2 hash, but I
don't know how to have that conversation in the Apache governance model.
On Wed, Jun 29, 2022 at 7:02 AM sebb wrote:
> Seems to me we should
I agree with Gary that we just don't support LibreSSL. To my knowledge
we've never advertised LibreSSL support, so I don't see it as an issue.
On Wed, Jun 29, 2022 at 10:21 AM sebb wrote:
> On Wed, 29 Jun 2022 at 14:17, Gary Gregory wrote:
> >
> > The simple solution is to keep doing what we
21 Jun 2022 at 22:32, Alex Remily wrote:
> >
> > previous
> > submission.>
> >
> > Don't know that it's an "improvement", but a different approach. I think
> > if we provide a dockerfile that builds every supported arch (minus the
> Mac)
Then I was definitely looking at the wrong version of your file. I'll
circle back and run it again.
On Tue, Jun 21, 2022 at 5:52 PM sebb wrote:
> On Tue, 21 Jun 2022 at 22:32, Alex Remily wrote:
> >
> > previous
> > submission.>
> >
> >
n Tue, Jun 21, 2022 at 4:23 PM sebb wrote:
> On Tue, 21 Jun 2022 at 20:00, Alex Remily wrote:
> >
> > I went ahead and submitted a PR related to this discussion. The
> dockerfile
> > does a full build, minus the Mac, and should simplify the release
> process.
>
> N
so in
this PR.
Alex
https://github.com/apache/commons-crypto/pull/166
On Mon, Jun 20, 2022 at 10:24 AM sebb wrote:
> On Mon, 20 Jun 2022 at 14:35, Alex Remily wrote:
> >
> > Sebb,
> >
> > I cloned your repo and ran the dockerfile. Feedback:
> >
>
Sebb,
I cloned your repo and ran the dockerfile. Feedback:
The Maven download link is broken. It appears Apache updated to 3.8.6 on
the 17th. I think the 3.6.3 build is less likely (although still not
certain--as you pointed out) to get overwritten.
RUN wget
I've gone back and forth on that question myself. My initial instinct was
to advocate dropping the 32 bit Windows support, but since then I've come
to the opinion that Commons Crypto should support 32 bit Windows as long as
OpenSSL still does. There's minimal effort required to maintain
Yeah. There's a couple tickets that could probably be subsumed by a new
one. I'll have a look.
On Thu, Jun 16, 2022 at 8:04 PM Gilles Sadowski
wrote:
> Hello.
>
> Le jeu. 16 juin 2022 à 19:36, Alex Remily a écrit
> :
> >
> > Do you think we could simply u
sing route.
Thanks again for taking the time to provide feedback.
Alex
On Thu, Jun 16, 2022 at 2:48 PM sebb wrote:
> On Thu, 16 Jun 2022 at 18:21, Alex Remily wrote:
> >
> > Forwarding to the community dev list. Didn't realize it was dropped along
> > the way.
> >
I think that's a great idea, assuming as Gary pointed out that using a
MacVM for the build is legal (and I can't imagine AWS offering that service
if it wasn't). Use the MacVM as the host OS. Run the Mac build locally,
then run the dockerfile for the balance of the builds. The Windows and
Linux
as well as a flexible environment for targeted
builds.
Thoughts?
On Thu, Jun 16, 2022 at 1:58 PM sebb wrote:
> On Thu, 16 Jun 2022 at 18:18, Alex Remily wrote:
> >
> > I just ran [2], and whatever it does, it doesn't appear to do a build of
> > commons-crypto.
>
>
, and instructions.]
>
> Thanks,
> Gilles
>
> Le jeu. 16 juin 2022 à 19:18, Alex Remily a écrit
> :
> >
> > I just ran [2], and whatever it does, it doesn't appear to do a build of
> > commons-crypto. I'd appreciate it if any developers who have the time
>
Forwarding to the community dev list. Didn't realize it was dropped along
the way.
Alex
-- Forwarded message -
From: Alex Remily
Date: Thu, Jun 16, 2022 at 1:01 PM
Subject: Re: [Crypto] What is it ?
To: Jochen Wiedmann
Jochen,
Please give my attempt at a docker build a try
I just ran [2], and whatever it does, it doesn't appear to do a build of
commons-crypto. I'd appreciate it if any developers who have the time
would take a look at the dockerfile here:
https://github.com/aremily/commons-crypto
If you're copying the dockerfile into your own fork, you'll need the
Interesting. Since I just finished up writing yet a third dockerfile, I'll
try running both of them and see what happens. Hopefully, one of them was
used to perform the last release and we can just update the build
documentation to reflect.
On Thu, Jun 16, 2022 at 1:00 PM sebb wrote:
> As the
Currently, all a user needs to do to use commons-crypto is to include it as
a dependency in an application that runs on a supported operating system
with a supported version of OpenSSL (1.0 and 1.1). Commons-crypto
dynamically, and IMO quite elegantly, determines the underlying OS and
OpenSSL
Since we're talking about exposing new functionality, there's been a major
new OpenSSL release since our last release, so we should probably discuss
putting support for it on our roadmap, along with exposing
additional APIs. I'd like to add support for Blake2 in the next release,
and I'm happy to
As a user and past contributor, my view of Commons Crypto is that it is a
Java wrapper around certain common features of OpenSSL, full stop. As
such, it provides near-native performance to the Java developer for
processor-intensive operations via a Java API. It is a set of tools for
developing
I agree that a Docker build is a good idea. In fact, I *thought* the
project already had a Dockerfile from the release process for 1.1.0. I'm
certain that at least one contributor created one, but apparently it never
made the baseline. I don't recall if it was actually used to build the
If you actually don't have OpenSSL installed you can get it from the
website https://www.openssl.org/source/.
On Thu, May 5, 2022 at 4:24 PM Jochen Wiedmann
wrote:
> Hi,
>
> trying to run the unit tests for commons-crypto, I get the error message
>
> Native library is not loaded
>
> I
What version of OpenSSL do you have installed and how are you running the
unit tests, e.g., are you using the command line, maven, an integrated IDE
test runner, etc?
On Thu, May 5, 2022 at 4:24 PM Jochen Wiedmann
wrote:
> Hi,
>
> trying to run the unit tests for commons-crypto, I get the error
ry Gregory
> > > > Gesendet: Sunday, February 28, 2021 2:45:26 PM
> > > > An: Commons Developers List
> > > > Betreff: Re: [crypto] Interest in adding support for cryptographic
> hash function?
> > > >
> > > > That sounds reasonable to me.
I'd be exposing additional elements of the OpenSSL API via additions to the
commons crypto API. Since I wouldn't be adding any additional
dependencies, I would expect that licensing and portability would remain
unchanged. Would it not?
Thanks,
Alex
On Sat, Feb 27, 2021 at 1:08 PM Gilles
I'm working on a project that makes heavy use of hashing, and I'd like to
use the OpenSSL implementation. Thoughts on adding support for the SHA-2
and/or Blake2 family into commons crypto? I'm happy to do the work if
there's someone out there willing to review and advise.
Alex
Every time I've received a licence error working on the crypto project it
was because I was missing the Apache license in the source header. That
seemed the most likely scenario here.
On Sun, Nov 22, 2020 at 11:22 AM sebb wrote:
> On Sun, 22 Nov 2020 at 13:39, Alex Remily wrote:
> >
Paste the license into the source file. Check out any other source for an
example.
On Sun, Nov 22, 2020 at 8:33 AM Arturo Bernal
wrote:
>
> Hi All,
>
>
> Ii'm trying to do some change in commons crypto project but i always get
> the following error-> "Too many files with unapproved license"
>
e, Sep 1, 2020, 15:32 Geoffrey Blake
> wrote:
>
> > Yes, thanks everyone for helping. Was a long journey to get here.
> >
> > On Tue, Sep 1, 2020 at 11:32 AM Alex Remily wrote:
> >
> > > Thank you to everyone involved for their part in getting this out.
Thank you to everyone involved for their part in getting this out.
On Tue, Sep 1, 2020 at 11:58 AM Gary Gregory wrote:
>
> This VOTE passes with the following +1s:
>
> - Alex Remily
> - Geoffrey Blake
> - Bruno P. Kinoshita, binding
> - Rob Tompkins, binding
> - Gary Gr
arted with the ASF helping with vote threads, documentation issues,
> and slowly got used to the code base, to the process and how to contribute.
> So it's also a good way to get to know others here and get involved.
>
> Cheers
> Bruno
>
>
>
>
> On Tuesday, 1 Septemb
What are the voting requirements? Do you need to be an Apache member,
committer, contributor, etc?
On Mon, Aug 31, 2020 at 9:02 PM Gary Gregory wrote:
>
> May I have PMC reviews please?
>
> Gary
>
> On Fri, Aug 28, 2020 at 4:35 PM Gary Gregory wrote:
>
> > We have fixed quite a few bugs and
+1
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec
Java version: 1.8.0_241, vendor: Oracle Corporation, runtime:
/Library/Java/JavaVirtualMachines/jdk1.8.0_241.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
Gary,
Should we note something about the backwards compatibility with
OpenSSL 1.0.2? The way I read the docs now suggests that Commons
Crypto 1.0 supports OpenSSL 1.0.2 and that Commons Crypto 1.1 supports
OpenSSL 1.1.x. In fact, the Commons Crypto 1.1 build supports OpenSSL
1.0.2+, 1.1.0 and
directory, though, which
fixed the issue, but I agree this is a limitation. A user should be
able to run more than one instance of libcrypto on the same host. I'm
unsure as to the best way to proceed.
On Thu, Aug 27, 2020 at 6:41 PM Gary Gregory wrote:
>
> On Mon, Aug 24, 2020 at 7:28 PM Alex
Gary Gregory wrote:
>
> Here is what community testing we have so far for the Crypto.main() smoke
> test:
>
> - darwin64-x86_64-cc; OpenSSL 1.1.1g; Gary Gregory, Alex Remily
> - debian-amd64; OpenSSL 1.0.1f; Gary Gregory
> - debian-amd64; OpenSSL 1.1.1g; Bruno P. Kinoshita
>
s.crypto.Crypto.main(Crypto.java:144)
>
> Same issue with using -cp target/commons-crypto-1.1.0-SNAPSHOT.jar instead
> of target/class which is not a surprise.
>
> Which version of LibreSSL do you use?
>
> Gary
>
>
> > -Geoff
> >
> > On Sun, Aug 23, 2020
Bruno,
Are you certain that OpenSSL isn't installed on your Windows box?
It's supposed to fail before it looks for "OpenSSL_version" if there's
no OpenSSL installed.
Alex
On Tue, Aug 25, 2020 at 2:37 AM Bruno P. Kinoshita wrote:
>
> Hi Gary,
>
> I did a mvn clean test install from master, and
;/usr/local/Cellar/openssl@1.1/1.1.1g/lib/engines-1.1"
Alex
On Sun, Aug 23, 2020 at 9:50 PM Gary Gregory wrote:
>
> I do have LibreSSL but I used homebrew to install OpenSSL 1.1.1g which I
> put first on the PATH. Maybe something is off in my setup...
>
> Gary
>
> On
the PATH. Maybe something is off in my setup...
>
> Gary
>
> On Sun, Aug 23, 2020, 21:46 Alex Remily wrote:
>
> > Gary,
> >
> > I'll have a look. I did the 1.1 support stuff and I'm familiar with
> > that class and that error, although I don't recall seeing
>
> Gary
>
> On Sun, Aug 23, 2020, 21:46 Alex Remily wrote:
>
> > Gary,
> >
> > I'll have a look. I did the 1.1 support stuff and I'm familiar with
> > that class and that error, although I don't recall seeing that
> > specific error in that class. The
Gary,
I'll have a look. I did the 1.1 support stuff and I'm familiar with
that class and that error, although I don't recall seeing that
specific error in that class. The JNI libraries check the OpenSSL
version at runtime, but maybe a compile time dependency got through.
Out of curiosity, I
Gary,
I can test the 64 bit Mac, Windows and Linx builds this week. Did you
want to include this test fix in the snapshot:
https://issues.apache.org/jira/browse/CRYPTO-149
There's a pending PR with the fix. It's only one line of code so it
should merge easily.
In the past I've had some
>>>>
> >>>>>>>>
> >>>>>>>>> On Aug 6, 2020, at 10:33 AM, Matt Sicker wrote:
> >>>>>>>>>
> >>>>>>>>> Now I hope we don't have unit tests depending on non-static state
> >>>>>>>
Gilles is quite good at writing such tests.
> > > >>
> > > >> -Rob
> > > >>
> > > >>> I'd expect a crypto library's test
> > > >>> suites to include several hard-coded known-good and known-bad
> > > >>&g
No problem. I'll do it when I get home tonight.
On Thu, Aug 6, 2020, 8:25 AM Gary Gregory wrote:
> Hi Alex,
>
> Would you mind creating that ticket with that info?
>
> Thank you,
> Gary
>
> On Thu, Aug 6, 2020, 08:10 Alex Remily wrote:
>
> > That is an inter
That is an intermittent issue that I haven't been able to reliably
reproduce. As I recall, the test that's failing is supposed to fail, but
in a different way. I think it's supposed to fail because of a short
buffer but occasionally fails because of an internal error, and when that
happens this
grated into
> Maven for automating these releases that someone knows offhand?
>
> -Geoff
>
> On Fri, Jul 24, 2020 at 7:50 PM Alex Remily wrote:
> >
> > Sounds like a great idea.
> >
> > On Fri, Jul 24, 2020, 8:29 PM Marcelo Vanzin wrote:
> >
> &
y
> and call docker to build all the others.
>
> On Fri, Jul 24, 2020 at 5:04 PM Alex Remily wrote:
> >
> > I'd recommend using MinGW. I installed it through brew on my Mac and
> cross
> > compiled the windows build with little difficulty. I expect a similar
> > expe
> get
> > > > up and running minimally on Ubuntu:
> > > >
> > > > sudo apt-get install build-essential g++-mingw-w64
> > > > gcc-aarch64-linux-gnu libc6-dev-i386
> > > > sudo apt-get install libssl-dev git
> > > > sudo add-apt-r
Gary,
I compiled the 64-bit Windows build on my Mac and tested it in a
Windows VM. It was fairly straightforward with mingw. I still need
to cross-compile the Linux builds, but I'm cautiously optimistic that
they will be trivial compared to the Windows cross compilation.
Everything is easier on
For those of us not as familiar with Gradle, what are some of the
benefits? Drawbacks?
On Thu, Jul 16, 2020 at 5:30 PM Rob Tompkins wrote:
>
> I think we might be coming towards time to make this move or at least
> accommodate for gradle builds in commons. Let’s look to the success the
>
; and saw this above the win64 target:
>
> # for cross-compilation on Ubuntu, install the g++-mingw-w64-x86-64 package
>
> We could potentially build everything but MacOS on 1 Ubuntu 16.04LTS
> box. Or even a 14.04 box if necessary. Anybody have the time to try?
>
> On Thu, Jun 2
t.
>
> On Sat, Jun 13, 2020 at 6:14 PM Xeno Amess wrote:
> >
> > I have a feeling about both mingw or cygwin build output will be slower
> > than microsoft-visual-studio build output...
> > Just a feeling, but no evidence.
> >
> > Alex Remily 于2020年6月14
> >
> > Gary
> >
> > On Sat, Jun 13, 2020, 18:02 Alex Remily wrote:
> >
> > > I can't speak to how the original developers did the build, but all
> > > the Windows builds that I did were on a Windows machine. I always
> > > assumed that th
r package:
> > >
> > > [INFO] --- maven-antrun-plugin:1.8:run (make) @ commons-crypto ---
> > > [INFO] Executing tasks
> > >
> > > make:
> > > [exec] make native CROSS_PREFIX=aarch64-linux-gnu- OS_NAME=Linux
> > > OS_ARCH=aarch64
>
Just checking in on the status of the 1.1 release.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
So I did a little homework and JNA appears to be a first class citizen
in Commons Crypto. One instantiates a JNA-backed CryptoCipher just as
one does JNI or JCE. The OpenSslJna class is exposed for that
purpose. I hacked together the below from some JNA test classes to
demonstrate and it runs
st on my Mojave MacOS install, libreSSL is
> found and links fine with JNI. JNA is the library that fails to load
> on macOS, but that is apparently ok as the JNA implementation is not
> used by anything user accessible.
>
> -Geoff
>
> On Mon, Apr 27, 2020 at 7:53 AM Alex Remil
ue
> than just Travis, as the Travis Mac environment is fairly standard.
>
> On Mon, 27 Apr 2020 at 14:53, Alex Remily wrote:
> >
> > Adam,
> >
> > Fair points. I don't know if commons-crypto "officially" supports
> > LibreSSL, but now that I thi
inks fine with JNI. JNA is the library that fails to load
> on macOS, but that is apparently ok as the JNA implementation is not
> used by anything user accessible.
>
> -Geoff
>
> On Mon, Apr 27, 2020 at 7:53 AM Alex Remily wrote:
> >
> > Adam,
> >
> > Fair p
Adam,
Fair points. I don't know if commons-crypto "officially" supports
LibreSSL, but now that I think about it, it may be a moot point. As
long as LibreSSL complies with the OpenSSL 1.0 or 1.1 API, it *should*
run. It did compile and build against LibreSSL on the Mac, and the
tests didn't
> > release (which I assume there is) - then you could have the release
> > > > binaries built and delivered automatically for you. It is possible to
> > > > go as far as having them uploaded to Maven Central (staging) if you
> > > > wished.
> > &
red automatically for you. It is possible to
> > > > go as far as having them uploaded to Maven Central (staging) if you
> > > > wished.
> > > >
> > > > On Sat, 18 Apr 2020 at 17:40, Adam Retter <
> adam.ret...@googlemail.com> wrote:
>
wrote:
> >
> > Adding OpenSSL 1.1.x for x64, arm64, and ppc64le, turned out to be
> > trivial so I just pushed it now in an additional commit to the same
> > PR.
> >
> > On Sun, 19 Apr 2020 at 15:19, Alex Remily wrote:
> > >
> > > Makes sens
t be too bad. Depends on what packages are prebuilt and available
> > - I can take a look later
> >
> > On Sun, 19 Apr 2020, 04:43 Alex Remily, wrote:
> >
> >> Thanks Adam. Very much appreciated. How much effort would it be to do
> >> the
> >> same f
13 Apr 2020 at 16:35, Alex Remily wrote:
> >
> > I don't know whether it would help the build manager with the release
> > process, but I think it would be a good idea to update the build matrix
> > regardless. I made an attempt a while ago to add coverage for more
>
I've seen the expected exception error, but rarely and I've never been able
to reproduce it. I'm surprised it's come up on Travis because it's only
come up a few times for me in the hundreds of builds I've done. Maybe we
log it as a bug just to document it, but like I said, I don't know how to
m64 and Mac. I could setup a job to build binaries on
> Travis and keep a copy either on every commit or when a tag is created.
> Would that be helpful?
>
> On Mon, 13 Apr 2020, 03:13 Gary Gregory, wrote:
>
> > On Sun, Apr 12, 2020 at 8:57 PM Alex Remily
> wrote:
> >
I can do the 64 bit builds on Mac, Linux and Windows, so I'm happy to
provide whichever of those is required. It seems that Geoff can do the
arm64 build. Do we even bother supporting 32 bit architectures at this
point?
On Sun, Apr 12, 2020 at 7:36 PM Marcelo Vanzin wrote:
> Hi Gary,
>
> On
vate Build, runtime:
> /usr/lib/jvm/java-8-openjdk-amd64/jre
> Default locale: en, platform encoding: UTF-8
> OS name: "linux", version: "4.4.0-43-microsoft", arch: "amd64", family:
> "unix"
>
> Thanks!
> Gary
>
>
&
is welcome or a message here confirming that all JIRAs listed on
> > https://issues.apache.org/jira/projects/CRYPTO/versions/12335578 are
> > indeed in git master. Then I can update the changes.xml if no one
> submits a
> > PR.
> >
> > Gary
> >
> >
>
listed on
> https://issues.apache.org/jira/projects/CRYPTO/versions/12335578 are
> indeed in git master. Then I can update the changes.xml if no one submits a
> PR.
>
> Gary
>
>
> >
> >
> > On Fri, Apr 10, 2020 at 5:02 PM Gary Gregory
> > wrote:
>
Disregard. I figured it out.
On Fri, Apr 10, 2020 at 9:17 PM Alex Remily wrote:
> Gary,
>
> I don't have access to the page at the link. Can you add me?
> Sorry, you can't view this page
> This page is only available to Jira Software users. If you think you
> should be a
1.0 here:
> https://issues.apache.org/jira/projects/CRYPTO/versions/12335578
>
> These are all marked as resolved. Can you confirm that these indeed all
> are?
>
> TY,
> Gary
>
>
> >
> > On Thu, Apr 9, 2020 at 8:45 PM Alex Remily
> wrote:
> >
> >>
Commons Crypto Team,
It's been four years since the last release of commons crypto. There have
been many updates to the repository since then, notably the integration of
OpenSSL 1.1.1, and native arm64 support. Geoff Blake (copied) and I have
been advocating for a new release, and we need
Thanks for the links. I'll do just that.
On Wed, Apr 8, 2020 at 7:46 PM Gilles Sadowski wrote:
> Hi.
>
> 2020-04-09 1:15 UTC+02:00, Alex Remily :
> > I guess we're both in the same boat.
>
> Did you try and ping the people[1] (or their respective project[2])
> who contr
t; On Tue, Apr 7, 2020 at 8:43 PM Alex Remily wrote:
> >
> > I think most of the original developers have moved on. I did some of the
> > recent updates surrounding 1.1.1 support, and Marcelo was a big help
> > throughout the process. He established design goals, reviewed
I think most of the original developers have moved on. I did some of the
recent updates surrounding 1.1.1 support, and Marcelo was a big help
throughout the process. He established design goals, reviewed code,
provided tips, etc. I haven't seen him around in a while though, and I'm
not sure
1 - 100 of 116 matches
Mail list logo
