Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SSL Verification Option for Certificate Checking #20

Closed
caronc opened this issue Jul 5, 2017 · 3 comments
Closed

SSL Verification Option for Certificate Checking #20

caronc opened this issue Jul 5, 2017 · 3 comments
Assignees

Comments

@caronc
Copy link
Owner

caronc commented Jul 5, 2017

Issue #19 pointed out that SSL Certificate Verification is enforced by default which is ideal in preventing Man-In-The-Middle attacks. But some smaller setups (and home projects) just get the certificates and don't want to pay the $200 USD to get their certificates signed.

Add ?verify=False as an optional parameter one can specify when using the secure (https) web posting method to deactivate SSL Certificate verification.

@caronc caronc closed this as completed in e08f199 Jul 5, 2017
@seanvree
Copy link

seanvree commented Jul 6, 2017

@caronc - so what's the entire script to run to test?

"python notify.py -b "test" ?verify=False -s mmosts://mydomain.com/wireapm5w7gfmek1jkr6zm0000 -D"

Also, my certs are NOT self-signed BTW.

@caronc
Copy link
Owner Author

caronc commented Jul 6, 2017

Oh, that's weird. The error your reporting is documented as being caused by unsigned certificates (or no internet access to verify them with).

The check would be:

python notify.py -b "test"  -s mmosts://mydomain.com/wireapm5w7gfmek1jkr6zm0000?verify=False -D

@seanvree
Copy link

seanvree commented Jul 6, 2017

it works! See #19

@caronc caronc self-assigned this Jul 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants