You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by "btzq (via GitHub)" <gi...@apache.org> on 2024/04/15 16:04:28 UTC

[I] Support ACL based on Domain/URL instead of IP [cloudstack]

btzq opened a new issue, #8917:
URL: https://github.com/apache/cloudstack/issues/8917

   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and main branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete the comments.
   -->
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Improvement Request
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   ~~~
   Improvement Request (Functionality)
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on main branch.
   -->
   
   ~~~
   4.19
   ~~~
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, advanced networking, etc.  N/A otherwise
   -->
   N/A
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   N/A
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   Note: This ticket is broken down as requested from the origianl post, https://github.com/apache/cloudstack/issues/8841
   
   **Support ACL based on Domain/URL instead of IP**
   
   - As a company, sometimes i would like to block access to specific sites (eg. google drive), which is based on domain. 
   - But i am unable to do so because, ACL Rules are based on explicitly specifying the IP address.
   - Specifying the IP address/range of the intended website will be tedious and non-practical.
   
   ##### STEPS TO REPRODUCE
   <!--
   For bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate.
   
   For new features, show how the feature would be used.
   -->
   N/A
   
   <!-- Paste example playbooks or commands between quotes below -->
   ~~~
   N/A
   ~~~
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   ~~~
   To be able to manage ACL Rules more easily for enterprise use cases.
   ~~~
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   Unable to effectively block access to certain sites using URL/Domain
   ~~~
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Support ACL based on Domain/URL instead of IP [cloudstack]

Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland commented on issue #8917:
URL: https://github.com/apache/cloudstack/issues/8917#issuecomment-2058290870

   As ACLs are implemented using iptables there is not a trivial way to implement this. The VR will have to use ipset and dig/nslookup to create sets of ips from domain names and (re)apply those. It will be hard to make this relyable if users try to change those on the fly, or reorder them. There also needs to be a mechanism to update them automatically as DNS entruies for them may change out of bounds.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Support ACL based on Domain/URL instead of IP [cloudstack]

Posted by "btzq (via GitHub)" <gi...@apache.org>.
btzq commented on issue #8917:
URL: https://github.com/apache/cloudstack/issues/8917#issuecomment-2059117638

   We got this idea on some enterprise firewalls like PFSense.
   
   Is there no way to achieve a similar result?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Support ACL based on Domain/URL instead of IP [cloudstack]

Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland commented on issue #8917:
URL: https://github.com/apache/cloudstack/issues/8917#issuecomment-2059305975

   Yes @btzq , there is, as described above, but the programming needs to be done on the VR. I am just saying it is not a trivial job. It is certainly possible.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Support ACL based on Domain/URL instead of IP [cloudstack]

Posted by "vishesh92 (via GitHub)" <gi...@apache.org>.
vishesh92 commented on issue #8917:
URL: https://github.com/apache/cloudstack/issues/8917#issuecomment-4480177532

   The workaround is to fetch the get the IP ranges of the providers you want to block (google, onedrive, etc.) and update the ACLs. This will need to be run as a script which runs frequently to ensure new and old IPs are added and removed to avoid blocking the actual traffic.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org