yaws_config.erl:2071: ssl:cipher_suites/0 is deprecated and will be removed in OTP 24; use use cipher_suites/2,3 instead #401
Comments
|
Yes, thanks, already working on it. Unfortunately this issue did not show up in the 23.0 release candidates, only in the 23.0 final release. We've had the |
|
Maybe consider only setting the flag when running tests. It keeps getting in the way. |
|
I just removed |
|
Thanks a lot for the quick fix. |
|
sorry... it is still a problem regardless of rebar. Configuration: Prefix: /usr/local Erlang root dir: /usr/lib/erlang yaws-yaws-2.0.7]$ make |
|
erl Eshell V11.0.3 (abort with ^G) |
|
uname -a |
|
Run |
|
Making all in src |
|
If you're trying to build from a 2.0.7 tarball or tag, it won't work. You need commit 28eecfd or newer. |
|
Hi,
I actually go to this url:
https://github.com/erlyaws/yaws/releases/tag/yaws-2.0.7
which says:
Yaws 2.0.7 <https://github.com/erlyaws/yaws/releases/tag/yaws-2.0.7>
[image: @vinoski] <https://github.com/vinoski> vinoski
<https://github.com/vinoski> released this on Jul 14, 2019 · 25 commits
<yaws-2.0.7...master> to master
since this release
version 2.0.7
yaws-2.0.7 <https://github.com/erlyaws/yaws/tree/yaws-2.0.7>
c5aa1e3
<c5aa1e3>
and I am obtaining zip source file there.
…On Fri, Aug 14, 2020 at 9:10 AM Steve Vinoski ***@***.***> wrote:
If you're trying to build from a 2.0.7 tarball or tag, it won't work. You
need commit 28eecfd
<28eecfd>
or newer.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#401 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AELNG4KJLUETM4XOQ2WZTELSAVOYFANCNFSM4NASB3TA>
.
|
|
Yaws 2.0.7 was released over a year ago. It preceded Erlang/OTP version 23.0 by nearly a year. It therefore doesn't support 23.0 or newer. You can use version 22.x with Yaws 2.0.7. If you require 23.0, then you will have to clone the Yaws repo and use it at commit 28eecfd or newer. Work on the next Yaws release, 2.0.8, is ongoing, and it'll include 23.0 support, but it's not yet ready. |
|
Hi Steve,
I made the following changes and it compiles fine (well, one test fails,
and I think, for the same reason, so, can be fixed the same way).
src/yaws_config.erl
%Ciphers = ssl:cipher_suites(),
Ciphers = ssl:cipher_suites(all, 'tlsv1.3'), (line 2071)
testsuite/dhfile_SUITE.erl
ssl_with_valid_dhfile(Config) ->
%SslOpts = [{ciphers, [C || {dhe_rsa, _, _}=C <- ssl:cipher_suites()]}],
SslOpts = [{ciphers, [C || {dhe_rsa, _, _}=C <- ssl:cipher_suites(all,
'tlsv1.3')]}],
ssl_with_invalid_dhfile(Config) ->
%SslOpts = [{ciphers, [C || {dhe_rsa, _, _}=C <- ssl:cipher_suites()]}],
SslOpts = [{ciphers, [C || {dhe_rsa, _, _}=C <- ssl:cipher_suites(all,
'tlsv1.3')]}],
…On Fri, Aug 14, 2020 at 9:10 AM Steve Vinoski ***@***.***> wrote:
If you're trying to build from a 2.0.7 tarball or tag, it won't work. You
need commit 28eecfd
<28eecfd>
or newer.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#401 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AELNG4KJLUETM4XOQ2WZTELSAVOYFANCNFSM4NASB3TA>
.
|
|
I see.
Thank you, Steve.
…On Fri, Aug 14, 2020 at 9:52 AM Steve Vinoski ***@***.***> wrote:
Yaws 2.0.7 was released over a year ago. It preceded Erlang/OTP version
23.0 by nearly a year. It therefore doesn't support 23.0 or newer. You can
use version 22.x with Yaws 2.0.7.
If you require 23.0, then you will have to clone the Yaws repo and use it
at commit 28eecfd
<28eecfd>
or newer. Work on the next Yaws release, 2.0.8, is ongoing, and it'll
include 23.0 support, but it's not yet ready.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#401 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AELNG4LQOMNQXUFSNB63RDTSAVTV7ANCNFSM4NASB3TA>
.
|
|
As for your suggested fix, the code has to work on Erlang/OTP versions 18.0 through 23.x. I believe what you're suggesting would work only on 23.x. |
|
erlang website doc says:
Lists all possible cipher suites corresponding to Description that are
available. The exclusive option will exclusively list cipher suites
introduced in Version whereas the the other options are inclusive from the
lowest possible version to Version. The all options includes all suites
except the anonymous.
…On Fri, Aug 14, 2020 at 9:58 AM Steve Vinoski ***@***.***> wrote:
As for your suggested fix, the code has to work on Erlang/OTP versions
18.0 through 23.x. I believe what you're suggesting would work only on 23.x.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#401 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AELNG4LXK3ZZDUHR2RHXTG3SAVUL7ANCNFSM4NASB3TA>
.
|
|
Hi Steve,
I am sorry to bug you with it, but I am trying to replace my apache with
yaws server. I am reading whatever documentation I could get, but, it seems
to me it is not really up to date.
I spent about a week trying to build/install it on Centos 7. It was not
straightforward, but I eventually managed to build and install it.
I then spent some time trying to figure out how to run it. Again,
unfortunately the documentation I have is not very clear and sometimes
controversial.
Now, when I got it up and running (though it will need to be revisited, as
I am running it as root, which is not a good thing to do), I started trying
to have yaws running a website, which is a typical php/mysql site.
I could not find any clear explanations on how php stuff should be
configure in yaws.conf
all I found so far is this:
https://thestaticvoid.com/post/2009/08/04/replacing-apache-with-yaws/
which is pretty old.
Does any place exist where I could get some more or less clear
documentation on how to handle configuration of yaws?
I am sorry, if what I am asking sounds silly - I am myself pretty new to
erlang - I am dealing with language for about 5-6 month. But I absolutely
fell in love with this language.
I wrote a small program in Erlang to deal with my 3 models and produce
G-code for the CNC machine out of it. and I did it in python (which I
honestly hate for its weird approach of major versions incompatibility). I
also have that same program (well with almost the same functionality)
written in C. But, after I tried Erlang I realized that the performance of
the Erlang program is pretty much like pure C, (which I cannot say about
Python). Coding in Erlang is absolute pleasure (even though I am very far
from what Joe called beautiful codding).
So, my experience with Erlang is not that extensive, so perhaps my question
about yaws configuration and its adaptation to PHP is quite silly and
totally wrong...
Anyway, if you know/can point me to any documentation, which could help to
adapt my php/mysql written site to yaws - I would very much appreciate that.
... or are you tempted to say - I will have to rewrite the entire website
for it? (I mean I understand I will need to modify certain parts of it to
embed out/1 function... anything else? to get it running?)
Regards,
Slav.
…On Fri, Aug 14, 2020 at 10:00 AM sma ***@***.***> wrote:
erlang website doc says:
Lists all possible cipher suites corresponding to Description that are
available. The exclusive option will exclusively list cipher suites
introduced in Version whereas the the other options are inclusive from
the lowest possible version to Version. The all options includes all
suites except the anonymous.
On Fri, Aug 14, 2020 at 9:58 AM Steve Vinoski ***@***.***>
wrote:
> As for your suggested fix, the code has to work on Erlang/OTP versions
> 18.0 through 23.x. I believe what you're suggesting would work only on 23.x.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#401 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AELNG4LXK3ZZDUHR2RHXTG3SAVUL7ANCNFSM4NASB3TA>
> .
>
|
|
@slavamas Your comment isn't relevant to this issue, so I'd prefer to not continue this conversation here. I suggest the following:
|
|
Thank you, Steve.
Regards,
Slav
…On Wed, Aug 26, 2020 at 7:15 AM Steve Vinoski ***@***.***> wrote:
@slavamas <https://github.com/slavamas> Your comment isn't relevant to
this issue, so I'd prefer to not continue this conversation here. I suggest
the following:
- Yaws documentation exists in two places in the source code: the
manual pages directory
<https://github.com/erlyaws/yaws/tree/master/man> and the LaTeX doc
<https://github.com/erlyaws/yaws/blob/master/doc/yaws.tex>. You can
build the latter to a pdf file if you have the right tools installed. The
documentation is all up to date.
- If you don't find the information you're seeking in that
documentation, please raise a new issue.
- For general questions or help, please use the Yaws mailing list
<https://sourceforge.net/p/erlyaws/mailman/erlyaws-list/>. You can
also search it to see if your problem has already been discussed.
- Sometimes you can find Yaws questions on Stack Overflow
<https://stackoverflow.com/questions/tagged/yaws> that are relevant to
the issue you're having.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#401 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AELNG4PWNGRQ7ZTD3WBDCPTSCUKJ5ANCNFSM4NASB3TA>
.
|
Compilation fails under OTP 23 with rebar3.
This is because of
warnings_as_errorsinerl_opts. Please consider removewarnings_as_errorswhich is a mistake. That flag only makes sense in development and does the wrong thing almost in every other situation, for example when pulled in as a dep.The text was updated successfully, but these errors were encountered: