Re: [CentOS] Suddenly OpenVPN not working - backgrounds prompt for username / password
So it seems that now when I use --daemon it backgrounds BEFORE prompting for my password instead of after So I am good as long as I don't do that. Why this all of a sudden? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fedora change that will probably affect RHEL
On 07/25/2015 05:00 PM, Gordon Messmer wrote: > On 07/25/2015 11:45 AM, Jake Shipton wrote: >> I think a better solution to suite both worlds would be to simply have a >> boot flag on the installation media such as maybe >> "passwordcheck=true/false" > > https://xkcd.com/1172/ > > It's practically a law that every time someone's workflow is broken, > they request an option to change it. Personally, I'm against it. > Putting a weak password into the installer *is* a request for a weak > password. There's no reason to request a weak password twice (with a > boot arg and a weak password) when the alternative is to graphically > represent the password strength and let the user decide. > > I don't like the change, but at the same time I do all of my installs > with kickstart, and such installs are not affected. Kickstart files can > contain a hashed password, and since a hashed password can't be checked, > it can't be rejected. Thus, any decision FESCO makes won't affect me at > all. One thing that people don't understand or don't want to address is that most KNOWN instances of a Linux machine being hacked/owned/pwned/taken over (substitute your word here) and then rooted happen because of weak passwords. It is certainly one's own right (at least in my country) to be completely and utterly stupid with your decision making ... but if you have any paying clients who have information on any machines you manage and said clients information gets stolen, if you have weak passwords then expect to shell out some cash for your stupid decision making. Thank God we are not still using the computer code we did in 1991 when Linux started. Changes impact people, but good for us that the code has changed and moved forward. If people want weak passwords, I guess you can let people have them .. but it is an idiotic thing to do. It is also one that makes you liable if you lose someone's privacy information because of your decision. That is just MY opinion .. yours may vary. Thanks, Johnny Hughes signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fedora change that will probably affect RHEL
On 07/26/2015 08:13 AM, Johnny Hughes wrote: > On 07/25/2015 05:00 PM, Gordon Messmer wrote: >> On 07/25/2015 11:45 AM, Jake Shipton wrote: >>> I think a better solution to suite both worlds would be to simply have a >>> boot flag on the installation media such as maybe >>> "passwordcheck=true/false" >> >> https://xkcd.com/1172/ >> >> It's practically a law that every time someone's workflow is broken, >> they request an option to change it. Personally, I'm against it. >> Putting a weak password into the installer *is* a request for a weak >> password. There's no reason to request a weak password twice (with a >> boot arg and a weak password) when the alternative is to graphically >> represent the password strength and let the user decide. >> >> I don't like the change, but at the same time I do all of my installs >> with kickstart, and such installs are not affected. Kickstart files can >> contain a hashed password, and since a hashed password can't be checked, >> it can't be rejected. Thus, any decision FESCO makes won't affect me at >> all. > > One thing that people don't understand or don't want to address is that > most KNOWN instances of a Linux machine being hacked/owned/pwned/taken > over (substitute your word here) and then rooted happen because of weak > passwords. > > It is certainly one's own right (at least in my country) to be > completely and utterly stupid with your decision making ... but if you > have any paying clients who have information on any machines you manage > and said clients information gets stolen, if you have weak passwords > then expect to shell out some cash for your stupid decision making. > > Thank God we are not still using the computer code we did in 1991 when > Linux started. Changes impact people, but good for us that the code has > changed and moved forward. > > If people want weak passwords, I guess you can let people have them .. > but it is an idiotic thing to do. It is also one that makes you liable > if you lose someone's privacy information because of your decision. > > That is just MY opinion .. yours may vary. Gordon, just to make sure you (and others on the list) understand .. I have no issue with your specific post .. I probably should have replied to the OP's mail instead, but yours was the last I read on this thread. signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] C6.6 Gnome panel problem
Hi all!
I usually keep the panels on my Centos 6.6 (Gnome) so they auto-hide,
but t'other day I wanted to keep the top panel visible for a while to
make the clock visible for doing some rough timings.
so I open the top panel, click properties, and UNcheck the "autohide"
checkbox, close the properties menu, and to my surprise, the panel
still autohides. Went thru that exercise several times ("come on guys,
lets keep doing the same thing over and over til it works!", like
congress does)
So I open up the gnome configuration editor and browse around to find
apps/panel/default_setup/toplevels/top_panel and
apps/panel/toplevels/top_panel.
neither one has a check in the checkbox for autohide, so I'm at a
loss here as to what's going on.
Anybody out there got any clues?
thanks!
Fred
--
---
Under no circumstances will I ever purchase anything offered to me as
the result of an unsolicited e-mail message. Nor will I forward chain
letters, petitions, mass mailings, or virus warnings to large numbers
of others. This is my contribution to the survival of the online
community.
--Roger Ebert, December, 1996
- The Boulder Pledge -
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C6.6 Gnome panel problem
On 07/27/2015 05:34 AM, Fred Smith wrote:
Hi all!
I usually keep the panels on my Centos 6.6 (Gnome) so they auto-hide,
but t'other day I wanted to keep the top panel visible for a while to
make the clock visible for doing some rough timings.
so I open the top panel, click properties, and UNcheck the "autohide"
checkbox, close the properties menu, and to my surprise, the panel
still autohides. Went thru that exercise several times ("come on guys,
lets keep doing the same thing over and over til it works!", like
congress does)
So I open up the gnome configuration editor and browse around to find
apps/panel/default_setup/toplevels/top_panel and
apps/panel/toplevels/top_panel.
neither one has a check in the checkbox for autohide, so I'm at a
loss here as to what's going on.
Anybody out there got any clues?
Did you try logging out and back in? Shouldn't be the case but it is
gnome after all
thanks!
Fred
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
[CentOS] wicd problem 0: i have started having problems wicd and network connections
greetings, system: CentOS = 6.6 - current updates KDE = 4.3.4 Network Manager = 0.8.1 wicd = 1.7.0 (bzr-r552) from what i have read in threads, it appears that 'wicd' is recommended network controller over 'network manager'. because of this, i installed wicd and tried to use. i find this strange because i see problems when using 'wicd'. in attempt to understand what and where problem may be, i have tried various ways of checking for problem. to post what i have found, i am posting in 6 parts to hopefully make it easier for help in troubleshooting by breaking down what i have found. comments and suggestions most welcome. tia. -- If Bill Gates got a dime for every time Windows crashes... ...oh, wait. He does. THAT explains it! -+- in a world with out fences, who needs gates. CentOS GNU/Linux 6.6 tc,hago. g . ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] wicd problem 2: wicd does not sync when ifconfig commands are given from a terminal
greetings, during past week or so, i have been having problems with mozilla firefox locking up kde desktop and i have to open a terminal to reboot system. to insure that i get kde back to a desired state, i make backups of ~/.kde path when ever i change any settings of kde. after system reboots and desktop manager is displayed, i to terminal, delete current ~/.kde, then copy ~/.kde-backup to ~/.kde. while in terminal, i run 'ifconfig' to see if network is connected, which it is, so i 'sudo ifconfig eth0 down' to disconnect. after starting kde, wicd icon in system tray is showing wicd has connection to network, which it does not. when i click wicd icon and then select 'disconnect', and close wicd window, then reopen wicd and select 'connect', there is no connection. a 3rd problem i see with 'wicd' is in post "Subject: wicd problem"; 3: wicd blocking 1st attempt connection for firefox and yumex -- If Bill Gates got a dime for every time Windows crashes... ...oh, wait. He does. THAT explains it! -+- in a world with out fences, who needs gates. CentOS GNU/Linux 6.6 tc,hago. g . ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] wicd problem 1: wicd allows network to be connected on reboot
greetings, i find this strange because i see problems when using 'wicd'. 1st problem is that wicd allows network to be connected on reboot, even when network is disconnected at time of reboot. such does not seem to be good because i leave system up 24/7/365 and if there is a mains failure and ups takes system down, system will come back up with network connected, which i prefer not to have happen. is there a way to set up 'wicd' so that it does not start connected? a 2nd problem i see with 'wicd' is in post "Subject: wicd problem"; 2: wicd does not sync when ifconfig commands are given from a terminal -- If Bill Gates got a dime for every time Windows crashes... ...oh, wait. He does. THAT explains it! -+- in a world with out fences, who needs gates. CentOS GNU/Linux 6.6 tc,hago. g . ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] wicd problem 3: wicd blocking 1st attempt connection for firefox and yumex
greetings, wicd is preventing firefox and yumex to connect to internet. when i first try to connect to a web site with firefox, i get err message; Unable to connect when i click [Try Again], connection is made. all further connection attempts are ok. when i try to run yumex, i get error message; Not connected to a network. Do you want to continue selecting [Yes] continues starting yumex, but i have active repositories. when i run yum cl command; ]$ yum check-update Loaded plugins: aliases, changelog, downloadonly, fastestmirror, presto, : refresh-packagekit, security, tmprepo, verify, versionlock Determining fastest mirrors Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=6&; arch=x86_64&repo=os error was 14: PYCURL ERROR 6 - "Couldn't resolve host 'mirrorlist.centos.org'" Error: Cannot find a valid baseurl for repo: base when i run yum cl command again; ]$ yum check-update Loaded plugins: aliases, changelog, downloadonly, fastestmirror, presto, : refresh-packagekit, security, tmprepo, verify, versionlock Loading mirror speeds from cached hostfile epel/metalink | 13 kB 00:00 which indicates yum has made connection. a 4th problem i see with 'wicd' is in post "Subject: wicd problem"; 4: wicd restarts itself when as root user making terminal commands -- If Bill Gates got a dime for every time Windows crashes... ...oh, wait. He does. THAT explains it! -+- in a world with out fences, who needs gates. CentOS GNU/Linux 6.6 tc,hago. g . ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] wicd problem 5: wicd restarts itself when as user making terminal commands
greetings, following are command line problems as user using virtual terminals. ]$ ifconfig;date eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20f:feff:fe8f:8f23/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1419 errors:0 dropped:0 overruns:0 frame:0 TX packets:709 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:117028 (114.2 KiB) TX bytes:87298 (85.2 KiB) Interrupt:19 Memory:f018-f01a loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:334 errors:0 dropped:0 overruns:0 frame:0 TX packets:334 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:25264 (24.6 KiB) TX bytes:25264 (24.6 KiB) virbr0Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:23 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3505 (3.4 KiB) Sun Jul 26 21:43:27 CDT 2015 [geo@boxen ~]$ sudo ifconfig eth0 down;date [sudo] password for geo: Sun Jul 26 21:44:26 CDT 2015 [geo@boxen ~]$ ifconfig;date eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23 inet6 addr: fe80::20f:feff:fe8f:8f23/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1454 errors:0 dropped:0 overruns:0 frame:0 TX packets:722 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:119920 (117.1 KiB) TX bytes:88850 (86.7 KiB) Interrupt:19 Memory:f018-f01a loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:334 errors:0 dropped:0 overruns:0 frame:0 TX packets:334 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:25264 (24.6 KiB) TX bytes:25264 (24.6 KiB) virbr0Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:23 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3505 (3.4 KiB) Sun Jul 26 21:44:39 CDT 2015 [geo@boxen ~]$ sudo ifconfig eth0 down;date Sun Jul 26 21:45:08 CDT 2015 [geo@boxen ~]$ ifconfig;date eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:1471 errors:0 dropped:0 overruns:0 frame:0 TX packets:746 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:121128 (118.2 KiB) TX bytes:93189 (91.0 KiB) Interrupt:19 Memory:f018-f01a loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:334 errors:0 dropped:0 overruns:0 frame:0 TX packets:334 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:25264 (24.6 KiB) TX bytes:25264 (24.6 KiB) virbr0Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:23 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3505 (3.4 KiB) Sun Jul 26 21:45:13 CDT 2015 [geo@boxen ~]$ ifconfig;date eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23 inet6 addr: fe80::20f:feff:fe8f:8f23/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1483 errors:0 dropped:0 overruns:0 frame:0 TX packets:778 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:122580 (119.7 KiB) TX bytes:99082 (96.7 KiB) Interrupt:19 Memory:f018-f01a loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:334 errors:0 dropped:0 overruns:0 frame:0 TX packets:334 errors:0 d
[CentOS] wicd problem 4: wicd restarts itself when as root user making terminal commands
greetings, to further check wicd problem, i decided to run test as root user and as user. i verified wicd problems 1, 2, 3 happen when logged in as root user. to further test wicd problems, i tried a few command line problems using virtual terminals. in following, note changing of status for eth0. [root@boxen Documents]# ifconfig eth0 down [root@boxen Documents]# ifconfig eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:886 errors:0 dropped:0 overruns:0 frame:0 TX packets:491 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:78924 (77.0 KiB) TX bytes:63994 (62.4 KiB) Interrupt:19 Memory:f018-f01a loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:296 errors:0 dropped:0 overruns:0 frame:0 TX packets:296 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:22964 (22.4 KiB) TX bytes:22964 (22.4 KiB) virbr0Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:22 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3417 (3.3 KiB) [root@boxen Documents]# ifconfig eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20f:feff:fe8f:8f23/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:900 errors:0 dropped:0 overruns:0 frame:0 TX packets:520 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:80504 (78.6 KiB) TX bytes:69267 (67.6 KiB) Interrupt:19 Memory:f018-f01a loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:296 errors:0 dropped:0 overruns:0 frame:0 TX packets:296 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:22964 (22.4 KiB) TX bytes:22964 (22.4 KiB) virbr0Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:22 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3417 (3.3 KiB) [root@boxen Documents]# ifconfig eth0 down;ifconfig;date loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:296 errors:0 dropped:0 overruns:0 frame:0 TX packets:296 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:22964 (22.4 KiB) TX bytes:22964 (22.4 KiB) virbr0Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:22 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3417 (3.3 KiB) Sun Jul 26 21:30:00 CDT 2015 [root@boxen Documents]# ifconfig;date eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20f:feff:fe8f:8f23/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:993 errors:0 dropped:0 overruns:0 frame:0 TX packets:575 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:87572 (85.5 KiB) TX bytes:76022 (74.2 KiB) Interrupt:19 Memory:f018-f01a loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:296 errors:0 dropped:0 overruns:0 frame:0 TX packets:296 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:22964 (22.4 KiB) TX bytes:22964 (22.4 KiB) virbr0Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST
Re: [CentOS] wicd problem 0: i have started having problems wicd and network connections
On 7/26/2015 9:18 PM, g wrote: from what i have read in threads, it appears that 'wicd' is recommended network controller over 'network manager'. recommended by whom ?rhel and therefore centos use network manager. wicd is used by arch and some other distributions... wicd is not available via the base centos repository, either. -- john r pierce, recycling bits in santa cruz ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
