[CentOS] Bind Vulnerability CVE-2016-2775

2016-08-31 Thread Sidharth Sharma
Hello Experts,

When we can expect Security Update for Bind Vulnerability on Centos 6.8/7.2?
ISC BIND Lightweight Resolver Protocol Req Processing Dos Vulnerability:
CVE-2016-2775

-- 
With Thanks & Regards:
Sidharth Sharma
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] Perl Unsafe Module Path Handling Directory Traversal Vulnerability ( CVE-2016-1238)

2016-08-31 Thread Sidharth Sharma
Hello Experts,

When we can expect Security Update for Perl Vulnerability  CVE-2016-1238 on
CentOS 6.8 and 7.2?

-- 
With Thanks & Regards:
Sidharth Sharma
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] group write permissions not being respected

2016-08-31 Thread Chris Murphy
Try booting with enforcing=0 and if that fixes it, you need to find out
what security label is needed for gluster.

Chances are it's easiest to use -o context= mount option on the brick, but
if the brick is not exclusive to gluster you'll need chcon -R.

If that's not it, maybe try the gluster client instead of using NFS. See if
you get a different result that narrows down what's going on.

My vague recollection is for Samba, without the correct SELinux label, I
could neither read nor write.


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


[CentOS-docs] Addition to Wiki How-To Articles

2016-08-31 Thread Brock Hudson
BrockHudson

Proposed Subject: iSCSI Target Configuration

Proposed Location: How To's > Storagedevices, Logical Volume Management, and 
RAID > iSCSI Target Configuration


I'd also like to request a home page for myself as well.


Thank you.
___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs


Re: [CentOS] group write permissions not being respected

2016-08-31 Thread Pat Haley


For example the directory /gdata/bibliography/Work/GroupBib/trunk/ can 
be written in by user phaley but not by other users who are member of 
the group mseasweb.  The directory has permissions


[root@mseas ~]# ls -lh /gdata/bibliography/Work/GroupBib
total 12K
drwxrwsr-x 4 phaley mseasweb 4.0K Aug 30 12:31 trunk

The parent directory (/gdata/bibliography/Work/GroupBib) has permissions

[root@mseas ~]# ls -lh /gdata/bibliography/Work/
total 8.0K
drwxrwsr-x 6 phaley mseasweb 4.0K Aug 30 14:01 GroupBib



On 08/31/2016 02:04 PM, m.r...@5-cent.us wrote:

Stupid question, and note I missed most of the earlier posts in this
thread: what are the permissions on the directory that this directory are
in?

   mark

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


--

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Pat Haley  Email:  pha...@mit.edu
Center for Ocean Engineering   Phone:  (617) 253-6824
Dept. of Mechanical EngineeringFax:(617) 253-8125
MIT, Room 5-213http://web.mit.edu/phaley/www/
77 Massachusetts Avenue
Cambridge, MA  02139-4301

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


Re: [CentOS] group write permissions not being respected

2016-08-31 Thread m . roth
Stupid question, and note I missed most of the earlier posts in this
thread: what are the permissions on the directory that this directory are
in?

  mark

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


Re: [CentOS] group write permissions not being respected

2016-08-31 Thread Pat Haley


So far, those look the same

client:

[root@mseas FixOwn]# getfacl /gdata/bibliography/Work/GroupBib/trunk/
getfacl: Removing leading '/' from absolute path names
# file: gdata/bibliography/Work/GroupBib/trunk/
# owner: phaley
# group: mseasweb
# flags: -s-
user::rwx
group::rwx
other::r-x

server:

[root@mseas-data2 ~]# getfacl /gdata/bibliography/Work/GroupBib/trunk/
getfacl: Removing leading '/' from absolute path names
# file: gdata/bibliography/Work/GroupBib/trunk/
# owner: phaley
# group: mseasweb
# flags: -s-
user::rwx
group::rwx
other::r-x


On 08/31/2016 12:50 PM, Gordon Messmer wrote:

On 08/30/2016 03:01 PM, Pat Haley wrote:
the owner of a directory can still write to that directory but any 
other member of the associated group cannot, even though the 
directory clearly has group write permissions set



Use "getfacl" on both the client and server side to view the complete 
permission set.  What do those look like?


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


--

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Pat Haley  Email:  pha...@mit.edu
Center for Ocean Engineering   Phone:  (617) 253-6824
Dept. of Mechanical EngineeringFax:(617) 253-8125
MIT, Room 5-213http://web.mit.edu/phaley/www/
77 Massachusetts Avenue
Cambridge, MA  02139-4301

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


Re: [CentOS] CentOS 6 - logwatch report not in HTML format

2016-08-31 Thread Arun Khan
On Wed, Aug 31, 2016 at 8:59 AM, Alexander Farber
 wrote:
> You should have provided more info initially.
>
> "goes out in text format" might mean several things.
>

I don't know what you mean by "several things"

In the context of logwatch the only options are HTML or TEXT.  Please see my OP.

Thanks for your assistance.

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


Re: [CentOS] group write permissions not being respected

2016-08-31 Thread Gordon Messmer

On 08/30/2016 03:01 PM, Pat Haley wrote:
the owner of a directory can still write to that directory but any 
other member of the associated group cannot, even though the directory 
clearly has group write permissions set



Use "getfacl" on both the client and server side to view the complete 
permission set.  What do those look like?


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


Re: [CentOS] CentOS 6 - logwatch report not in HTML format

2016-08-31 Thread Alexander Farber
You should have provided more info initially.

"goes out in text format" might mean several things.

On Wed, Aug 31, 2016 at 5:31 PM, Arun Khan  wrote:

> On Wed, Aug 31, 2016 at 7:58 AM, Alexander Farber
>  wrote:
> > logwatch is run as cronjob.
>
> Let's take cron out of the picture.  Invoking logwatch from an
> interactive shell -- no joy.  The report still goes out in text
> format.
>
> -- Arun Khan
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6 - logwatch report not in HTML format

2016-08-31 Thread Arun Khan
On Wed, Aug 31, 2016 at 7:58 AM, Alexander Farber
 wrote:
> logwatch is run as cronjob.

Let's take cron out of the picture.  Invoking logwatch from an
interactive shell -- no joy.  The report still goes out in text
format.

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


Re: [CentOS] CentOS 6 - logwatch report not in HTML format

2016-08-31 Thread Alexander Farber
logwatch is run as cronjob.

On Wed, Aug 31, 2016 at 4:11 PM, Arun Khan  wrote:

> On Mon, Aug 29, 2016 at 10:24 PM, Alexander Farber
>  wrote:
> > No, I mean there is sometimes a variable for mail format too:
>
> The HTML formatting is a logwatch option, invoked through the
> logwatch.conf file.
>
> -- Arun Khan
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] NODEJS010-NPM is not getting installed due to dependency errors on Custom Centos ISO installation

2016-08-31 Thread Jim Perrin


On 08/31/2016 03:48 AM, SUDHANSHU BHUTANI wrote:
> Hi,
> 
> I have built successfully all the dependent packages of nodejs010 and npm.
> 
> I have used following command:-
> *rpmbuild --define 'scl nodejs010' --bb SPEC/name_of_spec.spec*

You should really use mock, so that you don't have unintended libraries
from your build host included/linked/required in the resulting rpm.
> 
> Following is the list of RPMs cloned and built from GIT:-
> 




> 
> *However, when we copy these RPMS to our ISO, anaconda installer fails
> to install due to dependency errors:-*


You should use the 'repoclosure' utility to make sure that you have met
all the dependencies of packages in the repo on your iso.



> How is it possible, to get these errors, how come packages are not
> satisfying minimum dependency for working of NPM?


repoclosure should tell you. You may be missing something scl related.


> 
> If i do yumdownloader for all these above RPMs from repo: [centos-sclo-rh]
> : http://mirror.centos.org/centos/7/sclo/x86_64/rh/nodejs010/), then i
> get following RPMs without "centos" name:-


Correct. This is an rpm macro change. by default the 'centos' is added
in there.


> 
> *If i copy paste above RPMS to my custom ISO, then anaconda
> successfully installs these packages, without any errors*


This would suggest something is wrong with your build. See previous
statement about using mock vs rpmbuild.


> *What is there is these already built RPMs (taken from repo: [centos-sclo-rh]
> : http://mirror.centos.org/centos/7/sclo/x86_64/rh/nodejs010/) which
> is not there in my built RPMS?*

That's kind of up to you to figure out, since we can't see your custom
built ones.


> Any pointers for this, as we feel, there is some inconsistency in the
> version available on git.centos.org/git/rpms/.git ?

More likely it's in your build method.


-- 
Jim Perrin
The CentOS Project | http://www.centos.org
twitter: @BitIntegrity | GPG Key: FA09AD77
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6 - logwatch report not in HTML format

2016-08-31 Thread Arun Khan
On Mon, Aug 29, 2016 at 10:24 PM, Alexander Farber
 wrote:
> No, I mean there is sometimes a variable for mail format too:

The HTML formatting is a logwatch option, invoked through the
logwatch.conf file.

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


[CentOS] NODEJS010-NPM is not getting installed due to dependency errors on Custom Centos ISO installation

2016-08-31 Thread SUDHANSHU BHUTANI
Hi,

I have built successfully all the dependent packages of nodejs010 and npm.

I have used following command:-
*rpmbuild --define 'scl nodejs010' --bb SPEC/name_of_spec.spec*

Following is the list of RPMs cloned and built from GIT:-

nodejs010-2.1-5.el7.centos.x86_64.rpm
nodejs010-http-parser-2.0-6.20121128gitcd01361.el7.centos.x86_64.rpm
nodejs010-http-parser-devel-2.0-6.20121128gitcd01361.el7.centos.x86_64.rpm
nodejs010-libuv-0.10.30-1.el7.centos.x86_64.rpm
nodejs010-libuv-devel-0.10.30-1.el7.centos.x86_64.rpm
nodejs010-node-gyp-3.2.0-2.el7.centos.noarch.rpm
nodejs010-nodejs-0.10.40-1.el7.centos.x86_64.rpm
nodejs010-nodejs-abbrev-1.0.5-1.el7.centos.noarch.rpm
nodejs010-nodejs-ansi-0.3.0-1.el7.centos.noarch.rpm
nodejs010-nodejs-ansicolors-0.3.2-1.el7.centos.noarch.rpm
nodejs010-nodejs-ansistyles-0.1.3-1.el7.centos.x86_64.rpm
nodejs010-nodejs-archy-1.0.0-1.el7.centos.noarch.rpm
nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.noarch.rpm
nodejs010-nodejs-array-index-0.1.1-1.el7.centos.noarch.rpm
nodejs010-nodejs-asap-1.0.0-4.el7.centos.noarch.rpm
nodejs010-nodejs-async-some-1.0.2-2.el7.centos.noarch.rpm
nodejs010-nodejs-balanced-match-0.2.1-2.el7.centos.noarch.rpm
nodejs010-nodejs-bl-1.0.0-1.el7.centos.noarch.rpm
nodejs010-nodejs-block-stream-0.0.7-2.el7.centos.noarch.rpm
nodejs010-nodejs-brace-expansion-1.1.1-2.el7.centos.noarch.rpm
nodejs010-nodejs-builtin-modules-1.1.0-1.el7.centos.noarch.rpm
nodejs010-nodejs-builtins-1.0.2-2.el7.centos.noarch.rpm
nodejs010-nodejs-caseless-0.11.0-1.el7.centos.noarch.rpm
nodejs010-nodejs-char-spinner-1.0.1-2.el7.centos.noarch.rpm
nodejs010-nodejs-chmodr-1.0.2-1.el7.centos.noarch.rpm
nodejs010-nodejs-chownr-1.0.1-1.el7.centos.noarch.rpm
nodejs010-nodejs-clone-0.2.0-3.el7.centos.noarch.rpm
nodejs010-nodejs-cmd-shim-2.0.0-2.el7.centos.noarch.rpm
nodejs010-nodejs-columnify-1.3.2-3.el7.centos.noarch.rpm
nodejs010-nodejs-concat-map-0.0.1-1.el7.centos.noarch.rpm
nodejs010-nodejs-concat-stream-1.4.4-5.el7.centos.noarch.rpm
nodejs010-nodejs-config-chain-1.1.9-1.el7.centos.noarch.rpm
nodejs010-nodejs-core-util-is-1.0.1-2.el7.centos.noarch.rpm
nodejs010-nodejs-debug-2.2.0-2.el7.centos.noarch.rpm
nodejs010-nodejs-debuglog-1.0.1-4.el7.centos.noarch.rpm
nodejs010-nodejs-defaults-1.0.0-5.el7.centos.noarch.rpm
nodejs010-nodejs-delegates-0.1.0-1.el7.centos.noarch.rpm
nodejs010-nodejs-devel-0.10.40-1.el7.centos.x86_64.rpm
nodejs010-nodejs-dezalgo-1.0.2-3.el7.centos.noarch.rpm
nodejs010-nodejs-editor-1.0.0-1.el7.centos.noarch.rpm
nodejs010-nodejs-forever-agent-0.5.0-2.el7.centos.noarch.rpm
nodejs010-nodejs-fstream-1.0.3-2.el7.centos.noarch.rpm
nodejs010-nodejs-fstream-ignore-1.0.2-1.el7.centos.noarch.rpm
nodejs010-nodejs-fstream-npm-1.0.1-1.el7.centos.noarch.rpm
nodejs010-nodejs-fs-vacuum-1.2.6-3.el7.centos.noarch.rpm
nodejs010-nodejs-fs-write-stream-atomic-1.0.3-3.el7.centos.noarch.rpm
nodejs010-nodejs-gauge-1.2.2-3.el7.centos.noarch.rpm
nodejs010-nodejs-github-url-from-git-1.4.0-1.el7.centos.noarch.rpm
nodejs010-nodejs-github-url-from-username-repo-1.0.0-1.el7.centos.noarch.rpm
nodejs010-nodejs-glob-5.0.15-1.el7.centos.noarch.rpm
nodejs010-nodejs-graceful-fs-4.1.2-3.el7.centos.noarch.rpm
nodejs010-nodejs-has-unicode-2.0.0-1.el7.centos.noarch.rpm
nodejs010-nodejs-hosted-git-info-2.1.4-3.el7.centos.noarch.rpm
nodejs010-nodejs-inflight-1.0.4-2.el7.centos.noarch.rpm
nodejs010-nodejs-inherits-2.0.0-13.el7.centos.noarch.rpm
nodejs010-nodejs-ini-1.2.0-1.el7.centos.noarch.rpm
nodejs010-nodejs-init-package-json-1.9.1-1.el7.centos.noarch.rpm
nodejs010-nodejs-is-absolute-0.2.3-3.el7.centos.noarch.rpm
nodejs010-nodejs-isarray-0.0.1-3.el7.centos.noarch.rpm
nodejs010-nodejs-is-builtin-module-1.0.0-1.el7.centos.noarch.rpm
nodejs010-nodejs-is-relative-0.2.1-2.el7.centos.noarch.rpm
nodejs010-nodejs-is-unc-path-0.1.1-2.el7.centos.noarch.rpm
nodejs010-nodejs-is-windows-0.1.0-3.el7.centos.noarch.rpm
nodejs010-nodejs-jju-1.2.1-1.el7.centos.noarch.rpm
nodejs010-nodejs-json-parse-helpfulerror-1.0.3-1.el7.centos.noarch.rpm
nodejs010-nodejs-json-stringify-safe-5.0.0-2.el7.centos.noarch.rpm
nodejs010-nodejs-lockfile-1.0.0-1.el7.centos.noarch.rpm
nodejs010-nodejs-lodash._basetostring-3.0.1-1.el7.centos.noarch.rpm
nodejs010-nodejs-lodash._createpadding-3.6.1-1.el7.centos.noarch.rpm
nodejs010-nodejs-lodash.pad-3.1.1-1.el7.centos.noarch.rpm
nodejs010-nodejs-lodash.padleft-3.1.1-1.el7.centos.noarch.rpm
nodejs010-nodejs-lodash.padright-3.1.1-1.el7.centos.noarch.rpm
nodejs010-nodejs-lodash.repeat-3.0.1-1.el7.centos.noarch.rpm
nodejs010-nodejs-lru-cache-2.7.0-1.el7.centos.noarch.rpm
nodejs010-nodejs-mime-db-1.15.0-3.el7.centos.noarch.rpm
nodejs010-nodejs-mime-types-2.1.3-1.el7.centos.noarch.rpm
nodejs010-nodejs-minimatch-3.0.0-1.el7.centos.noarch.rpm
nodejs010-nodejs-minimist-0.0.8-1.el7.centos.noarch.rpm
nodejs010-nodejs-mkdirp-0.5.0-1.el7.centos.noarch.rpm
nodejs010-nodejs-ms-0.7.1-2.el7.centos.noarch.rpm
nodejs010-nodejs-mute-stream-0.0.4-3.el7.centos.noarch.rpm