Add Support for OpenSSL 1.1.0 #1838
Comments
|
Yop I have exactly the same problem on Arch too. Since I'm only a beginner in Pony I don't need all that net stuff so I just removed it from the stdlib by commenting lines here and there, and It's working fine now. My /usr/lib/pony/0.13.1/packages/stdlib/_test.pony file looks like this currently : |
|
OpenSSL 1.1.0 is currently unsupported. You'd need an older, supported version. |
|
the changes to use openssl 1.1 are actually very few, however that code won't work with 1.0 |
jemc
changed the title
|
I ran into this while running the complete test suite. The SSL API changes are documented here: https://wiki.openssl.org/index.php/OpenSSL_1.1.0_Changes |
|
I make no claims this is correct and it may erase all of the data on your computer, but it looks to have worked for me. I came up with the change after looking at https://wiki.openssl.org/index.php/Library_Initialization and /usr/include/openssl/ssl.h crypto.h and evp.h. Which I applied on top of the PR #2303 changes and successfully compiled the stdlib tests: And ran them: |
|
Now that there is experimental support for 4.0.1 and 5.0.0 on master it would be nice to get openssl 1.1 support in also, expecially for Arch Linux which is using it as the default. So I need some advice on how to proceed. My current change, test-openssl1.1, is "working" for openssl 1.1.0 so I think the next step is to get it to work for openssl 1.0.2. What I think is needed is have some type of conditional compiliation. So maybe something like the following could be done in the effected packages. Here's what it might look like for packages/net/ssl/ssl_context.pony: @@ -18,11 +18,15 @@ class val SSLContext
new create() =>
"""
Create an SSL context.
"""
- _ctx = @SSL_CTX_new[Pointer[_SSLContext]](@SSLv23_method[Pointer[None]]())
+ ifdef OPENSSL_API_COMPAT_1_1_0
+ _ctx = @SSL_CTX_new[Pointer[_SSLContext]](@TLS_method[Pointer[None]]())
+ else
+ _ctx = @SSL_CTX_new[Pointer[_SSLContext]](@SSLv23_method[Pointer[None]]())
+ end
// set SSL_OP_NO_SSLv2
@SSL_CTX_ctrl(_ctx, 32, 0x01000000, Pointer[None])
// set SSL_OP_NO_SSLv3The problem is I'm not sure how to modify the Makefile to pass "-DOPENSSL_API_COMPAT_1_1_0" when compiling the modified files. Of course this maybe the totally wrong direction, so suggestions and other ideas welcome! |
|
@winksaville - do you need the conditional compilation to be resolved at compile time of the |
|
Needs to be done at compile time.
…On Tue, Nov 28, 2017, 1:56 PM Joe Eli McIlvain ***@***.***> wrote:
@winksaville <https://github.com/winksaville> - do you need the
conditional compilation to be resolved at compile time of the ponyc/
libponyrt binaries, or at compile time of the pony program (when ponyc is
run)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1838 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA-hHE3KSYlgeLnFdRHc1ClkoLBPeG9zks5s7IGVgaJpZM4M7_II>
.
|
|
@winksaville - sorry, which of the two compile times that I mentioned? 😄 |
|
Sorry miss read your question. When the files in my change are compiled:
winksaville@34535cf
packages/crypto
packages/net/ssl
…On Tue, Nov 28, 2017, 9:17 PM Joe Eli McIlvain ***@***.***> wrote:
@winksaville <https://github.com/winksaville> - sorry, which of the two
compile times that I mentioned? 😄
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1838 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA-hHCx3F0KZhYfGsYZ8ibcobEQCL7fOks5s7Oj5gaJpZM4M7_II>
.
|
|
@winksaville - I don't think modifying the If you want to have it decided forever when running |
|
Its not so much what I want, I'm just trying to allow a programmer to use
the pony crypto and ssl packages on systems that have openssl 1.1.
I think I need some more education about pony packages. I just realized
that it looks like packages are distributed as sources as I see on my Arch
Linux system /usr/lib/pony/0.20.0-4003.0b2a2d2/packages:
wink@wink-desktop:/usr/lib/pony/0.20.0-4003.0b2a2d2/packages
$ ls crypto
constant_time_compare.pony crypto.pony digest.pony hash_fn.pony
_test.pony
wink@wink-desktop:/usr/lib/pony/0.20.0-4003.0b2a2d2/packages
$ ls net/ssl
ssl_connection.pony ssl_context.pony _ssl_init.pony ssl.pony x509.pony
Is it correct that packages are distributed as sources?
In any case a short term problem I see is how to build and test pony on
systems that have openssl 1.1 such as Arch Linux? Right now you can build
ponyc on Arch Linux but the stdlib tests fail to link because
packages/net/ssl and packages/crypto expect openssl 1.0.0. So one solution
might be to use something like the my modifcations to the Makefile and pass
-DOPENSSL_API_COMPAT_X_X_X to the places where packages/stdlib is compiled.
So maybe something like below and then modifiy packages/crypto and
packages/net/ssl with appropriate "ifdef's" with the default path if
nothing is defined to assume openssl 1.0.0.
test: all
@$(PONY_BUILD_DIR)/libponyc.tests
@$(PONY_BUILD_DIR)/libponyrt.tests
@$(PONY_BUILD_DIR)/ponyc -D$(OPENSSL_API_COMPAT) -d -s --checktree --verify
packages/stdlib
@./stdlib --sequential
@rm stdlib
test-examples: all
@PONYPATH=. $(PONY_BUILD_DIR)/ponyc -D$(OPENSSL_API_COMPAT) -d -s
--checktree --verify examples
@./examples1
@rm examples1
test-ci: all
@$(PONY_BUILD_DIR)/ponyc --version
@$(PONY_BUILD_DIR)/libponyc.tests
@$(PONY_BUILD_DIR)/libponyrt.tests
@$(PONY_BUILD_DIR)/ponyc -D$(OPENSSL_API_COMPAT) -d -s --checktree --verify
packages/stdlib
@./stdlib --sequential
@rm stdlib
@$(PONY_BUILD_DIR)/ponyc -D$(OPENSSL_API_COMPAT) --checktree --verify
packages/stdlib
@./stdlib --sequential
@rm stdlib
@PONYPATH=. $(PONY_BUILD_DIR)/ponyc --D$(OPENSSL_API_COMPAT) d -s
--checktree --verify examples
@./examples1
@rm examples1
@$(PONY_BUILD_DIR)/ponyc --antlr > pony.g.new
@diff pony.g pony.g.new
@rm pony.g.new
docs: all
$(SILENT)$(PONY_BUILD_DIR)/ponyc packages/stdlib
-D$(OPENSSL_API_COMPAT) --docs --pass expr
$(SILENT)cp .docs/extra.js stdlib-docs/docs/
What do you think?
…On Wed, Nov 29, 2017 at 8:03 AM Joe Eli McIlvain ***@***.***> wrote:
@winksaville <https://github.com/winksaville> - I don't think modifying
the ponyc Makefile is what you want. The -D argument is going to have to
be passed every time the user runs ponyc to compiler their program, based
on which is available.
If you want to have it decided forever when running make for ponyc (the
compile time of ponyc), then you'd need to add some ponyint_* functions
in the C source for ponyc to wrap the incompatible calls in a C-level
#ifdef block.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1838 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA-hHAq5EM8OLVicFUHKT1-pubV1bt7Xks5s7YBYgaJpZM4M7_II>
.
|
Yeah, I think this is the key point - pony doesn't have any concept of a compiled package - only a compiled program. Packages are distributed as source code, and then the Pony compiler looks at all the source files at once and compiles the whole program. So every time you use the |
|
Hmm,
I modified the Makefile locally adding test-stdlib target where added
passing the -DOPENSSL_API_COMPAT_1_1_0:
test-stdlib: all
$(SILENT)$(PONY_BUILD_DIR)/ponyc -D$(OPENSSL_API_COMPAT) -d -s --checktree
--verify packages/stdlib
$(SILENT)./stdlib --sequential
$(SILENT)rm stdlib
And got a "not a valid platform flag":
Error:
/home/wink/prgs/pony/ponyc/packages/net/ssl/ssl_context.pony:23:11:
"OPENSSL_API_COMPAT_1_1_0" is not a valid platform flag
ifdef OPENSSL_API_COMPAT_1_1_0 then
^
So I can't have arbitrary "defines" or did I do something wrong?
…On Wed, Nov 29, 2017 at 11:14 AM Joe Eli McIlvain ***@***.***> wrote:
Is it correct that packages are distributed as sources?
Yeah, I think this is the key point - pony doesn't have any concept of a
compiled package - only a compiled program. Packages are distributed as
source code, and then the Pony compiler looks at all the source files at
once and compiles the whole program.
So every time you use the net/ssl package in your program, it will be
compiled, and any Pony-level ifdefs will be resolved at *that* time. So
you'd need to include the relevant -D flag when compiling your program.
The Makefile in this repo doesn't play any role in that process - it
would have to be in the invocation used by the user. Many Pony projects
include their own Makefile for passing any relevant flags to the Pony
compiler, and generally having more repeatable control over compilation.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1838 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA-hHMQlwmsWTVnA5Yi6eCYEYu1sFx1nks5s7a0mgaJpZM4M7_II>
.
|
|
I'm not sure it the correct solution but it works if the ifdef expression is a string: |
|
With my latest change I've successfully compiled ponyc and tested on both an Arch Linux system running openssl 1.1 and a Ubuntu 17.10 system running openssl 1.0.0 |
|
While i really like being able to compile pony programs against openssl 1.1.0 i dont like having to specify the flag everytime. Would it be possible to use https://www.openssl.org/docs/man1.1.0/crypto/OpenSSL_version.html to let ponyc create some builtin defines for the underlying libssl and/or libcrypto on which we can do the ifdef without having to specify it manually? The same as we have |
|
Just FYI, Windows currently uses LibreSSL 2.6.1. |
|
@mfelsche, just to be clear a -DOPENSSL_API_COMPAT_X_X_X is not need unless you need/want to use openssl 1.1. At the moment I'm unclear how wrapping in C code actually helps, it still seems there's a requirement for some compile time switchs be it in pony or in C code. I must be missing something. One thing I don't like about my code is in the constructors of digest.pony I duplicated the same code 7 times: I couldn't figure out how to create a method that I could call from a constructor, any suggestions? |
|
you can call methods from constructors once every field has been initialized. |
|
Ideally, this kind of issue would be handled by a better FFI, which would be able to parse C headers and conditionally compile code based on the defines in those headers. Until we have such an FFI (which is one of my mid-long term goals) I'm not sure what the right solution is. |
|
One option would be to simply not support the older version of OpenSSL. |
|
Given that the “older version” is widely available on many distros such as RedHat, not supporting it isn’t a user friendly choice and greatly reduces our reach. |
|
Seems plausible, if you can make it work. |
This resolves issue [ponylang#1838](ponylang#1838)
This resolves issue [ponylang#1838](ponylang#1838)
This resolves issue [ponylang#1838](ponylang#1838)
This resolves issue [ponylang#1838](ponylang#1838)
This resolves issue [ponylang#1838](ponylang#1838)
This resolves issue [ponylang#1838](ponylang#1838)
This resolves issue [ponylang#1838](ponylang#1838)
This resolves issue [ponylang#1838](ponylang#1838)
This resolves issue [ponylang#1838](ponylang#1838)
|
The basic issue that emerged with OpenSSL 1.1.0 is that the current FFI is not yet able to differentiate between libraries of different versions. As there are some incompatibilities between OpenSSL 1.0.X and 1.1.X we need to wrap the FFI calls in some conditional compilation statements and only use the 1.1.X API if we know we have it available. #2415 is fixing this problem for openssl 1.0.0 and 1.1.0 while introducing the burden on the application developer to define "OPENSSL_COMPAT_1_1_0" everytime when compiling his program in order to use the correct openssl version. The goal here should be to do the detection of the openssl version in the compiler, not the Makefile of the compiler only, in order to have such a conditional compilation but without the need to specify anything manually. There are some possible other solutions to this problem:
All three would avoid manual definition of a "OPENSSL_COMPAT_1_1_0" flag. But the effort is much higher for all three. |
|
Just a clarification, defining OPENSSL_API_COMPAT_1_1_0 is only needed to
support 1.1.0. To support the current 1.0.0 API's no define is needed. In
the future it would be deseriable to allow OPENSSL_API_COMPAT to be
assigned a value and then used in expressions based on "==" or comparisions
such as ">=". For instance OPENSSL_API_COMPAT=0x010100 for 1.1.0 or
OPENSSL_API_COMPAT=0x010000 for 1.0.0 API's. And then you should be able to
write code like "ifdef OPENSSL_API_COMPAT >= 0x010100 then ... end"
…On Wed, Dec 27, 2017 at 2:11 PM Matthias Wahl ***@***.***> wrote:
The basic issue that emerged with OpenSSL 1.1.0 is that the current FFI is
not yet able to differentiate between libraries of different versions. As
there are some incompatibilities between OpenSSL 1.0.X and 1.1.X we need to
wrap the FFI calls in some conditional compilation statements and only use
the 1.1.X API if we know we have it available.
#2415 <#2415> is fixing this
problem for openssl 1.0.0 and 1.1.0 while introducing the burden on the
application developer to define "OPENSSL_COMPAT_1_1_0" everytime when
compiling his program in order to use the correct openssl version. The goal
here should be to do the detection of the openssl version in the compiler,
not the Makefile of the compiler only, in order to have such a conditional
compilation but without the need to specify anything manually.
There are some possible other solutions to this problem:
- Have a use "lib:LIBRARY_NAME" statement that makes the library
version available to the code where it is used, maybe as an ifdef variable
- Improve the FFI to be able to read out #DEFINEs from C header files
and use them in pony code (in this case OPENSSL_VERSION_NUMBER)
- create an ifdef variable that is exposing which openssl is available
(e.b. openssl_1_0_0 and openssl_1_1_0). Here it should be made so that pony
applications that do not use ssl or crypto packages do not need to link
against libssl or libcrypto just for having this ifdef variable.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1838 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA-hHJ_SCfQaAe4K78TWZa28zB1yQSxfks5tEsCOgaJpZM4M7_II>
.
|
This resolves issue [ponylang#1838](ponylang#1838)
This resolves issue [ponylang#1838](ponylang#1838)
….1.0 if use=openssl_1.1.0 is passed on the make command line then the compile time define, -Dopenssl_1.1.0, is passed to the compiler when building the pony packages. Specifically there are ifdef "openssl_1.1.0" statements in packages/crypto and packages/net/ssl which assume the openssl 1.1.0 API's. To manually compile user programs that want to use openssl 1.1.0 pass -Dopenssl_1.1.0 on the ponyc command line. This resolves issue [ponylang#1838](ponylang#1838)
….1.0 To have the ponyc tests use openssl 1.1 you may need pass -Dopenssl_1.1.0 to the compiler. This may be accomplished using either of the two following command lines: make OPENSSL_1.1.0=-Dopenssl_1.1.0 test or make use=openssl_1.1.0 test Specifically there are ifdef "openssl_1.1.0" statements in packages/crypto and packages/net/ssl which can use the openssl 1.1.0 API's. To manually compile user programs that want to use openssl 1.1.0 pass -Dopenssl_1.1.0 on the ponyc command line. For instance to compile stdlib: ./build/release/ponyc -Dopenssl_1.1.0 packages/stdlib This resolves issue [ponylang#1838](ponylang#1838)
….1.0 To have the ponyc tests use openssl 1.1 you may need pass -Dopenssl_1.1.0 to the compiler. This may be accomplished using either of the two following command lines: make OPENSSL_1.1.0=-Dopenssl_1.1.0 test or make use=openssl_1.1.0 test Specifically there are ifdef "openssl_1.1.0" statements in packages/crypto and packages/net/ssl which can use the openssl 1.1.0 API's. To manually compile user programs that want to use openssl 1.1.0 pass -Dopenssl_1.1.0 on the ponyc command line. For instance to compile stdlib: ./build/release/ponyc -Dopenssl_1.1.0 packages/stdlib This resolves issue [ponylang#1838](ponylang#1838)
….1.0 To have the ponyc tests use openssl 1.1 you may need pass -Dopenssl_1.1.0 to the compiler. This may be accomplished using either of the two following command lines: make OPENSSL_1.1.0=-Dopenssl_1.1.0 test or make use=openssl_1.1.0 test Specifically there are ifdef "openssl_1.1.0" statements in packages/crypto and packages/net/ssl which can use the openssl 1.1.0 API's. To manually compile user programs that want to use openssl 1.1.0 pass -Dopenssl_1.1.0 on the ponyc command line. For instance to compile stdlib: ./build/release/ponyc -Dopenssl_1.1.0 packages/stdlib This resolves issue [ponylang#1838](ponylang#1838)
….1.0 To have the ponyc tests use openssl 1.1 you may need pass -Dopenssl_1.1.0 to the compiler. This may be accomplished using either of the two following command lines: make OPENSSL_1.1.0=-Dopenssl_1.1.0 test or make use=openssl_1.1.0 test Specifically there are ifdef "openssl_1.1.0" statements in packages/crypto and packages/net/ssl which can use the openssl 1.1.0 API's. To manually compile user programs that want to use openssl 1.1.0 pass -Dopenssl_1.1.0 on the ponyc command line. For instance to compile stdlib: ./build/release/ponyc -Dopenssl_1.1.0 packages/stdlib This resolves issue [ponylang#1838](ponylang#1838)
If your system has openssl 1.1.0 and you need to use the crypto or ssl packages you must define openssl_1.1.0 when invoking ponyc. Specifically, there are ifdef "openssl_1.1.0" statements in packages/crypto and packages/net/ssl which can use the openssl 1.1.0 API's. When compiling using ponyc/Makefile and targeting various tests you need to set OPENSSL=-Dopenssl_1.1.0. For instance, if targeting "test" the command line would be: make OPENSSL=-Dopenssl_1.1.0 test If you are compiling pony programs using ponyc in your own Makefile or directly on the command line and the program uses crypto or ssl then pass -Dopenssl_1.1.0 on the ponyc command line. For instance, to compile stdlib: ./build/release/ponyc -Dopenssl_1.1.0 packages/stdlib This resolves issue [ponylang#1838](ponylang#1838)
If your system has openssl 1.1.0 and you need to use the crypto or ssl packages you must define openssl_1.1.0 when invoking ponyc. Specifically, there are ifdef "openssl_1.1.0" statements in packages/crypto and packages/net/ssl which can use the openssl 1.1.0 API's. When compiling using ponyc/Makefile and targeting various tests you need to set OPENSSL=-Dopenssl_1.1.0. For instance, if targeting "test" the command line would be: make OPENSSL=-Dopenssl_1.1.0 test If you are compiling pony programs using ponyc in your own Makefile or directly on the command line and the program uses crypto or ssl then pass -Dopenssl_1.1.0 on the ponyc command line. For instance, to compile stdlib: ./build/release/ponyc -Dopenssl_1.1.0 packages/stdlib This resolves issue [ponylang#1838](ponylang#1838)
If your system has openssl 1.1.0 and you need to use the crypto or ssl packages you must define openssl_1.1.0 when invoking ponyc. Specifically, there are ifdef "openssl_1.1.0" statements in packages/crypto and packages/net/ssl which can use the openssl 1.1.0 API's. When compiling using ponyc/Makefile and targeting various tests you need to set OPENSSL=-Dopenssl_1.1.0. For instance, if targeting "test" the command line would be: make OPENSSL=-Dopenssl_1.1.0 test If you are compiling pony programs using ponyc in your own Makefile or directly on the command line and the program uses crypto or ssl then pass -Dopenssl_1.1.0 on the ponyc command line. For instance, to compile stdlib: ./build/release/ponyc -Dopenssl_1.1.0 packages/stdlib This resolves issue [ponylang#1838](ponylang#1838)
If your system has openssl 1.1.0 and you need to use the crypto or ssl packages you must define openssl_1.1.0 when invoking ponyc. Specifically, there are ifdef "openssl_1.1.0" statements in packages/crypto and packages/net/ssl which can use the openssl 1.1.0 API's. When compiling using ponyc/Makefile and targeting various tests you need to set OPENSSL=-Dopenssl_1.1.0. For instance, if targeting "test" the command line would be: make OPENSSL=-Dopenssl_1.1.0 test If you are compiling pony programs using ponyc in your own Makefile or directly on the command line and the program uses crypto or ssl then pass -Dopenssl_1.1.0 on the ponyc command line. For instance, to compile stdlib: ./build/release/ponyc -Dopenssl_1.1.0 packages/stdlib This resolves issue [ponylang#1838](ponylang#1838)
If your system has openssl 1.1.0 and you need to use the crypto or ssl packages you must define openssl_1.1.0 when invoking ponyc. Specifically, there are ifdef "openssl_1.1.0" statements in packages/crypto and packages/net/ssl which can use the openssl 1.1.0 API's. When compiling using ponyc/Makefile and targeting various tests you need to set OPENSSL=-Dopenssl_1.1.0. For instance, if targeting "test" the command line would be: make OPENSSL=-Dopenssl_1.1.0 test If you are compiling pony programs using ponyc in your own Makefile or directly on the command line and the program uses crypto or ssl then pass -Dopenssl_1.1.0 on the ponyc command line. For instance, to compile stdlib: ./build/release/ponyc -Dopenssl_1.1.0 packages/stdlib This resolves issue [ponylang#1838](ponylang#1838)
If your system has openssl 1.1.0 and you need to use the crypto or ssl packages you must define openssl_1.1.0 when invoking ponyc. Specifically, there are ifdef "openssl_1.1.0" statements in packages/crypto and packages/net/ssl which can use the openssl 1.1.0 API's. When compiling using ponyc/Makefile and targeting various tests you need to set OPENSSL=-Dopenssl_1.1.0. For instance, if targeting "test" the command line would be: make OPENSSL=-Dopenssl_1.1.0 test If you are compiling pony programs using ponyc in your own Makefile or directly on the command line and the program uses crypto or ssl then pass -Dopenssl_1.1.0 on the ponyc command line. For instance, to compile stdlib: ./build/release/ponyc -Dopenssl_1.1.0 packages/stdlib This resolves issue [ponylang#1838](ponylang#1838)
If your system has openssl 1.1.0 and you need to use the crypto or ssl packages you must define openssl_1.1.0 when invoking ponyc. Specifically, there are ifdef "openssl_1.1.0" statements in packages/crypto and packages/net/ssl which can use the openssl 1.1.0 API's. When compiling using ponyc/Makefile and targeting various tests you need to set OPENSSL=-Dopenssl_1.1.0. For instance, if targeting "test" the command line would be: make OPENSSL=-Dopenssl_1.1.0 test If you are compiling pony programs using ponyc in your own Makefile or directly on the command line and the program uses crypto or ssl then pass -Dopenssl_1.1.0 on the ponyc command line. For instance, to compile stdlib: ./build/release/ponyc -Dopenssl_1.1.0 packages/stdlib This resolves issue [ponylang#1838](ponylang#1838)
If your system has openssl 1.1.0 and you need to use the crypto or ssl packages you must define openssl_1.1.0 when invoking ponyc. Specifically, there are ifdef "openssl_1.1.0" statements in packages/crypto and packages/net/ssl which can use the openssl 1.1.0 API's. When compiling using ponyc/Makefile and targeting various tests you need to set OPENSSL=-Dopenssl_1.1.0. For instance, if targeting "test" the command line would be: make OPENSSL=-Dopenssl_1.1.0 test If you are compiling pony programs using ponyc in your own Makefile or directly on the command line and the program uses crypto or ssl then pass -Dopenssl_1.1.0 on the ponyc command line. For instance, to compile stdlib: ./build/release/ponyc -Dopenssl_1.1.0 packages/stdlib This resolves issue [ponylang#1838](ponylang#1838)
|
I think this can be closed now that #2415 has been merged. |
Currently when attempting to link
stdlib.oI get the following undefined reference errors:This is notably due to changes in OpenSSL 1.1.0 and its deprecation of these functions. For example
SSL_library_initis nowOPENSSL_init_ssl.Perhaps this mailing list post and its referenced links might be of use when figuring this out: https://www.mail-archive.com/[email protected]/msg36437.html
The text was updated successfully, but these errors were encountered: