Originally created by @imakecodes on GitHub (May 5, 2025).
Is there any possibility to block access to the ports based on the IP address attempting the connection? Or to follow a similar logic to what is already in place for domains and subdomains?
Originally created by @imakecodes on GitHub (May 5, 2025).
Is there any possibility to block access to the ports based on the IP address attempting the connection? Or to follow a similar logic to what is already in place for domains and subdomains?
@oschwartz10612 commented on GitHub (May 5, 2025):
Are you talking about blocking to raw tcp or udp resources? Unfortunately that is not built in right now into the application and might be tough because we dont have the use of badger yet like we do for http.
@oschwartz10612 commented on GitHub (May 5, 2025):
Are you talking about blocking to raw tcp or udp resources? Unfortunately that is not built in right now into the application and might be tough because we dont have the use of badger yet like we do for http.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @imakecodes on GitHub (May 5, 2025).
Is there any possibility to block access to the ports based on the IP address attempting the connection? Or to follow a similar logic to what is already in place for domains and subdomains?
@oschwartz10612 commented on GitHub (May 5, 2025):
Are you talking about blocking to raw tcp or udp resources? Unfortunately that is not built in right now into the application and might be tough because we dont have the use of badger yet like we do for http.
@oschwartz10612 commented on GitHub (May 5, 2025):
I think we can keep this as a feature request. I will move to discussions so people can upvote.