Hi Matt and community,
Have you take a look at my work? If so, what do you think?
Best regards,
rodde
to 23.6.2022 klo 19.06 Matt Juntunen kirjoitti:
> Hello,
>
> Thanks for providing the data here. I will hopefully have time to take
> a look at this over the weekend. Send me a ping here on
We have fixed quite a few bugs and added some significant enhancements
since Apache Commons Configuration 2.7 was released, so I would like
to release Apache Commons Configuration 2.8.0.
Apache Commons Configuration 2.8.0 RC3 is available for review here:
The only OpenSSL fork I know of in macOS is BoringSSL which is also used by
Chrome. This fork maintains some level of compatibility though.
—
Matt Sicker
> On Jun 29, 2022, at 20:03, Alex Remily wrote:
>
> Which Mac OS version did you use? Since I upgraded to BigSur (OS 11) my
> Commons
Which Mac OS version did you use? Since I upgraded to BigSur (OS 11) my
Commons Crypto builds fail. I think Apple moved a bunch of the developer
libraries, but I haven't taken the time to troubleshoot.
On Wed, Jun 29, 2022 at 8:55 PM Gary Gregory wrote:
> Arg, idiotic line wrapping removed:
Arg, idiotic line wrapping removed: https://pastebin.com/raw/nPczrrd8
Gary
On Wed, Jun 29, 2022 at 8:49 PM Gary Gregory wrote:
>
> FWIW, I just checked out the rel/commons-crypto-1.1.0 on macOS and ran
> 'mvn clean verify' and everything built just fine.
>
> The Maven ant-run output was:
>
>
FWIW, I just checked out the rel/commons-crypto-1.1.0 on macOS and ran
'mvn clean verify' and everything built just fine.
The Maven ant-run output was:
[INFO] --- maven-antrun-plugin:1.8:run (make) @ commons-crypto ---
[INFO] Executing tasks
make:
[exec]
I agree with Alex.
Forget LibreSSL. Commons Crypto is for OpenSSL, nice, simple, and
tight. Last time I checked I had an antique version of LibreSSL on my
mac years ago, I just installed OpenSSL and never looked back.
Gary
On Wed, Jun 29, 2022 at 8:11 PM Alex Remily wrote:
>
> issues with JNA
I wouldn't characterize the issues running against LibreSSL as
"undetected". I also don't see this as an issue with Mac or Windows, but
with LibreSSL. Install any supported OpenSSL library on any supported
architecture (to include Mac and Windows) and all commons crypto
functionality is
Hello,
I don’t really understand why we “must” support libreSSL. I mean it is good if
we would support multiple implementations to cater for a wider audience, but if
commons-crypto requires a certain OpenSSL library and if that library is
available for all platforms, why not.
Integrators (aka
On Wed, 29 Jun 2022 at 18:06, Gary Gregory wrote:
>
> We cannot remove support for Windows and macOS, that's silly.
AFAICT that means we must support the different set of function names
in LibreSSL.
Note that we only currently use a small proportion of them.
> I have not followed all the
An important aspect to consider is compatibility, we do not want to break
anything within a major version.
Gary
On Wed, Jun 29, 2022, 11:15 Alex Remily wrote:
> 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
We cannot remove support for Windows and macOS, that's silly.
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
around. I don't see why we need to rip out anything as fundamental.
Gary
On Wed, Jun
On Wed, 29 Jun 2022 at 16:11, Alex Remily wrote:
>
> 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.
In that case AFAICT we will have to drop *all* support for macOS and
Windows, as they both seem
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
On Wed, 29 Jun 2022 at 14:17, Gary Gregory wrote:
>
> The simple solution is to keep doing what we do now: only support OpenSSL
> and not whatever Apple does with LibreSSL which may or may not be up to
> date.
I think this also affects Windows.
I don't have Windows box at present, but I have
The simple solution is to keep doing what we do now: only support OpenSSL
and not whatever Apple does with LibreSSL which may or may not be up to
date.
Gary
On Wed, Jun 29, 2022, 06:59 sebb wrote:
> It looks like macOS 10.5+ and Windows (latest) use LibreSSL by default
> rather than OpenSSL.
>
Deprecation seems ok, just make sure the deprecations are documented with
any replacement or explanation.
Gary
On Wed, Jun 29, 2022, 07:02 sebb wrote:
> Seems to me we should deprecate the code that supports OpenSSL 1.0.x
> for the next release.
>
> Then drop it at the first proper opportunity
Seems to me we should deprecate the code that supports OpenSSL 1.0.x
for the next release.
Then drop it at the first proper opportunity (major release?)
Agreed?
Sebb
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
It looks like macOS 10.5+ and Windows (latest) use LibreSSL by default
rather than OpenSSL.
The LibreSSL API does not have the same functions as either 1.0.2 or
1.1.1, so needs its own JNA class. In particular it looks like
ENGINE_load_rdrand is not present, nor is OpenSSL_version_num; 1.0.2
has
20 matches
Mail list logo
