[CentOS-announce] CEBA-2016:1349 CentOS 7 lvm2 BugFix Update

[Johnny Hughes]

CentOS Errata and Bugfix Advisory 2016:1349 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1349.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
9f8f2152738415ddef6509c16881468f8abedf7488490bfe724561ee7eb582c7  
cmirror-2.02.130-5.el7_2.5.x86_64.rpm
e23f39c92b83682c140324b0891d426bf538fbdc68cf7f267c2a87356816d89c  
device-mapper-1.02.107-5.el7_2.5.x86_64.rpm
0c3dc7d9d7957e749ad019f06e0cc1c87f3db76cb500457050ce2c3e46080b8b  
device-mapper-devel-1.02.107-5.el7_2.5.i686.rpm
4da48171c8f599255dd47809d5ed2cdbd23afe152c44540e4e6c41bb88cf7f6b  
device-mapper-devel-1.02.107-5.el7_2.5.x86_64.rpm
b1f004cceca52345c14d2dec35b44d989d39003d3a0e37ae14ee08210296e157  
device-mapper-event-1.02.107-5.el7_2.5.x86_64.rpm
6a8203ef009bd1dae1c2575bfaa89582a5d9b402e9a450ce3a787c22ead8f4a6  
device-mapper-event-devel-1.02.107-5.el7_2.5.i686.rpm
a2a822a1de226771fd00b9d6bce566def68a67b5c4ef1351f7d4e756a3d23e03  
device-mapper-event-devel-1.02.107-5.el7_2.5.x86_64.rpm
44d8c251698d60f8bf82d71d774652c7743515edd9077a780bb33709303188e6  
device-mapper-event-libs-1.02.107-5.el7_2.5.i686.rpm
59b65674dcab344b3d219b6961722bfd40780455bc0bce6bd02edd6dd768453c  
device-mapper-event-libs-1.02.107-5.el7_2.5.x86_64.rpm
8475f1a20a99c5f1d041187a531b5c5406c67bf84afb926096d11810f1a53d8e  
device-mapper-libs-1.02.107-5.el7_2.5.i686.rpm
4d964e6a7643010f2862791e2588e08f6011e4c656540d61d3ebe937ac9ce13a  
device-mapper-libs-1.02.107-5.el7_2.5.x86_64.rpm
b7a90ef80f4e8ddb35257802a57c07660e1ddc7e2c4a9957edf382ff67ec1567  
lvm2-2.02.130-5.el7_2.5.x86_64.rpm
65a4c81480d0efba21f0da7969a2f820d69e26934af24bf4fdb8c449a2d502dc  
lvm2-cluster-2.02.130-5.el7_2.5.x86_64.rpm
04d6d35438ff31602702872775f9fdc758c94d1e9656319dcfa09580ef21609d  
lvm2-devel-2.02.130-5.el7_2.5.i686.rpm
e53af702e6143a89598e64754410bbdbb079fb3e5b657091d88f44fec28fa391  
lvm2-devel-2.02.130-5.el7_2.5.x86_64.rpm
abafec8cbed90c9e68a796b61235bab160be70a8d0a8290041d78c155d41804e  
lvm2-libs-2.02.130-5.el7_2.5.i686.rpm
6c0f6537d19eecc549c1c7adf01cdee3aa6d805b30496946fbcc73cb4b3fe582  
lvm2-libs-2.02.130-5.el7_2.5.x86_64.rpm
39727f939e993c9baac491080ef3901b3d18536c3c4a7e12668bf381f15f99e9  
lvm2-lockd-2.02.130-5.el7_2.5.x86_64.rpm
2f3b320f5108eef429344b89416a2fcf6e15a47e014faeff5b47c6a3ebe234a3  
lvm2-python-libs-2.02.130-5.el7_2.5.x86_64.rpm
53316ba2995b27f5b7a4137817a66cd811c42c4ce286e682869d565f5bae76be  
lvm2-sysvinit-2.02.130-5.el7_2.5.x86_64.rpm

Source:
399d8210953038b445e7ac3fc91fc13b517b11dc1a849f820f17296a27477a56  
lvm2-2.02.130-5.el7_2.5.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

Re: [CentOS] Errors on yum upgrade

[henimp]

OK, thank you.

It's odd, being first time I've seen such yum error in many years of  
yum updates.



Quoting J Martin Rushton :


I've seen it before on several occasions and yet the directory tree
was removed.  I should just ignore it.  I suspect that find or similar
is just getting its ordering wrong.


On 28/06/16 02:55, hen...@openmail.cc wrote:

During yum upgrade a couple days ago, I saw this:

Cleanup: kernel-3.10.0-229.20.1.el7.x86_64
 35/64 warning: file
/lib/modules/3.10.0-229.20.1.el7.x86_64/modules.softdep: remove
failed: No such file or directory warning: file
/lib/modules/3.10.0-229.20.1.el7.x86_64/modules.devname: remove
failed: No such file or directory

Should I be concerned about this? What could have caused it?






-

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the 
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  
___

CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] .NET on Centos.

[Warren Young]

On Jun 28, 2016, at 12:03 PM, Warren Young  wrote:
> 
> ...but the F# project (--lang f#) chokes due to a version incompatibility.  
> This should shake out soon.

I’ve since learned that the problem is already fixed in the code, it is just 
working its way out to a released version at the moment.

> Beware that .NET Core is not the same thing as .NET.

Since my previous post, I stumbled across this well-written “what it is/is not” 
type of document from the core project:

  https://github.com/dotnet/core-docs/blob/master/docs/core/index.md

Well worth a read if you are at all curious about why you’d care about .NET on 
CentOS, or why we need a second implementation.

> As for stability, it’s still pre-1.0.

...on CentOS, I mean.  I’ve just seen the news that 1.0.0 final binaries are 
shipping on other platforms.

But by that very token, why are you asking about stability and security so 
early?  1.0.0 of *anything* is rarely rock-solid, and you can’t say the first 
version of *anything* is secure until it’s been proven over time to be so.

Give it time.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Errors on yum upgrade

[J Martin Rushton]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I've seen it before on several occasions and yet the directory tree
was removed.  I should just ignore it.  I suspect that find or similar
is just getting its ordering wrong.


On 28/06/16 02:55, hen...@openmail.cc wrote:
> During yum upgrade a couple days ago, I saw this:
> 
> Cleanup: kernel-3.10.0-229.20.1.el7.x86_64
>  35/64 warning: file
> /lib/modules/3.10.0-229.20.1.el7.x86_64/modules.softdep: remove
> failed: No such file or directory warning: file
> /lib/modules/3.10.0-229.20.1.el7.x86_64/modules.devname: remove
> failed: No such file or directory
> 
> Should I be concerned about this? What could have caused it?
> 
> 
> -
> 
> ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email
> out of the NSA's hands! $24.95 ONETIME Lifetime accounts with
> Privacy Features! 15GB disk! No bandwidth quotas! Commercial and
> Bulk Mail Options! ___ 
> CentOS mailing list CentOS@centos.org 
> https://lists.centos.org/mailman/listinfo/centos
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJXcu1PAAoJEAF3yXsqtyBlGLgP/220+vQdtxwIpZ6P7fBqA2QC
ngGKdkkomSMTWylvdJjd0KGZ+GZAnntMihjH7hsHYAtSjxf38nW1QygpzUF8SjhA
jqwaBphk851Hp4mQ0c6B1lBnLXoN4OQO9NYX42IqWQY7Uyo3wyoTxi0k6sluP81a
skfTL7ynJ2Gj8Q2Y2qM6vxuCpnDtnbiMoPEs/dNQiV/O6oACQLGa0tIrjQ4ngP/x
mI7gpr9vroFhf2U24fG6KL9FewtU9nnMVUNjF1qN/Q6z6TKX3XNgf9y//N81Czkd
j9hhyj7euKPOry5gLA6nsmMx9h/AZfXCGrMVTB1JQvHT/Lokb75acX89+mmKLHeB
2Ibd2DDyc7oZ6CHZj5FgIELGQz50D5ivX0TYoKM32dp2DBv2o+eMQT7SF5h8+VLO
zFJIHZ+DdZ4iFngp9v5s1ZoOeXCY+KcRU0b6wml3z0R+ZGvNhbxxq8r326h6hSt3
5yif7hX0ApDHhIrXAH7h/YuKdfDYv6hIvVx4sF8y8QlohY81DE0vYrpnmO7PeBcC
7r8UAGirWqTaZOeK/hqKcN8pwFq1Q3oasKlDxLePAey0CMSfpCa0Jfh8+0eVdLcJ
nLPN1U68+owXTF4d85IpQb43lV/NkF+wr83ISNOa8TLlxyzDSHEt4iU561pMAEtq
H2aJoEFdJMTXis1XrbIn
=JgUL
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] .NET on Centos.

[Dan Pacek]

the .net bits were pushed to git.centos on friday as far as we know

Dan


On 06/28/2016 01:52 PM, Johnny Hughes wrote:
> On 06/28/2016 12:17 PM, Peter Q. wrote:
>> Hi there, I was reading about it.
>> https://www.redhat.com/en/about/blog/net-core-now-available-and-supported-red-hat-enterprise-linux-and-red-hat-openshift
>>
>> What will happen with Centos and .NET?
>> In the side of security and stability.
> 
> That announcement, and this website:
> 
> http://developers.redhat.com/dotnet/
> 
> Are both Microsoft and Red Hat initiatives / agreements.  The .NET being
> discussed is in OpenShift containers running on Microsoft's Azure Cloud.
> 
> None of that is currently slated, to the best of my knowledge, to be
> rolled into the Base distribution for RHEL.  Therefore it is also not
> being  added into the CentOS Linux distribution.  If / when Red Hat does
> add things into the base RHEL Server, Workstation, Desktop platforms and
> releases the source code for it, we will of course rebuild that source
> code and add the resulting software to CentOS Linux.
> 
> Another method of getting things into the CentOS universe is to start a
> Special Interest Group that provides optional software to CentOS
> repositories (Currently things like Xen support, GlusterFS, Ceph, RDO,
> Software Collections, Opennfv, etc). I do not know of any current or
> planned .NET SIG for CentOS.  There certainly could be one in the future
> (if there is interest), or one of the current SIGs might need to bring
> in .NET for developing software for their SIG.  But I currently know of
> no one bringing it in.
> 
> Microsoft has stated that will also make .NET Core available for Ubuntu,
> Debian and CentOS Linux.  That is not something that I know anything
> about right now either.
> 
> The CentOS team certainly welcomes development software like .NET being
> provided by the software owner for use on CentOS Linux.
> 
> Thanks,
> Johnny Hughes
> 
> 
> 
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
> 


-- 
Dan Pacek
Competitive Intelligence Analyst
Red Hat - Platform Business Unit
dpa...@redhat.com
PH: 1-978-392-3138
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] .NET on Centos.

[Warren Young]

On Jun 28, 2016, at 11:17 AM, Peter Q.  wrote:
> 
> What will happen with Centos and .NET?

I’d expect it to show up in SCL at some point:

  https://wiki.centos.org/AdditionalResources/Repositories/SCL

Until then, the CentOS build instructions on Microsoft’s official download page 
work just fine, at least on EL7:

  https://www.microsoft.com/net/core#centos

RC3 apparently just shipped, which has caused some version incompatibilities in 
the .NET package repositories.  I was able to get the default C# “hello, world” 
project to build and run:

$ mkdir test
$ cd test
$ dotnet new --lang c#
$ dotnet restore
$ dotnet build
$ dotnet run
Hello World!

...but the F# project (--lang f#) chokes due to a version incompatibility.  
This should shake out soon.

Beware that .NET Core is not the same thing as .NET.  It is very much stripped 
down compared to the Windows .NET platform.  It is mainly intended for headless 
server-side applications, like serving ASP.NET sites.

> In the side of security and stability.

I’m guessing you’re asking if .NET Core will be secure.  I assume it will be as 
secure as any VM type interpreter, such as Java or Flash.  That is to say, 
theoretically quite secure, but in practice only as secure the platform’s 
maintainers put in the effort to make it secure.  My advice: wrap it in 
SELinux, VMs, chroots, etc., just as you would any other executable code you 
want walled off from the rest of your infrastructure.

As for stability, it’s still pre-1.0.  Don’t bet your business on it today.  If 
you need a stable .NET implementation for Linux today, use Mono.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] .NET on Centos.

[Johnny Hughes]

On 06/28/2016 12:17 PM, Peter Q. wrote:
> Hi there, I was reading about it.
> https://www.redhat.com/en/about/blog/net-core-now-available-and-supported-red-hat-enterprise-linux-and-red-hat-openshift
> 
> What will happen with Centos and .NET?
> In the side of security and stability.

That announcement, and this website:

http://developers.redhat.com/dotnet/

Are both Microsoft and Red Hat initiatives / agreements.  The .NET being
discussed is in OpenShift containers running on Microsoft's Azure Cloud.

None of that is currently slated, to the best of my knowledge, to be
rolled into the Base distribution for RHEL.  Therefore it is also not
being  added into the CentOS Linux distribution.  If / when Red Hat does
add things into the base RHEL Server, Workstation, Desktop platforms and
releases the source code for it, we will of course rebuild that source
code and add the resulting software to CentOS Linux.

Another method of getting things into the CentOS universe is to start a
Special Interest Group that provides optional software to CentOS
repositories (Currently things like Xen support, GlusterFS, Ceph, RDO,
Software Collections, Opennfv, etc). I do not know of any current or
planned .NET SIG for CentOS.  There certainly could be one in the future
(if there is interest), or one of the current SIGs might need to bring
in .NET for developing software for their SIG.  But I currently know of
no one bringing it in.

Microsoft has stated that will also make .NET Core available for Ubuntu,
Debian and CentOS Linux.  That is not something that I know anything
about right now either.

The CentOS team certainly welcomes development software like .NET being
provided by the software owner for use on CentOS Linux.

Thanks,
Johnny Hughes



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] .NET on Centos.

[Peter Q.]

Hi there, I was reading about it.
https://www.redhat.com/en/about/blog/net-core-now-available-and-supported-red-hat-enterprise-linux-and-red-hat-openshift

What will happen with Centos and .NET?
In the side of security and stability.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] UDP Constant IP Identification Field Fingerprinting Vulnerability

[James B. Byrne]

On Mon, June 27, 2016 12:29, Gordon Messmer wrote:
> On 06/26/2016 01:50 PM, James B. Byrne wrote:
>> However, all I am seeking is knowledge on how to handle this using
>> iptables.  I am sure that this defect/anomaly has already been
>> solved wherever it is an issue.  Does anyone have an example on
>> how to do this?
>
>
> I think the bit you're missing is that you don't have to address every
> detail that your auditors send you.  You can label an item a false
> positive.  You can respond that you are aware, and that you don't
> consider an item to be a security defect.  Fingerprinting is an
> excellent example thereof.  As was already noted, the IP ID field is
> just one of many aspects of IP networking that can be used to identify
> Linux systems.  If you don't address them all, addressing one is not a
> useful exercise.

I understand WRT false positive flagging.  And that is exactly what I
have done.  However, the PCI DSS report piqued my interest in this
matter and I thought to satisfy my curiosity.  The other stuff flagged
in the report seemed a little far-fetched to me. At least the
explanation of why they were flagged did.

As none of them affect our PCI status I have no interest in the rest.
This one however I was previously unaware and so I wanted to discover
more about it.

Thank you for the information and especially for the references.

Sincerely,



-- 
***  e-Mail is NOT a SECURE channel  ***
Do NOT transmit sensitive data via e-Mail
 Do NOT open attachments nor follow links sent by e-Mail

James B. Byrnemailto:byrn...@harte-lyne.ca
Harte & Lyne Limited  http://www.harte-lyne.ca
9 Brockley Drive  vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada  L8E 3C3

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] VNC server issue- Gnome - oh no! Something has gone wrong

[Hersh]

I forgot to mention, I have followed steps mentioned in this link
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-TigerVNC.html
for configuring vnc.

I have also tried upgrading VNCserver but that didn't help either.

Regards
Hersh

On 28 June 2016 at 15:39, Hersh  wrote:

> Hi,
>
> I have been using VNC on CentOS 7 server from last couple of months and it
> was running all fine till last night. Unfortunately, there was an abrupt
> power failure and system got restarted.  Now, when I try to login with
> VNCviwer, it thrown an error message-  "*Gnome - oh no! Something has
> gone wrong "*  with a logout option. When I click on logout, I see
> black/dark gray screen with 3 check boxes.
>
> I googled to figure out a solution and tried several solutions but could
> not fix the problem. Any suggestion would be very helpful.
>
> Regards
> Hersh
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] VNC server issue- Gnome - oh no! Something has gone wrong

[Hersh]

Hi,

I have been using VNC on CentOS 7 server from last couple of months and it
was running all fine till last night. Unfortunately, there was an abrupt
power failure and system got restarted.  Now, when I try to login with
VNCviwer, it thrown an error message-  "*Gnome - oh no! Something has gone
wrong "*  with a logout option. When I click on logout, I see black/dark
gray screen with 3 check boxes.

I googled to figure out a solution and tried several solutions but could
not fix the problem. Any suggestion would be very helpful.

Regards
Hersh
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Guest's Additions Virtual CD

[raving Joker]

Hello to everyone I'm a new italian member so I'm sorry if my english isn't
perfect.
I was thinking...
Why not (in CentOS 7) insert a tab in the installation phase that can
permit an automatic installation of guest's additions tools (I'm using
virtualbox, but it can be applied to other platforms with a menu), a little
system that reveals the guest addition's cd and if isn't inserted, displays
to the user a message with informations about how insert it and do the
installation automatically?

Thanks for all of people that want to reply, I know that this
virtualization platforms are in part in discordance with the ethical free
software's mindset...but why not in centos, with proper informative
messages?

Good afternoon

Raving
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Use USB2.0 Camera with KVM based VM

[Gordon Messmer]

On 06/27/2016 05:20 PM, Mark LaPierre wrote:

The reply to the bug post went on to say that the problem is that the
USB 2.0 camera will not work with the USB 1.1 default hub and that I
should change the hub from USB 1.1 to USB 2.0.

I see no way to do that.


I don't either, but maybe this is helpful...  According to this 
document, you can specify the bus that a USB device is attached to, 
including pass-through devices:

http://git.qemu.org/?p=qemu.git;a=blob_plain;f=docs/usb2.txt;hb=HEAD

So, one option would be to create a shell script that modifies the 
arguments given to qemu-system-x86_64, and then use "virsh edit " 
to replace the default emulator with the path to your shell script.  I 
do that for a guest where I pass through a video card, which needs a PCI 
express bridge:


$ cat /usr/local/bin/qemu-system-x86_64-passthrough
#!/bin/bash

declare -a qemuargs

for x in "$@"
do
if test "${x:0:21}" == "vfio-pci,host=01:00.0"
then
qemuargs+=(ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1)
qemuargs+=(-device)
qemuargs+=(vfio-pci,host=01:00.0,id=hostvga,bus=root.1,addr=00.0,multifunction=on)
else
qemuargs+=("$x")
fi
done

/usr/bin/qemu-system-x86_64 "${qemuargs[@]}"

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos