Discuss

discuss@lists.centos.org

34753 discussions

Re: [CentOS] Using gpg to encrypt a URL line on CentOS 6 additional information
by Jerry Geis 13 Jul '15

13 Jul '15

>+1. also, it'd probably be good to state what you're trying to accomplish rather >than if you can throw a technology at vague something or another. I think you'd >find gpg's password input cumbersome for symmetric keys, the output too long in ascii >armor and possibly annoying to deal with public keys... but you don't really say what >you're trying to fix/avoid/do/not do. Sorry if I wasnt being clear enough.... it basically comes down to this. I use an apache interface to my application, the URL line has parameters line mscript?value=2&something=4 etc.. I have a "crude" encoding (wouldnt even call it encryption) that I use right now. I'd like to make that more robust. I started looking and found mcrypt (which I mentioned in the first post) But that did not compile from source, and is not available in the standard yum install. Other repos have it but that may not be an option for me due to other reasons.... No problem. So I started thinking about does GPG support something similiar like mcrypt? Easy way to encrypt a line for URL. That is where my goal lies... Way to encrypt a URL string with what is "standard" in CentOS 6. Thanks, Jerry

3 2

Installing from USB
by Jerry Geis 12 Jul '15

12 Jul '15

I found this http://wiki.centos.org/HowTos/InstallFromUSBkey So for centos 7 if did the dd command seemed to work great. I did the install. So now I'd like to "modify" the USB key to add a boot menu option with my customer install options. I mounted /dev/sdb2 and edited the file /mnt/usb/EFI/BOOT/grub.conf added my menu item and rebooted to try to use it. It does not show up in the menu. How do I get the USB to use my new menu? Thanks Jerry

2 1

Re: [CentOS] puppet files denied by SELinux
by Tim Dunphy 12 Jul '15

12 Jul '15

Hi all, Thanks for all your suggestions. Here's where I'm at with this. Can you give details about your puppetmasterd setup ? it seems that > you're using Foreman as puppet ENC. > Yes, I'm on foreman 1.7.4 and puppet 3.75. You are correct that I'm using foreman, sorry I hadn't thought to mention it! > Foreman works fine with selinux enabled : that's what we use for the > centos.org infra :-) > Which version of puppet/foreman are you using ? Note that foreman has > the foreman-selinux package that is used to automatically tune > contexts and booleans needed for this. > You can still reapply those settings with > /usr/sbin/foreman-selinux-{disable,enable,relabel} > There is no need to recompile a custom selinux policy for > foreman/puppet those days > I didn't recompile any custom selinux policies. All I did to try to resolve the issue is to consult audit2allow and install the module it suggested. I did try running /usr/sbin/foreman-selinux-enable but that didn't seem to have an effect. Knowing nothing of your scenario, look at the source and target context. > > Looks like you copied a crt from an nfs location and you don't have a > file context defined to transition labels, maybe something like: > > semanage fcontext -a -t passenger_t "/etc/puppet/environments(/.*)?" > > However, I know nothing of puppets selinux infrastructure, you may need > a more applicable type. > > In these cases, audit2allow can't possibly guess the right thing and will > certainly produce a rule that is either unsafe or simply wrong. > You are correct that I copied the key and cert from an NFS share! Both the puppet server and the monitor1 client share the same /home directory via NFS. Pretty cool that you picked up on that! I do suspect you're probably right that this may be causing the problem. Just on a hunch, I tried copying the certs and keys from the montior1 host over to the puppet host to the /tmp directory on the puppet server. That leaves out NFS altogether. And when I do that, my bacula puppet module WORKS!! Puppet doesn't complain at all! But if I check out another host where I copied the cert and key from the NFS home directory I still get the error: Error: /Stage[main]/Bacula::Config/File[/etc/pki/tls/private/monitor2.mydomain.com.key]: Could not evaluate: Could not retrieve information from environment production source(s) puppet:///modules/bacula/monitor2/monitor2.mydomain.com.key Error: /Stage[main]/Bacula::Config/File[/etc/pki/tls/certs/monitor2.mydomain.com.crt]: Could not evaluate: Could not retrieve information from environment production source(s) puppet:///modules/bacula/monitor2/monitor2.mydomain.com.crt Also when I try to set context using the line you suggested I get an error: #semanage fcontext -a -t passenger_t "/etc/puppet/environments(/.*)?" ValueError: Type passenger_t is invalid, must be a file or device type So I googled around and found what seems to be the correct syntax: semanage fcontext -a -t passenger_exec_t "/etc/puppet/environments(/.*)?" Because when I applied that line, I didn't get any errors or complaints. However the problem still existed on the monitor2 host which had the key pair copied from the NFS share. So in summary it appears that there is some interaction between SELinux and NFS that is causing the issue. Any thoughts? Thanks, Tim On Sun, Jun 21, 2015 at 11:09 AM, Tim Dunphy <bluethundr(a)gmail.com> wrote: > Yes, you did when you used the audit2allow with the -M option argument >> of "puppet", which is confirmed by the command you issued to try to load >> it "semodule -i puppet.pp" (which you stated in your original message). >> I'm okay with you asserting otherwise and not following my first >> suggestion -- my second is to use a totally different name, e.g., "barf" >> and thus "semodule -i barf.pp". > > > Haha!! Ok man. I get you now. Thanks. Also I meant to send this to the > list.. Whoops! I'll try doing it again with something like 'my' in the > front. I remember having a similar problem with Zabbix last week that I > solved this way. > > On Sun, Jun 21, 2015 at 12:19 AM, Mark Milhollan <mlm(a)pixelgate.net> > wrote: > >> On Sat, 20 Jun 2015, Tim Dunphy wrote: >> >I wrote: >> >> >> That suggests there's already a module named puppet, and thus you are >> >> replacing it with the one you made which does not supply the >> >> puppet_var_lib_t type. Always prefix your own modules with something >> >> that makes them almost certain to be unique, e.g., yourdom_puppet. >> >> >> > >> >No, actually I didn't compile my own selinux module. :) Not sure how you >> >got that idea, but that is not the case. >> >> Yes, you did when you used the audit2allow with the -M option argument >> of "puppet", which is confirmed by the command you issued to try to load >> it "semodule -i puppet.pp" (which you stated in your original message). >> I'm okay with you asserting otherwise and not following my first >> suggestion -- my second is to use a totally different name, e.g., "barf" >> and thus "semodule -i barf.pp". >> >> >> /mark >> > > > > -- > GPG me!! > > gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B > > -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

2 3

Mounting NFS file systems via Nautilus on CentOS 6
by Toralf Lund 11 Jul '15

11 Jul '15

Hi, I'm trying to set up my "work" laptop, which has CentOS 6.6, for easy NFS access to a "NAS" disk at home. I can't set for a normal "permanent" mount, since most of the time, the filesystem will not be available. I know several different ways to mount temporarily from the command line, but I was hoping I could set up the system so I could mount by clicking in the file browser (Nautilus.) I can't seem to find a way to do this, though. I've tried two different approaches: 1. Add an entry of the form server:/directory /directory nfs rw,users,noauto to /etc/fstab. 2. Add a location of the form /net/server/directory to Bookmarks - as the filesystem is mounted automatically when entering this location, provided that autofs is enabled with the default configuration. Unfortunately, neither of these methods work out quite right. Setting up fstab as outlined in 1. means that I can mount the filesystem as a regular user by issuing "mount /directory", but I can't find a direct way to issue this command from the GUI: I actually thought a relevant entry would show up just like that under Places and/or computer:///, but apparently not. This could be related to what's described in https://bugzilla.gnome.org/show_bug.cgi?id=536292, although it mentions that the problem is fixed in GNOME 2.28, and I thought the CentOS 6 had a newer version than that. Method 2. does cause the filesystem to be mounted, but the problem is that it happens too often. The idea was of course that the mount would occur when selecting the bookmark, but it looks like Nautilus will actually try to access the location before that, so that the filesystem pretty much stays mounted at all times. If the disk is available, that is, I haven't tested yet what happens when it isn't, but others with different Linux variants report that Nautlius will lock up completely because it can't get data for the location. So, does anyone have any idea how to best set up the system do to what I want (see above)? I guess I might create special "mount" and "unmount" launchers, but I'd prefer a solution that's more integrated with the normal file browser operation. Thanks, - Toralf

1 0

Using gpg to encrypt a URL line on CentOS 6.
by Jerry Geis 11 Jul '15

11 Jul '15

Is there a way to use GPG to encrypt a URL line with parameters ? I was looking at libmcrypt also but it is not part of CentOS. I have found examples for mcrypt but not for gpg. Thoughts? Thanks. jerry

3 2

Re: [CentOS] OT, hardware: HP smart array drive issue
by m.roth＠5-cent.us 10 Jul '15

10 Jul '15

Jason Warr wrote: > On July 10, 2015 11:47:09 AM CDT, m.roth(a)5-cent.us wrote: >> Hi. Anyone working with these things? I've got a drive in "predictive >> failure" on in a RAID5. Now here's the thing: there was an issue >> yesterday when I got in, and I wound up power cycling the RAID; >> first boot of attached server had issues, and said the controller >> had a failure, and a drive had failed, and wouldn't continue >> booting; when I gave it the three-finger salute, this time on the >> way up, during POST, it noted the controller issue... but the >> thing came up, looking like it did a couple of days ago. >> >> Trying to prevent this from happening again, I've decided to replace >> the drive that's in predictive failure. The array has a hot spare. >> I tried to remove, using hpacucli, it refuses "operation not >> permitted", and there doesn't *seem* to be a "mark as failed" >> command. *Do* I just yank the drive? >> > Yep, just yank it. It should start auto rebuilding on the spare. > > If you didn't have a spare you would pull the suspect drive and replace it > with one of equal or greater capacity and it would auto rebuild as well. > > I have a bunch of them at home and have been using them at work for years. Thanks for your quick reply, Jason. I'm used to LSI/MegaRAID/PERCs, where you have to fail it, first. Oddity: I had the drive out for more then five minutes while getting it out of the sled, putting the new one in, oh, and dusting out the slot (gotta do that for all of them, next maintenance window), but after I put in the replacement, and used hpacucli to check, to my surprise it was rebuilding with the replacement, *not* with the spare. mark

3 2

HP Elitebook 8460p
by Phil Dobbin 10 Jul '15

10 Jul '15

Hi, all. I'm intending to install CentOS 7 on a HP Elitebook 8460p. Does anybody have any experience of this? Many thanks for any help. Cheers, Phil...

2 2

CentOS-announce Digest, Vol 125, Issue 4
by centos-announce-request＠centos.org 10 Jul '15

10 Jul '15

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2015:1218 Moderate CentOS 6 php Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 9 Jul 2015 19:23:41 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2015:1218 Moderate CentOS 6 php Security Update Message-ID: <20150709192341.GA59281(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2015:1218 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1218.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 97908585a91585137ccb6eee94f45568936c29c3358ddcf2f0fecef66aa807e3 php-5.3.3-46.el6_6.i686.rpm 904b300d398ee3d5ce0f55e4099c45f51b7753c855720c7d1c245cf5425b7f3e php-bcmath-5.3.3-46.el6_6.i686.rpm 53a07be26838874150138ca397e92eb467ba682b7cbc6d9fade3e9979cc2ca57 php-cli-5.3.3-46.el6_6.i686.rpm 09bb5673d2894ddf9de223ded3f9a1eef51956301d6ba735be10c0246cd4ffb5 php-common-5.3.3-46.el6_6.i686.rpm e1235f6cffd68c85eaa0216db76f4b628d5e9aa5b080936f6c4e82397440715e php-dba-5.3.3-46.el6_6.i686.rpm 72b398096f27035b56e4e46223d18e76692c771e7a2cdadebf8808da9c782ab3 php-devel-5.3.3-46.el6_6.i686.rpm 7b65855b6c9f6bfa7fb760ce61335974bd0d43e8713ae573243cf83986b594b6 php-embedded-5.3.3-46.el6_6.i686.rpm a52c5dfb1e0eb52c83965c0dc5e6b7ff1c6c50553fe1a9b29e49b977f0aeae0d php-enchant-5.3.3-46.el6_6.i686.rpm 1e287c54d1b76e9adc169ca6b446e08c1b7013f2c68408eae0c79923f3c58d73 php-fpm-5.3.3-46.el6_6.i686.rpm 18d933596c1def34379b5d0d1bf9a789ca0034d3930bbe1566dddfad6085bbd5 php-gd-5.3.3-46.el6_6.i686.rpm 3042e3eaed7876445b3acf07ef482259fe8413f3e4e55405d1d76366d8afde8b php-imap-5.3.3-46.el6_6.i686.rpm 3e5fc5c46acb4fb1249f2b3e8e580caa07f4cda05e8e2dbef83d2f81dcd845ff php-intl-5.3.3-46.el6_6.i686.rpm a40d0e8fafb5d54cde0cae013ef3ab19b559fd93dc8a8cb6ab93a0ebc3147bfa php-ldap-5.3.3-46.el6_6.i686.rpm 75b0cf46e035aed61c4714a517b2ccef8850cfadeb9543e34eb18b6dfdf398cb php-mbstring-5.3.3-46.el6_6.i686.rpm 9ca19170b19d9c6917dc407fafeb31d4cb7ad76992bee021cdcb976c021571e4 php-mysql-5.3.3-46.el6_6.i686.rpm 6e85aaa43ee1dd174292fbcdd8e3e35ced65e8d69a88b6266acc0add645a7163 php-odbc-5.3.3-46.el6_6.i686.rpm 82256356a0bde09f945f99096815423dc675ce853380d4ae6d4c15567ba066a2 php-pdo-5.3.3-46.el6_6.i686.rpm 22d30a8346618e1f09e266ba2b22b491e8daa65c5eb6c4bb86cc05329ce3c60d php-pgsql-5.3.3-46.el6_6.i686.rpm 2693447fa0ad5632f248b7f3e07c8b418dc36da5d117fb30ae80e7a26c05ac6e php-process-5.3.3-46.el6_6.i686.rpm 164b189cac9a834a9721c4f323d6e3a58ac0cdfefd64dcc21607de54556c9bfe php-pspell-5.3.3-46.el6_6.i686.rpm 0a278f4abe0eb142c864e1087c93b8d127adcb5708299e98f39453393aad8922 php-recode-5.3.3-46.el6_6.i686.rpm efeae4c0cbbc4a9d7643fc13f93d5665e4ef99c900de565dd34346e81d0fa64c php-snmp-5.3.3-46.el6_6.i686.rpm 3b32736c6698616a820f187ed430140f7ac93c9e6b478aa140b87bda0218a3ae php-soap-5.3.3-46.el6_6.i686.rpm b76458a0d402e52d3eb0bed3c8276c469165d3290cffa934b47674065041bad1 php-tidy-5.3.3-46.el6_6.i686.rpm 98c57680a6582c2460c7c4f95153e19560b0a9b762f531bdc88d6251e3243bf9 php-xml-5.3.3-46.el6_6.i686.rpm 11e4721c452a2e691e71d2e4530d0bd03e1817a7bfd36a99170b70bcdfef9231 php-xmlrpc-5.3.3-46.el6_6.i686.rpm 1b10dcc2a9140e3b515c5a5028e1ec29898b92d914ab2b0d4be892f4e25c0a5f php-zts-5.3.3-46.el6_6.i686.rpm x86_64: 0c45509eff8fe9176329691a60dbfde48d3ad02fa496c8c383d180203d605d63 php-5.3.3-46.el6_6.x86_64.rpm c7a9ea7d8e9250adcd45312394cdf57969490e18d5f46f48b788333b1cdce512 php-bcmath-5.3.3-46.el6_6.x86_64.rpm 017d7ae9cca8701ee461634d5baae9598cf78921955a4f77de85d6f5eb0109f6 php-cli-5.3.3-46.el6_6.x86_64.rpm 6b78b92fbd734e70743913c684ab1859850fdb8ac5eaf17b167e37444c883202 php-common-5.3.3-46.el6_6.x86_64.rpm 7b7c7712e78b169d49a0dbb91a58c8a9e755df347067e563258e85475081f685 php-dba-5.3.3-46.el6_6.x86_64.rpm 20fa622e155bf1ff739152321105bc91b3d5b99a312ec0bf5336905016c05b51 php-devel-5.3.3-46.el6_6.x86_64.rpm 94c0f77389b09896ee9e1053671cc592a03b6e817a9da200118eb533bd63c648 php-embedded-5.3.3-46.el6_6.x86_64.rpm 729dee2897ced5fade373520d2fa3328c065263a369177b1baa1bd3bc0d1992d php-enchant-5.3.3-46.el6_6.x86_64.rpm ab2a88d6f414d008354e987b2eca4641bc72cbc24d348120d04a1a2675732173 php-fpm-5.3.3-46.el6_6.x86_64.rpm 01f2a681f2b90511dc4b4db3a4a8b70fe604cf31e08c6e0fb8a3c2e97000801c php-gd-5.3.3-46.el6_6.x86_64.rpm ba53e43da7c07501d1ef7aea5a6c903324d129dded436b90a63627d18ec8ed1f php-imap-5.3.3-46.el6_6.x86_64.rpm bddd9dcfde4a79a59eb54a3690e29a8a37564371cb7608220aeb0340182368be php-intl-5.3.3-46.el6_6.x86_64.rpm 128e84cad9089e4711cb02455ce72a3ef0c0b4a5d999e1b7dab6959741adb45d php-ldap-5.3.3-46.el6_6.x86_64.rpm 5165459e1ea4da86459560da795df01f14127be1b91de3b3b811692b28b14276 php-mbstring-5.3.3-46.el6_6.x86_64.rpm 42557a4431d3ede06908fc44341ac50a612d418f524b8faec10e52212028da05 php-mysql-5.3.3-46.el6_6.x86_64.rpm 405080398f52c8cdfa5f15b5d579b9d488da62f9f86c934d51dadd0e6ef86f42 php-odbc-5.3.3-46.el6_6.x86_64.rpm 9289e97429bc379173e2b6b87026b9c7356678001369d1e215d12e28cdd21e56 php-pdo-5.3.3-46.el6_6.x86_64.rpm e28c0ef558d544a7d8691943e038e026af971ad518ec180c2513e3958765289e php-pgsql-5.3.3-46.el6_6.x86_64.rpm c402a8a8392752be1be1ca12a0ba70cd9720d50efd6021fc362c68a1aa9f1aa0 php-process-5.3.3-46.el6_6.x86_64.rpm b4ccefafc18c5b2f8cdd859ff32c244e79e5eaae6f80a06d15878ec7803203ef php-pspell-5.3.3-46.el6_6.x86_64.rpm 0dcac5d3afadbf4b259006bfef3f244c932fe5ab185febd944fa5ce4deea8a02 php-recode-5.3.3-46.el6_6.x86_64.rpm 9b6314836113114c39c98c05e33239b576b1b05cd05546d041ade7713cfb0dcd php-snmp-5.3.3-46.el6_6.x86_64.rpm 56f79deea445b7aeef8b4e27d357fb5e186454e43d53867a75de5362e73d9a69 php-soap-5.3.3-46.el6_6.x86_64.rpm 7de2b9c2794b0d3f2dc2c2add872cfeb8735503a50902e75b70a81b288490180 php-tidy-5.3.3-46.el6_6.x86_64.rpm 7de7c01300061c237e602983706f2871e5826e4ac7ab8c72dcba7a773d641f3e php-xml-5.3.3-46.el6_6.x86_64.rpm 0d10a266d7d66030604e03493b027ff63f366fdee3e2aad71b3efbf467c8e22a php-xmlrpc-5.3.3-46.el6_6.x86_64.rpm aee49ee856e2ab0d777e4724f141953cef239281220aa212cd5c2b9d34e2eccd php-zts-5.3.3-46.el6_6.x86_64.rpm Source: bb6d33cfdb1f35409416d43f456161085c9c6b11f0a24147a9368a0a7cc4f2e1 php-5.3.3-46.el6_6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 125, Issue 4 ***********************************************

1 0

built kernel-3.10.0-229.7.2.el7 OK but install fails
by Nicholas Geovanis 10 Jul '15

10 Jul '15

Hi all - First the boilerplate: On centos-release.x86_64 7-0.1406.el7.centos.2.3 [root@localhost x86_64]# uname -a Linux localhost.localdomain 3.10.0-123.el7.x86_64 #1 SMP Mon Jun 30 12:09:22 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux [root@localhost x86_64]# rpm -qa kernel\* | sort kernel-3.10.0-123.el7.x86_64 kernel-devel-3.10.0-123.el7.x86_64 kernel-headers-3.10.0-123.el7.x86_64 kernel-tools-3.10.0-123.el7.x86_64 kernel-tools-libs-3.10.0-123.el7.x86_64 I built kernel-3.10.0-229.7.2.el7, successfully to appearances. But on installing the new rpms I receive a couple dozen messages like these: [root@localhost x86_64]# rpm -ivh kernel-*.rpm Preparing... ################################# [100%] file /usr/lib64/libcpupower.so.0.0.0 from install of kernel-tools-libs-3.10.0-229.7.2.el7.centos.local.x86_64 conflicts with file from package kernel-tools-libs-3.10.0-123.el7.x86_64 file /usr/bin/cpupower from install of kernel-tools-3.10.0-229.7.2.el7.centos.local.x86_64 conflicts with file from package kernel-tools-3.10.0-123.el7.x86_64 Have I missed a step? Maybe something specific to 7 or different from 6? Thanks.....Nick

3 5

mcrypt 2.6.8 on centos 6
by Jerry Geis 10 Jul '15

10 Jul '15

I downloaded mcyrpt 2.6.8, untar, cd into the tree and did ./configure and I get errors. checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking for libmcrypt-config... no checking for libmcrypt - version >= 2.5.0... no *** Could not run libmcrypt test program, checking why... *** The test program failed to compile or link. See the file config.log for the *** exact error that occured. This usually means LIBMCRYPT was incorrectly installed *** or that you have moved LIBMCRYPT since it was installed. In the latter case, you *** may want to edit the libmcrypt-config script: no configure: error: *** libmcrypt was not found I'm still on ./configure not the make Anyone installed from source? I found libmcrypt on a fedora repo but its only 2.5.8 Thanks! Jerry

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss