[
https://issues.apache.org/jira/browse/FTPSERVER-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847289#action_12847289
]
David Latorre commented on FTPSERVER-357:
-----------------------------------------
About the metho names... We are keeping the getBlockedSubnets()
getBlockedAddresses() methods right? I don't know if we choose a better name
for these methods as they are a bit misleading ( I can't think of any though
and its one of our internal classes so whatever).
I don't really know what are the capabilities that a Whitelist/blacklist
solution should offer but I have some doubts:
- Is it likely that blacklist & whitelist can be used at the same time? For
example, we have some range of subnets allowed but there is a specific host
which is trying to break into FTPServer or flooding it with connections: an
user FTPLet might detect this and try to include that host to the blacklist. I
think spam filters define "whitelist" as a list of addresses that are never
rejected rather than "the only addresses that are allowed to connect to the
server" - is that an useful feature for us?
- Should we extend the black/white listing to the USER level? So, user A can
only connect from X.X.X.X whereas user B can connect from Y.Y.Y.Y or Y.Y.Y.Z I
find this most useful in our own case at my company where different users means
different customers.
> Implement IP Filtering based on black or white list
> ---------------------------------------------------
>
> Key: FTPSERVER-357
> URL: https://issues.apache.org/jira/browse/FTPSERVER-357
> Project: FtpServer
> Issue Type: New Feature
> Components: Core
> Reporter: Sai Pullabhotla
> Fix For: 1.1.0
>
> Attachments: ftpserver-ipfilter.patch
>
>
> Create a new IP Filter based on black or white list to deny or allow incoming
> client connections.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
