Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm looking for something i saw ages ago so i know its out there just want to be pointed in the right dorection if possible to know about it again. I'm looking or something that is able to work inside a TCP wrapper and if a file is asked to be servered thats say not in an allow list of IP addresses etc, then that request is acknowledged and sent the file but sent a hevily encrypted version of the file. I know this is possibel it does mean making a change and added edit to some of the fucntions or something i can't remember, but if anyones knows anything that sounds remotely like this stuff please let me know
cherers
Doesn't matter about the protocol, the point of veiw is if an attacker tried to get a copy a file no matter what protocol they were using all they'd end up with is an encrypted file. If a computer in the allowed list tried to get the file then the file stays un-encrypted.
To be able to do this for "any protocol", you'd need a protocol specific handler for EACH protocol running on the system. At the network level, there is no such thing as a file, only a stream of bytes. FTP, HTTP, and other protocols represent files differently.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.