Simple-Web-Server - Revision history

M: /* Repo usage */

2019-01-18T21:06:46Z

Repo usage

← Older revision		Revision as of 21:06, 18 January 2019
Line 11:		Line 11:
	🌵 m@bitpost [~/development/Libraries/c++/Simple-Web-Server.git] cat hooks/post-receive		🌵 m@bitpost [~/development/Libraries/c++/Simple-Web-Server.git] cat hooks/post-receive
	#!/bin/bash		#!/bin/bash

	# MDM WHEN WE RECEIVE CHANGES, AUTOMATICALLY PUSH THEM ALONG TO GITHUB		# MDM WHEN WE RECEIVE CHANGES, AUTOMATICALLY PUSH THEM ALONG TO GITHUB

	branch_name=`git symbolic-ref --short HEAD`		branch_name=`git symbolic-ref --short HEAD`
	retcode=$?		retcode=$?
	non_push_suffix="_local"		non_push_suffix="_local"

	# Only push if branch_name was found (my be empty if in detached head state)		# Only push if branch_name was found (my be empty if in detached head state)
	if [ $retcode = 0 ] ; then		if [ $retcode = 0 ] ; then

M at 21:05, 18 January 2019

2019-01-18T21:05:56Z

← Older revision		Revision as of 21:05, 18 January 2019
Line 4:		Line 4:

	Not much change, it moved to [https://gitlab.com/eidheim/Simple-Web-Server GitLab], cool. I [https://github.com/moodboom/Simple-Web-Server cloned it], and had to make some small tweaks to make the GitLab CI tester happy.		Not much change, it moved to [https://gitlab.com/eidheim/Simple-Web-Server GitLab], cool. I [https://github.com/moodboom/Simple-Web-Server cloned it], and had to make some small tweaks to make the GitLab CI tester happy.

			== Repo usage ==
			* I have a [https://github.com/moodboom/Simple-Web-Server GitLab clone] with my changes made in branch moodboom-quick-http.
			* my Simple-Web-Server git hook on bitpost:

			🌵 m@bitpost [~/development/Libraries/c++/Simple-Web-Server.git] cat hooks/post-receive
			#!/bin/bash

			# MDM WHEN WE RECEIVE CHANGES, AUTOMATICALLY PUSH THEM ALONG TO GITHUB

			branch_name=`git symbolic-ref --short HEAD`
			retcode=$?
			non_push_suffix="_local"

			# Only push if branch_name was found (my be empty if in detached head state)
			if [ $retcode = 0 ] ; then
			#Only push if branch_name does not end with the non-push suffix
			if [[ $branch_name != *$non_push_suffix ]] ; then
			echo
			echo "**** Pushing current branch $branch_name to origin [ie gitlab]"
			echo
			git push origin $branch_name;
			fi
			fi

			* and my .git/config
			🌵 m@bitpost [~/development/Libraries/c++/Simple-Web-Server.git] cat config
			[core]
			repositoryformatversion = 0
			filemode = true
			bare = true
			[remote "origin"]
			url = git@gitlab.com:moodboom/Simple-Web-Server.git
			fetch = +refs/:refs/
			mirror = true

	== Usage ==		== Usage ==

M at 21:01, 18 January 2019

2019-01-18T21:01:30Z

← Older revision		Revision as of 21:01, 18 January 2019
Line 1:		Line 1:
	The best C++ https code I found during my [[C++ https libraries\|2016/08 search]]. [https://github.com/eidheim Ole Christian Eidheim], the author, is great, he answered my emails and accepted my pull requests.		The best C++ https code I found during my [[C++ https libraries\|2016/08 search]]. [https://github.com/eidheim Ole Christian Eidheim], the author, is great, he answered my emails and accepted my pull requests.

			== Updated code on 2019/01/18 ==

			Not much change, it moved to [https://gitlab.com/eidheim/Simple-Web-Server GitLab], cool. I [https://github.com/moodboom/Simple-Web-Server cloned it], and had to make some small tweaks to make the GitLab CI tester happy.

	== Usage ==		== Usage ==

M at 17:02, 5 February 2017

2017-02-05T17:02:07Z

← Older revision		Revision as of 17:02, 5 February 2017
Line 1:		Line 1:
	The best C++ https code I found during my [[C++ https libraries\|2016/08 search]]. [https://github.com/eidheim Ole Christian Eidheim], the author, is great, he answered my emails and accepted my pull requests.		The best C++ https code I found during my [[C++ https libraries\|2016/08 search]]. [https://github.com/eidheim Ole Christian Eidheim], the author, is great, he answered my emails and accepted my pull requests.

			== Usage ==
			* SWS uses regex to match requests to handlers, look here to debug when they don't match up as expected:
			SWS/server_http.hpp ~ln 348
			void find_resource(const std::shared_ptr<socket_type> &socket, const std::shared_ptr<Request> &request) {
			//Find path- and method-match, and call write_response
			bk: for(auto &regex_method: resource) {
			auto it=regex_method.second.find(request->method);
			if(it!=regex_method.second.end()) {
			bk: REGEX_NS::smatch sm_res;
			if(REGEX_NS::regex_match(request->path, sm_res, regex_method.first)) {
			request->path_match=std::move(sm_res);
			write_response(socket, request, it->second);

	== Security Concerns ==		== Security Concerns ==

M at 17:16, 21 August 2016

2016-08-21T17:16:13Z

← Older revision		Revision as of 17:16, 21 August 2016
Line 13:		Line 13:
	* my bare shared mirror of my fork: bitpost: development/thedigitalage/Simple-Web-Server.git		* my bare shared mirror of my fork: bitpost: development/thedigitalage/Simple-Web-Server.git
	* my dev clones: development/thedigitalage/Simple-Web-Server		* my dev clones: development/thedigitalage/Simple-Web-Server
	* to get upstream changes, ~~just copy+paste all this goo~~:		* to get upstream changes, first make sure you have a dev repo configured to do the work:
	cd development/thedigitalage/Simple-Web-Server # any dev clone will do		cd development/thedigitalage/Simple-Web-Server # any dev clone will do
	# make sure it has the upstream available - only do this once		# make sure it has the upstream available - only do this once
	# git remote add eidheim-upstream https://github.com/eidheim/Simple-Web-Server.git		git remote add eidheim-upstream https://github.com/eidheim/Simple-Web-Server.git
			Now you can fetch changes and get them merged:
	git fetch eidheim-upstream		git fetch eidheim-upstream
	git checkout master		git checkout master
	git rebase eidheim-upstream/master # rebase your branch, so upstream is preserved even if there are commits (there should NOT be!)		git rebase eidheim-upstream/master # rebase your branch, so upstream is preserved even if there are commits (there should NOT be!)
	git push		git push
	~~---~~		Push them from bitpost up to GitHub:
	~~# on~~ bitpost~~, push the mirror~~
	cd development/thedigitalage/Simple-Web-Server.git		cd development/thedigitalage/Simple-Web-Server.git
	git push		git push

M at 17:14, 21 August 2016

2016-08-21T17:14:34Z

← Older revision		Revision as of 17:14, 21 August 2016
Line 21:		Line 21:
	git rebase eidheim-upstream/master # rebase your branch, so upstream is preserved even if there are commits (there should NOT be!)		git rebase eidheim-upstream/master # rebase your branch, so upstream is preserved even if there are commits (there should NOT be!)
	git push		git push
			---
			# on bitpost, push the mirror
			cd development/thedigitalage/Simple-Web-Server.git
			git push
	* to put together a pull request to send to Ole, first get all upstream changes, then create a new branch off of my fork's master, push the new branch to my fork, and use GitHub to create the pull request		* to put together a pull request to send to Ole, first get all upstream changes, then create a new branch off of my fork's master, push the new branch to my fork, and use GitHub to create the pull request
	# follow above steps to ensure my fork has latest changes from Ole; then...		# follow above steps to ensure my fork has latest changes from Ole; then...

M at 17:12, 21 August 2016

2016-08-21T17:12:43Z

@@ Line 9: / Line 9: @@
 == Repo structure ==
-* upstream:
+* [https://github.com/eidheim/Simple-Web-Server upstream]
+* [https://github.com/moodboom/Simple-Web-Server my fork]
 == [https://github.com/eidheim/Simple-Web-Server/pull/65 AES discussion] ==
 eidheim commented 3 hours ago

M at 16:49, 21 August 2016

2016-08-21T16:49:06Z

← Older revision		Revision as of 16:49, 21 August 2016
Line 8:		Line 8:
	* Need HSTS headers to allow perfect forward secrecy.		* Need HSTS headers to allow perfect forward secrecy.

	== AES discussion ==		== Repo structure ==
			* upstream:

			== [https://github.com/eidheim/Simple-Web-Server/pull/65 AES discussion] ==
	eidheim commented 3 hours ago		eidheim commented 3 hours ago
	I found only this: https://github.com/zaphoyd/websocketpp/blob/master/examples/echo_server_tls/echo_server_tls.cpp#L124. Here OpenSSL is used directly to disable RC4 I think (...:!RC4:...). See here for documentation of the command: https://www.openssl.org/docs/manmaster/ssl/SSL_CTX_set_cipher_list.html. The SSL_CTX* is reached by doing context.native_handle() in https_server.hpp if I'm not mistaken. Although which ciphers should be included otherwise I'm not sure of, however, it should be possible to receive the cipher list from SSL_CTX_get_ciphers (https://www.openssl.org/docs/manmaster/ssl/SSL_get_ciphers.html), that is instead of hardcoding them like in https://github.com/zaphoyd/websocketpp/blob/master/examples/echo_server_tls/echo_server_tls.cpp#L124.		I found only this: https://github.com/zaphoyd/websocketpp/blob/master/examples/echo_server_tls/echo_server_tls.cpp#L124. Here OpenSSL is used directly to disable RC4 I think (...:!RC4:...). See here for documentation of the command: https://www.openssl.org/docs/manmaster/ssl/SSL_CTX_set_cipher_list.html. The SSL_CTX* is reached by doing context.native_handle() in https_server.hpp if I'm not mistaken. Although which ciphers should be included otherwise I'm not sure of, however, it should be possible to receive the cipher list from SSL_CTX_get_ciphers (https://www.openssl.org/docs/manmaster/ssl/SSL_get_ciphers.html), that is instead of hardcoding them like in https://github.com/zaphoyd/websocketpp/blob/master/examples/echo_server_tls/echo_server_tls.cpp#L124.

M at 16:45, 21 August 2016

2016-08-21T16:45:38Z

← Older revision		Revision as of 16:45, 21 August 2016
Line 1:		Line 1:
	The best C++ https code I found during my [[C++ https libraries\|2016/08 search]]. ~~I'm contributing to keep its ciphers etc. up-to-date so it can maintain an A on~~ [https://~~www.ssllabs~~.com/~~ssltest/index.html its ssl tests~~].		The best C++ https code I found during my [[C++ https libraries\|2016/08 search]]. [https://github.com/eidheim Ole Christian Eidheim], the author, is great, he answered my emails and accepted my pull requests.

	Ole ~~Christian Eidheim~~		== Security Concerns ==
			* I'm contributing to keep SWS ciphers etc. up-to-date so it can maintain an A on [https://www.ssllabs.com/ssltest/index.html its ssl tests].
			* [https://hynek.me/articles/hardening-your-web-servers-ssl-ciphers/ This blog entry] has been kept up to date with recommendations and solutions.
			* Use nothing older than tlsv12. Pull request applied, fixed.
			* Use AES not RC4. This requires setting OpenSSL options. Ole advised on how to update the ciphers. I'm investigating.
			* Need HSTS headers to allow perfect forward secrecy.

			== AES discussion ==
			eidheim commented 3 hours ago
			I found only this: https://github.com/zaphoyd/websocketpp/blob/master/examples/echo_server_tls/echo_server_tls.cpp#L124. Here OpenSSL is used directly to disable RC4 I think (...:!RC4:...). See here for documentation of the command: https://www.openssl.org/docs/manmaster/ssl/SSL_CTX_set_cipher_list.html. The SSL_CTX* is reached by doing context.native_handle() in https_server.hpp if I'm not mistaken. Although which ciphers should be included otherwise I'm not sure of, however, it should be possible to receive the cipher list from SSL_CTX_get_ciphers (https://www.openssl.org/docs/manmaster/ssl/SSL_get_ciphers.html), that is instead of hardcoding them like in https://github.com/zaphoyd/websocketpp/blob/master/examples/echo_server_tls/echo_server_tls.cpp#L124.
			@moodboom

			moodboom commented 3 hours ago
			Cool. Here's the analysis that led me to think AES was the correct choice:

			https://hynek.me/articles/hardening-your-web-servers-ssl-ciphers/

			I'll try hardcoding a recommended cipher from there as the default and see what I get. If that works, maybe we can provide a cipher option to the user?

			Including support for HSTS seems to be the other important concern.

M: Created page with "The best C++ https code I found during my 2016/08 search. I'm contributing to keep its ciphers etc. up-to-date so it can maintain an A on [https://www..."

2016-08-21T16:38:38Z

Created page with "The best C++ https code I found during my 2016/08 search. I'm contributing to keep its ciphers etc. up-to-date so it can maintain an A on [https://www..."

New page

The best C++ https code I found during my [[C++ https libraries|2016/08 search]]. I'm contributing to keep its ciphers etc. up-to-date so it can maintain an A on [https://www.ssllabs.com/ssltest/index.html its ssl tests].

Ole Christian Eidheim