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

HTTPS #555

Open
zerononce opened this issue Oct 7, 2019 · 0 comments
Open

HTTPS #555

zerononce opened this issue Oct 7, 2019 · 0 comments

Comments

@zerononce
Copy link

Was reading your page regarding CNAMEs, and you all wrote:

"Note: We do not support HTTPS on custom domains. HTTPS enables end to end encryption (from your browser to our server). Although not critical for the website but we strongly recommend against using the ERPNext app over an unencrypted protocol. To be safe always use the ERP at your erpnext.com address."

This is insane to me.

You're actually marketing yourselves as providing accounting services alongside other features that require users to input their sensitive information & you're actually telling them that they do not need to have their site secured with a certificate of any sort.

I'm not sure what you all are getting high on...but put the fucking pipe down.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant