Re: filestarter (graphic tool for iptables)
Firestarter is long-dead and likely doesn't support recent kernels. I would start here: https://fedoraproject.org/wiki/FirewallD On Fri, Nov 14, 2014 at 10:34 AM, Angelo Moreschini < mrangelo.fed...@gmail.com> wrote: > Hi > I'm still learning Linux, and I have fedora 20 on my compuer. > I would like get an advice about to use "firestarter". > > I have read many things about iptables (who it looks to me rather complex to > use). > > I know that firestarter is a graphical tool that it can be used to manage > iptables; so I would like to try it, also because (generally) GUI Tools > help to understand how the programs work. > > I am however a little puzzled to install firestarter because I do not see > it much recommended in the books that I'm reading, and why sites that > distribute > it are not officially sponsored by fedora .. > > At the link <http://koji.fedoraproject.org/koji/buildinfo?buildID=85460> I > found firestarter-1.0.3-20.fc11.x86_64.rpm > > I would like to get feedback about the opportunity to install this > distribution or perhaps a better distribution of this tool on my computer. > > Tank you > > Regards > > Angelo > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org > > -- Mark Bidewell http://www.linkedin.com/in/markbidewell -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Constant Guard Service Alert
Interesting, I got an alert at 6:33PM. My PCs are OSX, Linux Mint and SolydXK with assorted VMs. I'm scanning, but I wonder if there is a malfunction as the bot detected was Windows related. Go to: https://amibotted.comcast.net/. My output reads: Bot Notes: Threat behaviors: Downloads rootkits and steals sensitive information. Threat type (intent):Information Stealer (Information Theft & Sublease tool). Alternate names: W32.Rootkit /W32.Alureon/ W32.Renos/W32.TDSS/W32.DNSChanger Threat behavior description: The TDL/TDSS Gang (aka., Tyler Durden Loader). The TDL rootkit is a Master Boot Record (MBR) infector, targeting Microsoft Windows systems. The latest TDL rootkit is currently Version 4, and utilizes MBR hooking, a process that deceives a user by appearing to have been initially deleted. Upon a system restart, the rootkit/trojan is re-installed. This provides the remote attacker highly persistent backdoors into victim systems. Public research estimates the TDL/TDSS group to have been in operation since mid-2008. Observed traits: The TDL/TDSS rootkit has been observed spreading via spam and phishing e-mails. The observed stages of infection are as follows: Infect a victim (Stage 1) via spam, drive-by-downloads, and malicious attachments.Wait idle until the Stage 2 Trojan is ready for download. Load a rootkit Trojan (Stage 2). Alter the system to obfuscate Stage 1 and 2 infections (Stage 3). Infect other sites, allowing third-party access to sensitive information. Capabilities: After an initial infection, the Stage 2 rootkit is normally loaded via a fast-flux worm. Once the infection has passed to Stage 3, various other threats (such as ZeusBot, Buzus, RogueAV, PoisonIvy, etc.) may be installed and utilized by criminal operators. The authors behind the RudeWarlockMob are members of a professional criminal organization that also offers affiliate funding to anonymous distribution providers, infection operators, and other criminals. Times Seen: 23 On Sat, Sep 6, 2014 at 8:02 PM, Anthony Messina wrote: > On Saturday, September 06, 2014 06:39:46 PM Mickey wrote: > > Got a email from Comcast.net, saying I have a Bot on my Computer, and > how to > > elimnate it, Not so sure that I want to follow their directions. > > > > How I would I determine if this is true using Linux , I have Fedora 20 > > installed ? > > Maybe your neighbor's infected computer is borrowing your WiFi ;) > > In short, don't forget about other devices that may be using your internet > link such as mobile phones, tablets, TVs, etc. > > -- > Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery > 8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org > > -- Mark Bidewell http://www.linkedin.com/in/markbidewell -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: dns/dhcp client - hooks??
I think this may be an issue with the Fedora build of dhclient. I can successfully update DNS with dhclient on CentOS6 or Ubuntu, but not Fedora. On Tue, Jan 21, 2014 at 12:02 PM, bruce wrote: > kevin. > > the whole/partial reason for all of this. > > the local system with the dhcp, doesn't have a dns!!! > > you come in the lab, connect, you get your ip. as to the external > world, the dhcp serves the dns for the rest of the world. as to the > internal boxes, you get an ip, nothing more!! > > it wasn't the intent to have boxes hooked up for long... we're bending > the system... so to do that, we'd rather not have to always recall > ipaddresses, so we're going to kludge this.. > > > > On Tue, Jan 21, 2014 at 11:37 AM, Kevin Martin wrote: > > On 01/21/2014 10:36 AM, Kevin Martin wrote: > >> On 01/21/2014 09:54 AM, bruce wrote: > >>> tim.. > >>> > >>> i have complete control over the local dns > >>> > >>> the local client machines are given hostnames upon creation/boot up.. > >>> > >>> the idea is to be able to have someone within the local network, > >>> who'[s machine has been configured to point to the local dns, to be > >>> able to use the boxname "foo" to get to the machine instead of the > >>> ipaddress of the "foo" box. > >>> > >>> normally,, all of this would be handled by thre dhcp server.. in this > >>> case it isn't. > >>> > >>> so you need to do a kludge which involves updating the local dns > >>> server/records with the updated mapped ip/name. > >>> > >>> > >>> > >>> On Tue, Jan 21, 2014 at 10:49 AM, Tim > wrote: > >>>> Allegedly, on or about 21 January 2014, bruce sent: > >>>>> some of us who deall with getting dhcp ipp addresses, don't have > >>>>> access to managing the dhcp server!!! > >>>> > >>>> And you have access to a DNS server that you can reprogram?? > >>>> > >>>> If so, then have a look at the already existing coding for the DHCP > >>>> servers, and apply the same with your client. > >>>> > >>>> -- > >>>> [tim@localhost ~]$ uname -rsvp > >>>> Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 > x86_64 > >>>> > >>>> All mail to my mailbox is automatically deleted, there is no point > >>>> trying to privately email me, I will only read messages posted to the > >>>> public lists. > >>>> > >>>> George Orwell's '1984' was supposed to be a warning against tyranny, > not > >>>> a set of instructions for supposedly democratic governments. > >>>> > >>>> > >>>> > >>>> -- > >>>> users mailing list > >>>> users@lists.fedoraproject.org > >>>> To unsubscribe or change subscription options: > >>>> https://admin.fedoraproject.org/mailman/listinfo/users > >>>> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > >>>> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > >>>> Have a question? Ask away: http://ask.fedoraproject.org > >> can you 'dig @primaryDNS your.domain.com axfr' the primary DNS server? > If you can't you probably won't be able to do what you are > >> hoping to achieve as the primary name server isn't allowing you to do a > zone transfer. You would essentially have to know each and > >> every host and do a name lookup of each and every host one at a time > and capture that information and build your zone(s) that way. > >> > >> Kevin > >> > > better yet, why don't you just point the dns clients to the primary dns > server, set the domain to search, and do the name resolution > > that way? > > > > Kevin > > -- > > users mailing list > > users@lists.fedoraproject.org > > To unsubscribe or change subscription options: > > https://admin.fedoraproject.org/mailman/listinfo/users > > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > > Have a question? Ask away: http://ask.fedoraproject.org > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org > -- Mark Bidewell http://www.linkedin.com/in/markbidewell -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Fedup Failure
I tried upgrading from Fedora 19 to 20. When the System Upgrade task starts I get a failure around /run/initramfs (it moves fast). Then it boots back to Fedora 19. Any thoughts on how to debug? -- Mark Bidewell http://www.linkedin.com/in/markbidewell -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Systemd Freezing on NetworkManager or Display Manager
On Sat, Nov 9, 2013 at 1:12 PM, Rex Dieter wrote: > Ron Yorston wrote: > > > Rex Dieter wrote: > >>Mark Bidewell wrote: > >> > >>> I am using Fedora 19 on older hardware, and about half the time systemd > >>> freezes on boot. Typically the console messaging is pointing at > Network > >>> Manager but occasionally kdm or gdm. I can switch to another console > >>> and log in and network is up and I can enter X. > >>> > >>> Any ideas how to debug this? > >> > >>You might be hitting this, > >>https://bugzilla.redhat.com/show_bug.cgi?id=967521 > > > > Or possibly this: > > > >https://bugzilla.redhat.com/show_bug.cgi?id=1013867 > > Probably the same problem, slower boots causing service timeouts all over. > > -- rex > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org > Thanks do you know if any progress is being made on the performance issues? -- Mark Bidewell http://www.linkedin.com/in/markbidewell -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Systemd Freezing on NetworkManager or Display Manager
For some reason it never registered that the "OK" is on the left now. There is an "OK" after network manager, but the behavior seems different after the latest updates. I wonder if its a GDM vs KDM issue. KDM seems to start earlier in the boot process than GDM. GDM does seem more reliable. On Fri, Nov 8, 2013 at 7:54 PM, Joe Zeff wrote: > On 11/08/2013 04:49 PM, Mark Bidewell wrote: > >> I will double check the status, but I don't believe one is printed. I >> checked /var/log/messages And the is a message about being on IPv6 set >> 4 of 5. but ip addr show lists both IPv4 and IPv6 addresses. >> > > Generally, when you're booting, you'll see either [OK] or [Failed] at the > end of each line as the various services start. If it hangs without > either, that's probably where the trouble is. > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org > -- Mark Bidewell http://www.linkedin.com/in/markbidewell -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Systemd Freezing on NetworkManager or Display Manager
I will double check the status, but I don't believe one is printed. I checked /var/log/messages And the is a message about being on IPv6 set 4 of 5. but ip addr show lists both IPv4 and IPv6 addresses. On Fri, Nov 8, 2013 at 7:44 PM, Joe Zeff wrote: > On 11/08/2013 04:34 PM, Mark Bidewell wrote: > >> Generally, "Starting Network Manager". >> > > Thanx. The reason I ask is that I've seen things like this pop up before > on web forums, and sometimes the last line quoted ends with [OK] meaning, > of course, that whatever starts *next* is what's causing the hangup, and > the problem becomes figuring out what that is. Now, at least, we've got > that out of the way. > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org > -- Mark Bidewell http://www.linkedin.com/in/markbidewell -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Systemd Freezing on NetworkManager or Display Manager
Generally, "Starting Network Manager". On Fri, Nov 8, 2013 at 7:32 PM, Joe Zeff wrote: > On 11/08/2013 04:25 PM, Mark Bidewell wrote: > >> Any ideas how to debug this? >> > > When this happens, what is the very last message on the main screen? > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org > -- Mark Bidewell http://www.linkedin.com/in/markbidewell -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Systemd Freezing on NetworkManager or Display Manager
I am using Fedora 19 on older hardware, and about half the time systemd freezes on boot. Typically the console messaging is pointing at Network Manager but occasionally kdm or gdm. I can switch to another console and log in and network is up and I can enter X. Any ideas how to debug this? Thanks -- Mark Bidewell http://www.linkedin.com/in/markbidewell -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
