{"id":601,"date":"2019-04-02T22:22:35","date_gmt":"2019-04-03T03:22:35","guid":{"rendered":"http:\/\/zewwy.ca\/?p=601"},"modified":"2019-04-02T22:22:52","modified_gmt":"2019-04-03T03:22:52","slug":"zewwy-has-not-one-but-two-epiphanies","status":"publish","type":"post","link":"https:\/\/zewwy.ca\/index.php\/2019\/04\/02\/zewwy-has-not-one-but-two-epiphanies\/","title":{"rendered":"Zewwy has not one but two Epiphanies"},"content":{"rendered":"

<\/span>The Story<\/strong><\/span><\/h1>\n

Nothing goes better together than a couple moments of realization, and fine blog story. It was a fine brisk morning, on the shallow tides of the Canadian West… as the sun light gazed upon his glorious cheek… wait wait wait… wrong story telling.<\/p>\n

<\/span>The First Epiphany<\/span><\/h2>\n

First to get some reference see my blog post here<\/a> on setting up OPNsense as a reverse proxy, in this case I had no authentication and my backend pool was a single server so nothing oo-lala going on here. I did however re-design my network to encompass my old dynamic IP for my static one. One itsy bitsy problem I’m restricted on physical adapters, which isn’t a big deal, with trunking and VLAN tagging and all that stuff… however, I am limited on public IP addresses, and the amount of ports that can listen on the standard ports… which is well one for one… If it wasn’t for security, host headers would solve this issue with ease at the application layer (the web server or load balancer) with the requirement of HTTPS there’s just one more hurdle to overcome… but with the introduction of TLS 1.2 (over ten years now, man time flys) we can use Server Name Indication (SNI) to provide individual certs for each host header being served. Mhmmm yeah.<\/p>\n

This of course is not the epiphany… no no, it was simply how to get HAproxy plugin on OPNsense configured to use SNI. All the research I did, which wasn’t too much just some quick Googling… revealed that most configurations were manual via a conf file. Not that I have anything against that *cough Human error due to specialized syntax requirements*… it’s just that UIs are sort of good for these sort of things….<\/p>\n

The light bulb on what to do didn’t click (my epiphany) till I read this blog post<\/a>… from stuff-things.net … how original haha<\/p>\n

It was this line when the light-bulb went off…<\/p>\n

“All you need to do to enable SNI is to be give HAProxy multiple SSL certificates” also note the following he states… “In pass-through mode SSL, HAProxy doesn\u2019t have a certificate because it\u2019s not going to decrypt the traffic and that means it\u2019s never going to see the Host header. Instead it needs to be told to wait for the SSL hello so it can sniff the SNI request and switch on that” this is a lil hint of the SSL inspection can of worms I’ll be touching on later. Also I was not able to specifically figure out how to configure pass-though SSL using SNI… Might be another post however at this time I don’t have a need for that type of configuration.<\/p>\n

Sure enough, since I had multiple Certificates already created via the Let’s encrypt plugin… All I had to do was specify multiple certificates… then based on my “Rules\/Actions\/Conditions” (I used host based rules to trigger different backend pools) zewwy.ca -> WordPress and owa.zewwy.ca -> exchange server<\/p>\n

\"\"<\/a><\/p>\n

and just like that I was getting proper certificates for each service, using unique certs… on OPNsense 19.1 and HAProxy Plugin, with alternative back-end services… now that’s some oo-lala.<\/p>\n

My happiness was sort lived when a new issue presented it’self when I went to check my site via HTTPS:<\/p>\n

\"\"<\/a><\/p>\n

<\/span>The Second Epiphany<\/span><\/h2>\n

I let this go the first night as I accepted my SNI results as a victory. Even the next day this issue was already starting to bother me… and I wanted to know what the root of the issue was.<\/p>\n

At first I started looking at the Chrome debug console… notice it complaining about some of the plugins I was using and that they were seem as unsafe<\/p>\n

\"\"<\/a><\/p>\n

but the point is it was not the droids I was actually after… but it was the line (blocked:mixed-content) that set off the light bulb…<\/p>\n

So since I was doing SNI on the SSL listener, but I I was specifying my “Rule\/Action” that was pointing to my Backend Server that was using the normal HTTP real server. I however wanted to keep regular HTTP access open to my site not just for a HTTP->HTTPS redirect. I had however another listener available for exactly just that. At this point it was all just assumptions, even though from some post I read you can have a HTTPS load balancer hosting a web page over HTTPS while the back-end server is just HTTP. So Not sure on that one, but I figured I’d give it a shot.<\/p>\n

So first I went back to my old blog post on getting HTTPS setup on my WordPress website<\/a> but without the load balancer… turns out it was still working just fine!<\/p>\n

Then I simply created a new physical server in HAProxy plugin,<\/p>\n

\"\"<\/a><\/p>\n

created a new back-end Pool for my secure WordPress connection<\/p>\n

\"\"<\/a><\/p>\n

created a new “Rule\/Action” using my existing host header based condition<\/p>\n

\"\"<\/a><\/p>\n

and applied it to my listener instead of the standard HTTP rule (Rules on the SSL listener shown in the first snippet):<\/p>\n

\"\"<\/a><\/p>\n

Now when we access our site via HTTPS this time…<\/p>\n

<\/p>\n

Clean baby clean! Next up some IDS rules and inspection to prevent brute force attempts, SQL injections… Cross site scripting.. yada yada, all the other dirty stuff hackers do. Also those 6 cookies, where did those come from? Maybe I’ll also be a cookie monster next post… who knows!<\/p>\n

I hope you enjoyed my stories of “ah-ha moments”. Please share your stories in the comments. \ud83d\ude00<\/p>\n","protected":false},"excerpt":{"rendered":"

The Story Nothing goes better together than a couple moments of realization, and fine blog story. It was a fine brisk morning, on the shallow tides of the Canadian West… as the sun light gazed upon his glorious cheek… wait wait wait… wrong story telling. The First Epiphany First to get some reference see my … <\/p>\n

Continue reading “Zewwy has not one but two Epiphanies”<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"sfsi_plus_gutenberg_text_before_share":"","sfsi_plus_gutenberg_show_text_before_share":"","sfsi_plus_gutenberg_icon_type":"","sfsi_plus_gutenberg_icon_alignemt":"","sfsi_plus_gutenburg_max_per_row":"","footnotes":""},"categories":[4,6,8],"tags":[164,186,56],"class_list":["post-601","post","type-post","status-publish","format-standard","hentry","category-infosec","category-networking","category-server-administration","tag-opnsense","tag-sni","tag-wordpress"],"_links":{"self":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/601","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/comments?post=601"}],"version-history":[{"count":1,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/601\/revisions"}],"predecessor-version":[{"id":602,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/601\/revisions\/602"}],"wp:attachment":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/media?parent=601"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/categories?post=601"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/tags?post=601"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}