Re: Closing port 631 from other computers

On Fri, 2014-10-31 at 11:34 +0200, Jarmo Hurri wrote: > After the recent security incidents I am trying to increase the security > of my computer by closing unnecessary ports from outside world. > > The only listening port in my system right now is port 631 (ipp), as > "lsof -i | grep -i listen" r

Re: A Linux for the totally maintenance free

Tim: >> For some people, or lots of people, upgrading every 6 months is a >> headache best avoided. Quite apart from having to backup and restore, >> or backup and hope you don't have to restore, personal files and >> important settings, you have to deal with a changed user interface. It >> nearl

Re: A Linux for the totally maintenance free

On Fri, 2014-10-31 at 12:52 -0400, Tom H wrote: > The “learning curve” is an exaggerated meme based on my SMALL sample. > I’ve migrated my parents from Windows to Gnome 2 to Unity and my > neighbor from Windows to Unity without them having a problem finding > their bearings. I've always thought th

Re: smplayer OK

Tim: >> You're talking about the thing being debated on here about a week >> or so ago? Man of few words, poma, wrote: > What!? The precise details elude me, but it was something run by NetworkManager that called upon some outside service every time you went on line, and people were not happy abo

Re: Driver for RTL8192su chipset

On 31.10.2014 22:20, jd1008 wrote: > > On 10/31/2014 02:43 AM, poma wrote: >> >> You missed some important steps we've already written, man. >> >> First try this, then we'll see what about 'rtl8192su.ko & Co.' >> Don't break lines. >> >> 1. Check whether you have installed the necessary firmware >

Re: rc.local not start at the boot

On 11/01/14 03:44, Angelo Moreschini wrote: > thank you for your patience Ed > > I do not want to abuse your help .. maybe you can tell me what I can do. > If you show me a direction to follow, I will try to study also alone the > problem .. As I mentioned in my response to Joe, I think the sympt

Re: rc.local not start at the boot

On 11/01/14 03:01, Joe Zeff wrote: > On 10/31/2014 05:49 AM, Angelo Moreschini wrote: >> SELINUX=permissive =--> didn't work >> >> setsebool -P rsync_full_access 1 =--> didn't work too > > Therefor SELinux isn't involved. Yes, as it now stands selinux is not involved. I would like to mention th

Re: rc.local not start at the boot

On 11/01/14 05:22, Joe Zeff wrote: > I also find it interesting that it was causing the command to fail for you, > but doesn't seem to be involved in the OP's case. I will be very interested > in learning just what's going on, and will continue to offer suggestions if > and when I have them.

Re: rc.local not start at the boot

On 10/31/2014 02:09 PM, Ed Greshko wrote: It was quite simple I replicated what I hoped to be the OP's environment in a VM. In doing so I also saw a failure to successfully complete the execution of the rsync command. However, as you saw, there were no error messages to be seen. So, I s

Re: Driver for RTL8192su chipset

On 10/31/2014 02:43 AM, poma wrote: You missed some important steps we've already written, man. First try this, then we'll see what about 'rtl8192su.ko & Co.' Don't break lines. 1. Check whether you have installed the necessary firmware $ rpm -qf /usr/lib/firmware/rtlwifi/rtl8712u.bin linux-

Re: rc.local not start at the boot

On 11/01/14 02:55, Joe Zeff wrote: > On 10/31/2014 02:21 AM, Ed Greshko wrote: >> The problem is related to "selinux". > > How do you know? Are you getting SELinux alerts about this every time you > boot? It was quite simple I replicated what I hoped to be the OP's environment in a VM. In

5tFTW: Fedora Beta, Council & Elections, Strategic Planning, Outreach Committee, and FUDCon Reports (2014-10-31)

Reposted from . Fedora is a big project, and it’s hard to keep up with everything that goes on. This series highlights interesting happenings in five different areas every week. It isn’t comprehensive news coverage — just quick summaries with links to e

Re: "Input out of Range"

On 2014-10-31 12:25, Tom Horsley wrote: On Fri, 31 Oct 2014 11:49:38 -0700 Rick Stevens wrote: One way out is to plug the monitor into the box directly, boot up and verify that the screen comes up correctly. You can then get X to dump its settings and put those into an Xorg.conf file so it alwa

Re: rc.local not start at the boot

On Fri, 31 Oct 2014 13:06:52 -0700 Joe Zeff wrote: > However, there is one thought: we're pretty sure that there's something > about the rsync command that's failing. Have you considered directing > stderr to a file? Yep, I'd definitely stick something like this neat the front: exec > /var/lo

Re: rc.local not start at the boot

On 10/31/2014 12:44 PM, Angelo Moreschini wrote: thank you for your patience Ed I do not want to abuse your help .. maybe you can tell me what I can do. If you show me a direction to follow, I will try to study also alone the problem If I knew the answer, I'd tell you. Alas, all I can do at t

Re: rc.local not start at the boot

thank you for your patience Ed I do not want to abuse your help .. maybe you can tell me what I can do. If you show me a direction to follow, I will try to study also alone the problem .. regards Angelo On Fri, Oct 31, 2014 at 9:01 PM, Joe Zeff wrote: > On 10/31/2014 05:49 AM, Angelo Moresch

Re: "Input out of Range"

On Fri, 31 Oct 2014 11:49:38 -0700 Rick Stevens wrote: > One way out is to plug the monitor into the box directly, boot up and > verify that the screen comes up correctly. You can then get X to dump > its settings and put those into an Xorg.conf file so it always uses > those values. It won't matt

Re: rc.local not start at the boot

On 10/31/2014 05:49 AM, Angelo Moreschini wrote: SELINUX=permissive =--> didn't work setsebool -P rsync_full_access 1 =--> didn't work too Therefor SELinux isn't involved. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedorap

Re: Closing port 631 from other computers

On 10/31/2014 02:34 AM, Jarmo Hurri wrote: I tried disabling cups services, but then printing stopped working. What else do you expect when you disable the printing service? So ok, I need a connection from my computer to port 631 for printing. But that port should be closed from all other co

Re: rc.local not start at the boot

On 10/31/2014 02:21 AM, Ed Greshko wrote: The problem is related to "selinux". How do you know? Are you getting SELinux alerts about this every time you boot? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/ma

Re: rc.local not start at the boot

[angelo_dev@zorro ~]$ systemctl status rc-local.service rc-local.service - /etc/rc.d/rc.local Compatibility Loaded: loaded (/usr/lib/systemd/system/rc-local.service; static) Active: failed (Result: exit-code) since Fri 2014-10-31 20:43:44 IST; 2min 10s ago Process: 891 ExecStart=/etc/rc.d/

Re: "Input out of Range"

On 10/31/2014 11:02 AM, Beartooth issued this missive: > > I normally run three or four computers behind a 4-way KVM switch; > one of them is an old Dell PowerEdge SC1420, which began life as a > server, configured with RAID of some sort. It has long since been re- > purposed and re-config

Re: password troubles

On 10/31/2014 11:25 AM, Beartooth issued this missive: > I'm having troubles getting some PCs to accept their passwords, > either directly to sign in, or over ssh from another machine, or both. > I've even had a situation (more than once) where A would not let me ssh > in from B -- but I c

Re: password troubles

On Fri, 31 Oct 2014 18:25:23 + Beartooth wrote: > I'm having troubles getting some PCs to accept their passwords, > either directly to sign in, or over ssh from another machine, or both. > I've even had a situation (more than once) where A would not let me ssh > in from B -- but I co

password troubles

I'm having troubles getting some PCs to accept their passwords, either directly to sign in, or over ssh from another machine, or both. I've even had a situation (more than once) where A would not let me ssh in from B -- but I could ssh from B to C, and from C to A. No matter how

"Input out of Range"

I normally run three or four computers behind a 4-way KVM switch; one of them is an old Dell PowerEdge SC1420, which began life as a server, configured with RAID of some sort. It has long since been re- purposed and re-configured, and is now an ordinary old PC. I ran CentOS 6 on it for

Re: rc.local not start at the boot

On 10/31/14 22:56, Angelo Moreschini wrote: > 1) [root@zorro ~]# cat /dev/null > /var/log/audit/audit.log > [root@zorro ~]# > > # empty input > > 4) [root@zorro angelo_dev]# grep AVC /var/log/audit/audit.log > avcs > > 5) [root@zorro angelo_dev]# cat avcs =--- > empty > ([root@zorro angelo_dev]#

Re: A Linux for the totally maintenance free

On Fri, Oct 31, 2014 at 10:23 AM, Tom H wrote: > Judging from the hits that you get when you search for a problem, > Ubuntu. Although you do get many Arch hits, which is unsurprising > given how good its documentation is. Could you image a Fedora Wiki as good as the Arch Wiki? That would be amazi

Re: A Linux for the totally maintenance free

On Tue, Oct 28, 2014 at 2:26 AM, Tim wrote: > On Mon, 2014-10-27 at 11:44 -0400, Tom H wrote: >> >> Why don't you install Fedora and put up with having to use an external >> repo for non-free stuff (if necessary) and upgrading every 6 months or >> so? > > For some people, or lots of people, upgrad

Re: A Linux for the totally maintenance free

On Mon, Oct 27, 2014 at 12:39 PM, Bill Oliver wrote: > On Mon, 27 Oct 2014, Tom H wrote: >> >> You seem to be asking for the impossible. Whether you install Fedora, >> Ubuntu, OS X, or Windows, there are going to be regular updates. >> >> Why don't you install Fedora and put up with having to use

Gnome 3.12/3.14: how to define default keyboard layout

Hello I'm using Fedora 20 with Gnome 3.12 from Copr repo. I've found one bad regression in latest gnome versions. There is not possibility how to set default keyboard (I use "us" and "cs"). It seams that it use last state (even after reboot and new login). This is even worse when I set "Allow dif

Re: rc.local not start at the boot

1) [root@zorro ~]# cat /dev/null > /var/log/audit/audit.log [root@zorro ~]# # empty input 4) [root@zorro angelo_dev]# grep AVC /var/log/audit/audit.log > avcs 5) [root@zorro angelo_dev]# cat avcs =--- > empty ([root@zorro angelo_dev]# cat avcs -rw-r--r--. 1 root root 0 Oct 31 1

Re: Closing port 631 from other computers

Am 31.10.2014 um 10:34 schrieb Jarmo Hurri: > So I must be doing something wrong. My questions are: > > 1. Have I diagnosed the situation correctly? Is port 631 really open to >the outside world? Probably. > 2. If port 631 is open, why can I not close it using firewalld? You're very likely

Re: rc.local not start at the boot

On 10/31/14 20:49, Angelo Moreschini wrote: > SELINUX=permissive =--> didn't work > > setsebool -P rsync_full_access 1 =--> didn't work too > > > Do you have an actual user "programmers" defined? > yes : angelo_dev is a member of this group Well, this is crazy. I can recreate the symptoms

Re: rc.local not start at the boot

SELINUX=permissive =--> didn't work setsebool -P rsync_full_access 1 =--> didn't work too > Do you have an actual user "programmers" defined? yes : angelo_dev is a member of this group On Fri, Oct 31, 2014 at 2:16 PM, Ed Greshko wrote: > On 10/31/14 17:21, Ed Greshko wrote: > > The problem

Re: rc.local not start at the boot

On 10/31/14 17:21, Ed Greshko wrote: > The problem is related to "selinux". The selinux fix for this would be to issue this command as root, just once in a terminal session setsebool -P rsync_full_access 1 And then reboot. -- If you can't laugh at yourself, others will gladly oblige. --

Re: Closing port 631 from other computers

On 10/31/14 18:09, Jarmo Hurri wrote: > Ed Greshko writes: >> cupsd 2349 root 10u IPv4 37790 0t0 TCP *:ipp (LISTEN) >> Does indicate that it is listening on all interfaces. You can prevent >> this by editing your /etc/cups/cupsd.conf to contain the line >> Listen localhost:631 >> Which will r

gnutls, openssl and compiling mutt

Does it make any difference if mutt is compiled with '--with-gnutls' enabled or with '--with-openssl' enabled. Mutt (Fed20/21/Rawhide package) shows that '--with-gnutls' is used. I ask because I have no problem connecting to my ISP Ziggo with mutt when using Fedora. With the following in .muttrc

Re: rc.local not start at the boot

On 10/31/14 18:14, Angelo Moreschini wrote: > I tried : > > # this is the file /etc/rc./rc.local > /etc/rc.d/dummy-test.sh > #/etc/rc.d/syncronize-java_srcs.sh > su -c '/etc/rc.d/syncronize-java_srcs.sh' programmers Do you have an actual user "programmers" defined? > > -- > > but didn't work

Re: rc.local not start at the boot

I tried : # this is the file /etc/rc./rc.local /etc/rc.d/dummy-test.sh #/etc/rc.d/syncronize-java_srcs.sh su -c '/etc/rc.d/syncronize-java_srcs.sh' programmers -- but didn't work I understand what you are talking Ed, but I am a newbie and yet I am not able to manage problems concerning SELi

Re: Closing port 631 from other computers

Ed Greshko writes: > cupsd 2349 root 10u IPv4 37790 0t0 TCP *:ipp (LISTEN) > Does indicate that it is listening on all interfaces. You can prevent > this by editing your /etc/cups/cupsd.conf to contain the line > Listen localhost:631 > Which will result in > cupsd 2377 root 11u IP

Re: Closing port 631 from other computers

On 10/31/14 17:34, Jarmo Hurri wrote: > Greetings. > > After the recent security incidents I am trying to increase the security > of my computer by closing unnecessary ports from outside world. > > The only listening port in my system right now is port 631 (ipp), as > "lsof -i | grep -i listen" rep

Re: iptables adding rules not in /etc/sysconfig/iptables

On 30.10.2014 19:11, Tom Horsley wrote: ... > does. Also the default libvirtd service starts a bunch of > networking things for providing a default network that includes > some firewall tinkering (or used to, anyway). > $ rpm -qil libvirt-daemon-config-nwfilter Only for virtual network, therefore

Closing port 631 from other computers

Greetings. After the recent security incidents I am trying to increase the security of my computer by closing unnecessary ports from outside world. The only listening port in my system right now is port 631 (ipp), as "lsof -i | grep -i listen" reports: **

Re: rc.local not start at the boot

On 10/31/14 16:32, Ed Greshko wrote: > It is unfortunate that I've not been able to get any error message to > display. I have an idea of the problem and why no message is shownbut > again...too tired. OK I know what the problem is related to And, I know how to get around it (the

Re: smplayer OK

On 31.10.2014 09:53, Tim wrote: > On Thu, 2014-10-30 at 16:04 +0100, poma wrote: >> what's this? >> >> $ cat /etc/NetworkManager/conf.d/20-connectivity-fedora.conf >> [connectivity] >> uri=http://fedoraproject.org/static/hotspot.txt >> response=OK > > Doesn't exist on my systems. > > You're tal

Re: smplayer OK

On Thu, 2014-10-30 at 16:04 +0100, poma wrote: > what's this? > > $ cat /etc/NetworkManager/conf.d/20-connectivity-fedora.conf > [connectivity] > uri=http://fedoraproject.org/static/hotspot.txt > response=OK Doesn't exist on my systems. You're talking about the thing being debated on here about

Re: Driver for RTL8192su chipset

On 31.10.2014 09:43, poma wrote: > On 31.10.2014 02:10, jd1008 wrote: >> >> On 10/30/2014 06:39 PM, poma wrote: >>> On 30.10.2014 22:44, jd1008 wrote: On 10/26/2014 09:53 PM, poma wrote: > Subscribe, > http://vger.kernel.org/vger-lists.html#linux-wireless > and Larry_dot_Finge

Re: Driver for RTL8192su chipset

On 31.10.2014 02:10, jd1008 wrote: > > On 10/30/2014 06:39 PM, poma wrote: >> On 30.10.2014 22:44, jd1008 wrote: >>> On 10/26/2014 09:53 PM, poma wrote: >>> Subscribe, http://vger.kernel.org/vger-lists.html#linux-wireless and Larry_dot_Finger_at_lwfinger_dot_net is your pal. >>

Re: rc.local not start at the boot

On 10/31/14 16:22, Angelo Moreschini wrote: > Hi Rick, > > your suggestion seemed to be the right one .. > But still did not work ... > > I made now ​​one further try : > these are the listed files I used It isn't related to $PATH I'm too tired to explain again > > -

Re: rc.local not start at the boot

Hi Rick, your suggestion seemed to be the right one .. But still did not work ... I made now ​​one further try : these are the listed files I used -[angelo_dev@zorro rc.d]$ cat rc.local- #!/bin/bash /etc/rc.d/dummy-test.sh /etc/rc.d/syncronize-java_srcs.sh --