yaws
yaws copied to clipboard
erlyaws
yaws_config.erl:2071: ssl:cipher_suites/0 is deprecated and will be removed in OTP 24; use use cipher_suites/2,3 instead
Compilation fails under OTP 23 with rebar3.
This is because of warnings_as_errors in erl_opts. Please consider remove warnings_as_errors which 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.
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 warnings_as_errors setting for years and it's not been a problem because we generally support the past five OTP releases, and so we test against all of them.
Maybe consider only setting the flag when running tests. It keeps getting in the way.
sorry... it is still a problem regardless of rebar. date Thu Aug 13 23:40:19 PDT 2020 autoreconf -fi ....... == yaws 2.0.7 ==
Configuration: Application dir.: ${ERLANG_INSTALL_LIB_DIR}/yaws-${YAWS_VSN}
Prefix: /usr/local etcdir: ${prefix}/etc confdir: $(sysconfdir)/yaws bindir: ${exec_prefix}/bin vardir: ${prefix}/var wwwdir: $(localstatedir)/yaws/www appsdir: $(localstatedir)/yaws logdir: $(localstatedir)/log/yaws yawsdir: $(libdir)/yaws docdir: ${datarootdir}/doc/${PACKAGE_TARNAME} mandir: ${datarootdir}/man
Erlang root dir: /usr/lib/erlang
Erlang lib dir: /usr/lib/erlang/lib
Erlang compiler: /usr/bin/erlc
Erlang emulator: /usr/bin/erl
Windows Erlang emulator:
Erlang interpreter: /usr/bin/escript
Erlang dialyzer tool: /usr/bin/dialyzer
Erlang ct_run tool: /usr/bin/ct_run
yaws-yaws-2.0.7]$ make
Making all in src
make[1]: Entering directory /home/sm/yaws/zip/yaws-yaws-2.0.7/src' GEN ../ebin/yaws.app GEN ../ebin/yaws.appup ERLC ../ebin/yaws.beam ERLC ../ebin/yaws_app.beam ERLC ../ebin/yaws_ticker.beam ERLC ../ebin/yaws_config.beam compile: warnings being treated as errors yaws_config.erl:2071: ssl:cipher_suites/0 is deprecated and will be removed in OTP 24; use use cipher_suites/2,3 instead make[1]: *** [../ebin/yaws_config.beam] Error 1 make[1]: Leaving directory /home/sm/yaws/zip/yaws-yaws-2.0.7/src'
make: *** [all-recursive] Error 1
erl Erlang/OTP 23 [erts-11.0.3] [source] [64-bit] [smp:1:1] [ds:1:1:10] [async-threads:1] [hipe]
Eshell V11.0.3 (abort with ^G)
uname -a Linux cent7-16 3.10.0-1127.18.2.el7.x86_64 #1 SMP Sun Jul 26 15:27:06 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Making all in src
make[1]: Entering directory /home/sm/yaws/zip/yaws-yaws-2.0.7/src' ERLC ../ebin/yaws_config.beam compile: warnings being treated as errors yaws_config.erl:2071: ssl:cipher_suites/0 is deprecated and will be removed in OTP 24; use use cipher_suites/2,3 instead make[1]: *** [../ebin/yaws_config.beam] Error 1 make[1]: Leaving directory /home/sm/yaws/zip/yaws-yaws-2.0.7/src'
make: *** [all-recursive] Error 1
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 https://github.com/erlyaws/yaws/compare/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 https://github.com/erlyaws/yaws/commit/c5aa1e300105578f3c3c025b367f4d2725ae5b5d
and I am obtaining zip source file there.
On Fri, Aug 14, 2020 at 9:10 AM Steve Vinoski [email protected] wrote:
If you're trying to build from a 2.0.7 tarball or tag, it won't work. You need commit 28eecfd https://github.com/erlyaws/yaws/commit/28eecfd1c65c369de5b4b99cea9407205bbe8f8e or newer.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/erlyaws/yaws/issues/401#issuecomment-674148408, 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 [email protected] wrote:
If you're trying to build from a 2.0.7 tarball or tag, it won't work. You need commit 28eecfd https://github.com/erlyaws/yaws/commit/28eecfd1c65c369de5b4b99cea9407205bbe8f8e or newer.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/erlyaws/yaws/issues/401#issuecomment-674148408, 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 [email protected] 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 https://github.com/erlyaws/yaws/commit/28eecfd1c65c369de5b4b99cea9407205bbe8f8e 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 https://github.com/erlyaws/yaws/issues/401#issuecomment-674166291, 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 [email protected] 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 https://github.com/erlyaws/yaws/issues/401#issuecomment-674168769, 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 [email protected] 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 [email protected] 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 https://github.com/erlyaws/yaws/issues/401#issuecomment-674168769, 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:
- Yaws documentation exists in two places in the source code: the manual pages directory and the LaTeX doc. 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. You can also search it to see if your problem has already been discussed.
- Sometimes you can find Yaws questions on Stack Overflow that are relevant to the issue you're having.
Thank you, Steve.
Regards, Slav
On Wed, Aug 26, 2020 at 7:15 AM Steve Vinoski [email protected] 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 https://github.com/erlyaws/yaws/issues/401#issuecomment-680907266, or unsubscribe https://github.com/notifications/unsubscribe-auth/AELNG4PWNGRQ7ZTD3WBDCPTSCUKJ5ANCNFSM4NASB3TA .