mdshooters.com SSL certificate

[LCPIWB]

I know the SSL certicate for mdshooters has been expired for two years
now.
When https://letsencrypt.org/ offering goes public on Dec
3rd, can you please consider acquiring a new SSL certificate. It's free
and will trusted.
Please consider it.
Also enforcing all traffic to go through https would be nice.

Let me know if you need any technical support.

 

[K31]

I support this guy's suggestion.

 

[doofoo]

I don't know if I would suggest forcing redirect to HTTPS. There are a lot of workplaces that just flat out filter HTTPS... So stupid, but.. It happens A LOT.

Of course have the option for HTTPS but leave it just that.. A Option.

 

[offroaD]

I don't know if I would suggest forcing redirect to HTTPS. There are a lot of workplaces that just flat out filter HTTPS... So stupid, but.. It happens A LOT.

Of course have the option for HTTPS but leave it just that.. A Option.

Probably should not be on MDS during work hours.

 

[doofoo]

Probably should not be on MDS during work hours.

Yeah.....

 

[PJDiesel]

Probably should not be on MDS during work hours.

 

[engineerbrian]

Probably should not be on MDS during work hours.

Thats crazy talk!

 

[WeaponsCollector]

My workplace specifically blocks MDShooters and most other gun related sites because of "weapons". To get around it all I have to do is add "https://" to the address and it works after I click "continue to site(not recommended)." An added plus, every time I do this I get another mark in my secret file.

 

[HarCo2ANewb]

I don't know if I would suggest forcing redirect to HTTPS. There are a lot of workplaces that just flat out filter HTTPS... So stupid, but.. It happens A LOT.

Of course have the option for HTTPS but leave it just that.. A Option.

I am blocked if I DON'T use HTTPS

Probably should not be on MDS during work hours.

My workplace specifically blocks MDShooters and most other gun related sites because of "weapons". To get around it all I have to do is add "https://" to the address and it works after I click "continue to site(not recommended)." An added plus, every time I do this I get another mark in my secret file.

Yeah, this! I am sure someone in IT gets a ping every time I hit up against the web blocks but I have done it so many times, they probably just turned it off.

 

[doofoo]

I am blocked if I DON'T use HTTPS







Yeah, this! I am sure someone in IT gets a ping every time I hit up against the web blocks but I have done it so many times, they probably just turned it off.

Yeah it all depends on the location.. Was just saying. I've done work at locations that just flat out block HTTPS.. It makes NO sense, you can't even do banking - but they do it.. lol

I'd just leave HTTP available for those that need it.

 

[TheBert]

I know the SSL certicate for mdshooters has been expired for two years
now.
When https://letsencrypt.org/ offering goes public on Dec
3rd, can you please consider acquiring a new SSL certificate. It's free
and will trusted.
Please consider it.
Also enforcing all traffic to go through https would be nice.

Let me know if you need any technical support.

Just make sure the new cert is not an SHA1. It should be SHA256.

 

[rseymorejr]

Probably should not be on MDS during work hours.

Hey!
Mind your own damn business!

 

[babalou]

Weird

Yeah it all depends on the location.. Was just saying. I've done work at locations that just flat out block HTTPS.. It makes NO sense, you can't even do banking - but they do it.. lol

I'd just leave HTTP available for those that need it.

I prefer sslvpn port 443 over thick vpn clients due to upper layer layer versus network layer. Better security. Just have a firewall or device that can do ssl packet inspections. I would rather people browse using ssl versus non

 

[Mr H]

Probably should not be on MDS during work hours.

You funny guy.

 

[GeorgeSSR]

FYI, I've been using Let's Encrypt for a few months (was in the alpha for getting their ACME client fired up) for some side work. The only real issue with using this is that it's a short duration cert that needs to be refreshed every few months (though this can be handled with a cron job if you're willing to have httpd or whatever go down for 30 seconds at 3 AM).

In addition to LCPIWB I'm also willing to throw in some support if you guys need it to get this going.

 

[woodstock]

not to railroad the OP's intention for this thread, but in looking at the "i need an avatar" i see the OP's handle is LCPIWB. really? may i ask what holster? LCP's are very compact and i am curious to know how well a draw would be with it.

as for the http and and all that technical jazz, i am pretty inept, just ask cypherpunk or dogbone.

 

[LCPIWB]

not to railroad the OP's intention for this thread, but in looking at the "i need an avatar" i see the OP's handle is LCPIWB. really? may i ask what holster? LCP's are very compact and i am curious to know how well a draw would be with it.

as for the http and and all that technical jazz, i am pretty inept, just ask cypherpunk or dogbone.

Was not following my own thread.
I just needed to make up a handle...LCP was too short, so added IWB.
Of course living here in Md have not had a chance to carry...
But I do have one of the those urban carry things.
I am looking for a 7rd magazine, that would give me an extra finger and easier to draw.


New Admin kevin. How about the SSL cert?

 

[aray]

My work site won't allow connections to servers with SSL if the certificate has expired.

 

[IDFInfantry]

Let's Encrypt is probably the best solution if you don't want to spend money.
I have been using on all of my websites for a while now without issue.
If you are running Debian or something similar there is automation with Apache which makes things super simple. Couldn't get any easier really.

 

[LCPIWB]

Let's Encrypt is probably the best solution if you don't want to spend money.
I have been using on all of my websites for a while now without issue.
If you are running Debian or something similar there is automation with Apache which makes things super simple. Couldn't get any easier really.

I see the moved to Apache2.2.25 with the site upgrade, so they should not have any issue with the auto-configuration. They were using ngix which did not have the auto configuration tool.