Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
im nmapping myself to check for some holes ans such and noticed logging into my box with ftp and ssh were simple, so i looked at my guarddog config and blocked both ftp and ssh and still when i use ftp to log into my system it connects?? shouldnt it refuse me??
i know guarddog is considered pussy in the Linux world but im still new to the iptables thing and needed something even if it is basic!
i dont know what version. im not at my box. i know its the newest version cause i got it last night!! ya when i make changes it says iptables updated and all that, you think guarddog is better than a real script?? huh, maybe ill stick with guarddog then!!!! i know it works good cuase i went to that website that scans your ports and all and the only one that came up was stmp and the rest were marked stealth!!!! ya baby!!!, anyways ill try what you said. thanks!!!
Well can you remember if you got a prepacked .rpm, or compiled from the 2.0.0 source, or the development 2.1.3 maybe?
If you open your /etc/rc.firewall in a text editor (as root, and I'd be careful not to execute it instead) you can see the commented script which generates the rules.
It is generating quite a good ruleset, and with such an easy gui it's great til you learn exactly which rules you need to write.
I'd just be certain to check that ftp thing though.
I think I'll go hunt an Mdk9.1 rpm of 2.1.3 now actually, Guarddog rules
so dou you know why it wont block my smtp port, i have it blocked
in the options but when i iuse the shields up website to scan me
it says its still wide open!!! everything else blocks, telnet..ftp..etc.
umm, no i guess ftp is still giving access, i just ftp'd myself and i connected, how do i refuse connection to that?? i got telnet refusing but ya ill check my .rc file and se what it looks like, even though i wouldnt really know how to modify it, im still new and the hardest things ive done so far was compiling mplayer and wine, well getting wine to work!!! it was easy to install so ya im really into internet security and basically want my system to be real hard to break into, and one more thing, does guraddog update their product weekly,monthly,yearly, etc..
Sure you're not changing the rules for the wrong zone, eg changing Internet access but logging in via Local/LAN?
Did you check that?
I dunno how to modify it either atm.
From browsing their site, there seems to be a lot of effort focused on testing and debugging the new Development version 2.1.3, while the official stable release seems to be held at 2.0.0. Maybe try 2.1.1 for newer release vs stability and security.
The usual Open Source approach to testing involves releasing "beta" or "Release Candidate" versions of a piece of software and then allowing people to try it out and report any problems they encounter. Unfortuately this means that any features that are not used by the users are assumed to be in a state acceptable for release. This is may be acceptable for most software, but for security software it is not. We must assume the worst until proven otherwise. This means assuming that Guarddog's protocol support is insecure until proven secure.
Unfortunately I don't have access to all of the different software or the time to test every protocol myself. But you can help by following the instructions on this page and sending me your results. By putting together information from user reports I hope to determine which protocols people are successfully using and which ones need fixing. I'll also tabulate results and update the protocol testing table (the "scoreboard") that appears lower on this page.