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

Enterprise roll-out #660

Open
cluck opened this issue Aug 3, 2023 · 1 comment
Open

Enterprise roll-out #660

cluck opened this issue Aug 3, 2023 · 1 comment

Comments

@cluck
Copy link

cluck commented Aug 3, 2023

You're indeed stating important features of your webproxy product on the front page: the webproxy is said to be an Easy to manage web filtering proxy for the Enterprise, and that it Fits in Your Network. Great work!

But your EULA quicky annihilates my imagination of an Enterprise-grade Network-wide rollout: You may not make or distribute copies of the Software, or electronically transfer the Software from one computer to another or over a network. So, as I understand it, no one should ever store you installer in an MDM, SSCM, MS AD or similar and should never undertake an action to roll out your software in an automated unattended way to serve en enterprise or network in general (... right?).

I guess you want to fix either your front page or your EULA there.

Moreover, I get that your company is incorporated in the Netherlands. The very same EULA makes me wonder what federation you're referring to in All rights not specifically granted in this EULA, including Federal and International Copyrights, are reserved by Diladele B.V. and its suppliers. To my knowledge, the Kingdom of the Netherlands is an unified territory, and this sentence reads like it could be subject to a Copyright infringement inquiry under US-Federal law.... oh, the irony.

PS: This is on GitHub: do you plan to publish the source code of this security product?

@ra-at-diladele-com
Copy link
Contributor

Hello Claudio, for now we do not plan to publish the sources. I guess management means actual management of the proxy features, like enabling what needs to be enables etc; not the automation.

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

2 participants