Discuss July 2015

discuss@lists.centos.org

116 participants
114 discussions

LUKS encypted partition using --key-file can only be decrypted with --key-file
by Digimer 15 Sep '15

15 Sep '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I created a LUKS encrypted partition via a udev-triggered script on 6.6 using --key-file /tmp/foo. This worked fine, and I can decrypt the LUKS partition via script and manually using --key-file with luksOpen. The odd problem is that I can't decrypt the partition using the prompt. If I manually create a file with the passphrase in it and then point to it with --key-file, it decrypts fine. I used 'cat -A /tmp/foo' to verify that there was no '\n' at the end of the phrase. Is this expected behaviour? That is; If you create an encrypted partition using --key-file, you always decrypt with the same? If so, I can't understand the logic... If not, then I am not sure what I am doing wrong. Thanks for any insight! digimer - -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJU93ZLAAoJECChztQA3mh0swwP/2PX3Y3TmEEIeN7WxWQjnbX0 B+hdp3Yk1PBqaQ/FsOzGsnKnxOUu73fB25gDksEWnNedBru4ayJuYPW644rH8Ivr fS8Pz3y6buGqUaggzsGNaGfDOKtiLOp722OeuPUmaNHnGCE3qJbhE3RKBRrMl4SP Yi/otL8+85cp4isMESOYs3F5qw/osDmmKxktPbULbTrne94EWHHl+9RoSFDZFNCj JBsNE122WUtn+2JPV8it8nlIS/Kzqzv3qGR88lYiBj3y3F+zIbpix/8wyCgRVSw6 /LQwLSTmGKYdvLw2Td7oIqMrW69ZsgujAonnbyx2nl9WN3KSqr799SxL4n2M7ZOj a1MjcLdLr0kM28eu+/A3LyHQRkBVsz7f27e7M+drEVa4OHFS3KuL4EM47xkTGyps veljkNmZ8elL7PX+dmWsVGYyo4XH/bTFDcW8ZLhr+bc55xLplMRrhPNNFGQ+5k3R ev7HRhSqHD9Ub39KTea4WCJOsm0hJJgKYneWYmQJ1aVYmrFMHLJaJBzCqU+W751O GkXvU24eoajNKnIAcY9wrC/WzVru8dM2JwBefcatxCsWFhpcpSyrh0zhCAiZKOga hjskIq/54Il8YyzSVy5Xvwv8WACBUwoiPv6ZqVm3oKRkoZI3E14vVYTcG+b0cPqn S30qAHntsjFA70Hpedt5 =YYFB -----END PGP SIGNATURE-----

3 3

SAMBA as AD DC
by Sergio Belkin 11 Sep '15

11 Sep '15

Hi folks, Is able SAMBA on CentOS 7 to work as Active Directory Domain Controller? If it's not, what is the recommended way of doing? Compiling from sources? Install packages from SerNet? Thanks in advance! -- -- Sergio Belkin http://www.sergiobelkin.com LPIC-2 Certified - http://www.lpi.org

9 14

How to setup own i686 buildenv for CentOS7
by Robin Lee 07 Sep '15

07 Sep '15

Hi, all! How to setup own i686 mock for CentOS7? Or, is there any public i686 repo for CentOS7? I found i686 repo available in internal CentOS building environment, from a root.log from a mock build result[1]. [1] http://buildlogs.centos.org/c7-updates/glibc/20141218212615/2.17-55.el7_0.3… Cheers, -robin

3 5

Suddenly OpenVPN not working - backgrounds prompt for username / password
by Alan McKay 10 Aug '15

10 Aug '15

Hi folks, I'm on a fresh install of CentOS 7 and take my config that works on Ubuntu on the same box. Instead of getting a prompt for username and password for the VPN I get a backgrounded task that spits this out : [amckay@centos-gig ~]$ sudo openvpn --config /home/amckay/data/vpn.ovpn --daemon Broadcast message from root@centos-gig (Sat 2015-07-25 22:59:13 EDT): Password entry required for 'Enter Auth Username:' (PID 23461). Please enter password with the systemd-tty-ask-password-agent tool! [amckay@centos-gig ~]$ I actually started having the same problem at work when trying to connect to our management network. Different config file. CentOS 7 though. Same config file works great on Ubuntu. Been googling it but not much luck. thanks, -Alan -- “Don't eat anything you've ever seen advertised on TV” - Michael Pollan, author of "In Defense of Food"

3 3

whois command in c6
by John R Pierce 09 Aug '15

09 Aug '15

the whois command in c6 references whois.v6nic.net for ip addresses in the 43.0.0.0/8 range (and maybe others). v6nic is no longer a valid whois server, any nets delegated to it should instead be delegated to apnic. i have no upstream connections... this change was made in the generic sources for jwhois some time ago I see this fix was introduced in F20 here, https://bugzilla.redhat.com/show_bug.cgi?id=1121512 -- john r pierce, recycling bits in santa cruz

5 7

why no recent bind update for CentOS 6?
by Noam Bernstein 06 Aug '15

06 Aug '15

Hi CentOS developers - I’ve been happily using CentOS for several years now, so thanks for all the good work. In the last week, however, I noticed that while the items in RHSA-2015:1443 has shown up as updates (and announced on centos-announce), the analogous update for CentOS 6, RHSA-2015:1471 (according to https://access.redhat.com/security/cve/CVE-2015-4620), doesn’t seem to be there. Is there any reason why those of us using CentOS 6 are left behind, and/or any idea when a CentOS 6 bind update will be available? thanks, Noam

12 27

RHEL 6.7 is released
by Devin Reade 05 Aug '15

05 Aug '15

Now don't go bugging people asking when CentOS 6.7 will be out. "When it's ready." In upgrading from RHEL 6.6 to 6.7, I did find that I had to disable my 3rd party repos (elrepo and epel) in order to avoid yum erroring out. Plus I did the usual "yum clean all". (I don't use the PackageKit GUI as it's been unable to complete for quite a few months without dumping core.) Devin

5 5

OT - parted guidance
by Ken Smith 02 Aug '15

02 Aug '15

Hi All, Slightly OT as this is on a Centos 6 system I'm getting the fdisk message "partition does not start on a physical sector boundary" on a 4096 sector disk. I understand why this has happened. I just want to be sure of my parted syntax before I really mess things up. (before anyone says it - I know - do a backup) parted says that the offending partition 5 begins at 512 byte sector no. 462999615. Its the first partition in the extended partition that begins at 462999552. If I just want to move the partition back to the nearest 4096 boundary, which is 462999608, would the syntax be unit s move 5 462999608 Will parted sort itself out copying sector nos 462999615 to 462999608 and then 462999616 to 462999609 and on an on? Or will it not cope with jiggling the partition down the disk by 7 sectors? Thanks Ken -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

5 8

CentOS Continuous Release Repository updated with CentOS-6.7 RPMs
by Johnny Hughes 01 Aug '15

01 Aug '15

The packages that will become CentOS-6.7, as well as updates completed for CentOS-6.7 to date are now released into the CentOS-6.6 Continuous Release (CR) repository. All packages except for the centos-release RPM are included. The purpose of the CR repository is to make the built packages optionally available to users who opt in while we work on the CentOS-6.7 install tree and all the CentOS-6.7 install media and images. Normally the full release follows the CR release in 7-14 days if you do not use the CR process. For more info on the CR repository, see this link: http://wiki.centos.org/AdditionalResources/Repositories/CR If you want to enable CR on CentOS-6.6, use the command: yum install centos-release-cr You would then get the updates with the command: yum upgrade Known issues: 1. sssd-common is no longer multilib in CentOS 6.7. If you have the 32bit sssd-common installed on your x86_64 system, you will need to remove it with yum remove sssd-common.i686 prior to updating. 2. The boost RPMs are built with cmake-2.8 and the configuration files produced cause issues building some source code. There are an upstream bugs here (which is likely NOT being fixed): https://bugzilla.redhat.com/show_bug.cgi?id=849791 https://bugzilla.redhat.com/show_bug.cgi?id=1245805 and there are related CentOS issues found previously: http://bugs.centos.org/view.php?id=8117 If you are using boost to create packages, you can use the switch: "-DBoost_NO_BOOST_CMAKE=ON" To build sources that exhibit this issue. 3. The satyr package from EPEL is newer than the version included in CentOS-6.7. The package from EPEL seems to work OK as well, but they are likely to remove it as it also conflicts with RHEL-6.7. We have not observed any negative impacts from this issue. 4. yum-plugin-downloadonly has been obsoleted by yum and that functionality is now built into the default yum package. More information: 1. These CentOS packages are built from the RHEL-6.7 source code released by Red Hat on July 22, 2015. Please review the release and technical notes for that release here: http://red.ht/1JnEsVQ http://red.ht/1gdBkRu 2. The CentOS release notes for CentOS-6.7, currently a work in progress and not really complete until the final 6.7 release, are available here: http://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.7 3. The package set includes 243 Source RPMs updated and are broken down as: 21 Security Updates: 0 Critical Security 1 Important Security 16 Moderate Security 4 Low Security 25 Enhancement Updates 197 Bugfix Updates Individual per-package release announcements are available here: http://lists.centos.org/pipermail/centos-cr-announce/2015-July/thread.html -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net

4 3

livecd vs nfsroot vs what?
by Nux! 01 Aug '15

01 Aug '15

Hi, I'm trying to deploy some non-linux OS via pxe and I was thinking to just launch CentOS in RAM and then run dd or qemu-img or something like this in order to complete the other OS install via template imaging. My first idea was to build a custom CentOS livecd and use that in combination with pxe kernel parameters, but perhaps there's a better way to do this. Ideas? Thanks, Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss July 2015