JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for CCP4BB Archives


CCP4BB Archives

CCP4BB Archives


CCP4BB@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CCP4BB Home

CCP4BB Home

CCP4BB  August 2014

CCP4BB August 2014

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Disturbing feature with access rights

From:

Peter Keller <[log in to unmask]>

Reply-To:

Peter Keller <[log in to unmask]>

Date:

Thu, 21 Aug 2014 10:50:47 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (106 lines)

Dear Leo,

On Thu, 2014-08-21 at 05:24 +0200, CHAVAS Leonard wrote:
> Dear all
> 
> I came along a disturbing feature and I would appreciate to get your lights on this.
> 
> After rebuilding our data server, plenty of access rights have been
> changed and various folders have been ‘secured’ by restricting access
> to few users and groups. The whole ccp4 suite has also been subjected
> to this new policy; no writing in the folders and in sensitive files
> can be done anymore by unknown users. Good to feel safe :D

This seems like a sensible policy, and most centralised installations of
software like CCP4 is best done in this way.

> Now, when running Refmac5, we came up with plenty of complains about
> library files not readable, or more specifically some library files
> that ‘failed to open’. After few juggling around, we understood what
> was wrong: all the involved library files needed to be ‘writable’ to
> be properly read.

The libraries should not need to be writable to be loadable.

> Here is therefore my disturbing piece: why would you need to be able
> to write in a file if you just want to be able to read / execute it? I
> don’t think that this is a bug, but rather a feature, and would like
> to understand the logic behind it.

I doubt very much that this is a feature of CCP4. Unfortunately, you
have not given nearly enough information for anyone to make concrete
suggestions. Having said that, I would speculate that the problem lies
on one or both of two areas:

(i) Some sort of system or kernel-level hardening. Assuming that you
are using Linux (and if so, which distribution/version?) you may find
that something like Apparmor or SELinux is enabled and is restricting
your access. You can check for SELinux with the command "getenforce"
(/usr/sbin/getenforce on RedHat/CentOS). If it returns "enforcing", try
'tail -f /var/log/audit/audit.log' in one window while you try to run
refmac in another window (with the libraries read-only), and see if any
audit violations appear. There are tools within the SELinux suite that
can convert violations reported in audit.log into SELinux commands
and/or configurations to permit the access that you need.
Alternatively, you could disable SELinux if the security policy of your
institution allows it.

(ii) You mentioned a "data server". Are you seeing this problem on the
server, on client machines, or both? If client machines are involved,
the configuration of the technology that you are using to serve the
CCP4 installation may also be responsible. [What is this technology?
NFS? (and if so, version 3 or version 4?) A clustering filesystem? (and
if so, which one?) Samba? Something else?] 

(i) and (ii) can interact, for example the SELinux configuration can
mean that local and NFS file accesses have different characteristics,
even though the basic Unix permissions look the same from both points of
view.

Assuming once again that you are using Linux, the utility "strace" can
also be very useful for finding the exact errors returned when files
fail to opened. Be warned, there will be lots of "-1 ENOENT (No such
file or directory)" errors as shared libraries are searched for and not
found in all sorts of different directories. The important diagnostics
are the ones associated with attempts to open shared libraries that do
exist.

> Please note that I did not check how other programs responded, nor
> other versions of the suite (I am on the latest CCP4 release). I
> haven’t deeply screened the bb either for a potential previous notice
> on this.

If I were you, I would take this whole question to a system
administration forum or mailing list, unless you have really compelling
evidence to show that this is specifically a CCP4 problem.

I hope that this is of some use,
Peter.

> 
> Cheers, Leo
> 
> -
> Leonard Chavas
> -
> Mailing address:
> Center for Free-Electron Laser Science (CFEL)
> Deutsches Elektronen-SYnchrotron (DESY)
> Notkestrasse 85. Bldg 99
> 22607 Hamburg, Germany
> Room 03.051
> Phone : +49 (0)40 8998 6384
> Mobile: +49 (0)40 8998 96384
> -
> E-mail (DESY) : [log in to unmask]
> E-mail (CFEL) : [log in to unmask]
> -

-- 
Peter Keller                                     Tel.: +44 (0)1223 353033
Global Phasing Ltd.,                             Fax.: +44 (0)1223 366889
Sheraton House,
Castle Park,
Cambridge CB3 0AX
United Kingdom

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager