Darren,
>>> After investigating IPS ( pkg(5)) and SVR4 packages, in order to work
>>> for both SVR4 and IPS, the best way should be that adding a default
>>> group in system for slocate ( 95 should be good for slocate).
>>>
>>>
About adding a default group issue, I noticed that in Postgres
Closed as approved.
--irene
On Wed, 2008-08-13 at 12:48 +0800, Irene Huang wrote:
> Hi, all
> I am resetting the timeout to be August 16th.
> The updated proposal is posted at
> http://sac.eng/Archives/CaseLog/arc/LSARC/2008/447/proposal-v4.txt
>
> Please review
> --Irene
> Jim Li wrote:
> > Jy
Jim Li wrote:
> Darren,
After investigating IPS ( pkg(5)) and SVR4 packages, in order to
work for both SVR4 and IPS, the best way should be that adding a
default group in system for slocate ( 95 should be good for slocate).
> About adding a default group issue, I n
Hi, all
I am resetting the timeout to be August 16th.
The updated proposal is posted at
http://sac.eng/Archives/CaseLog/arc/LSARC/2008/447/proposal-v4.txt
Please review
--Irene
Jim Li wrote:
> Jyri Virkki wrote:
>> Jim Li wrote:
>>
>>> Because there are no preinstall or postinstall scripts in IP
Jyri Virkki wrote:
> Jim Li wrote:
>
>> Because there are no preinstall or postinstall scripts in IPS, so there
>> is no way to create a group when adding a package and delete this group
>> when removing the package.
>>
>
> IPS has a built-in group (and user) action, see pkg(5)
>
>
> Darr
Hi, Jim
Please make a decision on how to handle the property ASAP, and then I
think we can put an end to this case:)
Thanks
--Irene
On Mon, 2008-08-04 at 10:35 +0100, Darren J Moffat wrote:
> Jim Li wrote:
> > Darren J Moffat ??:
> >> Jim Li wrote:
> >>> Darren J Moffat wrote:
> >> So
It looks to me that there's no blocking issues for this case. If there's
no objections within 24 hours, I'd like to close the case as approved.
--Irene
On Thu, 2008-07-31 at 14:38 +0100, Darren J Moffat wrote:
> Jim Li wrote:
> > Darren J Moffat wrote:
> So what is the ownership and permissi
Irene Huang wrote:
> It looks to me that there's no blocking issues for this case. If there's
> no objections within 24 hours, I'd like to close the case as approved.
There is still discussion going on and the spec in place does not
reflect the status of the discussion.
Given all the changes I
Jim Li wrote:
> Darren J Moffat ??:
>> Jim Li wrote:
>>> Darren J Moffat wrote:
>> So what is the ownership and permissions of
>> /var/lib/slocate/slocate.db
>>
> The ownership is root, group is other and permissions is 744
The above check is completely useless given that
Jim Li wrote:
>
> Because there are no preinstall or postinstall scripts in IPS, so there
> is no way to create a group when adding a package and delete this group
> when removing the package.
IPS has a built-in group (and user) action, see pkg(5)
Darren J Moffat wrote:
>
> Either way this cas
Darren J Moffat ??:
> Jim Li wrote:
>> Darren J Moffat wrote:
> So what is the ownership and permissions of
> /var/lib/slocate/slocate.db
>
The ownership is root, group is other and permissions is 744
>>>
>>> The above check is completely useless given that that database is
>>> p
Darren J Moffat wrote:
>>> So what is the ownership and permissions of /var/lib/slocate/slocate.db
>>>
>> The ownership is root, group is other and permissions is 744
>
> The above check is completely useless given that that database is
> publically readable. Also it should't be rwx for owner it
Darren J Moffat wrote:
>>> So what is the ownership and permissions of /var/lib/slocate/slocate.db
>>>
>> The ownership is root, group is other and permissions is 744
>
> The above check is completely useless given that that database is
> publically readable. Also it should't be rwx for owner it
Darren J Moffat wrote:
> Jim Li wrote:
>> Q4. What reserved GID is being used for slocate? and other questions
>> about this.
>>
>> Group "slocate" is not necessary by going through the source code
>> deeply.
>> So just remove all "slocate" relative stuff.
>
> So slocate is no longer SUID or SGID
The updated proposal is posted at
Internally
http://sac.eng/Archives/CaseLog/arc/LSARC/2008/447/proposal-v3.txt
Diff file at
http://sac.eng/Archives/CaseLog/arc/LSARC/2008/447/proposal-v2-v3.diff
Externally
???http://www.opensolaris.org/os/community/arc/caselog/2008/447
I am reseting the timeou
I've updated the ARC material and summarized the question and answers as
following:
Q1. Should add a cron job entry to update index automatically.
Added it to run updatedb at 3:00 am everyday.
Q2. Does user need special privileges to execute updatedb?
It depends. Slocate allow user to create i
Jim Li wrote:
> Darren J Moffat wrote:
So what is the ownership and permissions of /var/lib/slocate/slocate.db
>>> The ownership is root, group is other and permissions is 744
>>
>> The above check is completely useless given that that database is
>> publically readable. Also it should'
Jim Li wrote:
>> So slocate is no longer SUID or SGID ?
> Yes, it not.
>> but if slocate isn't SUID or SGID to root or the owner of the database
>> file that implies that the database file is world readable so this
>> check is a bit pointless.
>>
> "check permission" here doesn't mean that it c
Jim Li wrote:
> Q4. What reserved GID is being used for slocate? and other questions
> about this.
>
> Group "slocate" is not necessary by going through the source code deeply.
> So just remove all "slocate" relative stuff.
So slocate is no longer SUID or SGID ?
> Q7. Does Slocate work with ACL
Darren J Moffat wrote:
> James Carlson wrote:
>
>> Jim Li writes:
>>
>>> 2> Slocate will check file permissions and ownership before
>>> displaying matched files so that files they don't have access to
>>> will be filtered out. Tracker will display all matched files no
>>> matter what the permi
Brian:
> The description for this project says:
>
> >This locate can index all files on your system, but only files
> >and directories which the invoking user has access to will be
> >displayed.
>
> This doesn't really explain to me what exactly this project does very
>
James Carlson wrote:
> I'm on the fence on this one. The way it "fails safe" is that you
> don't install it if you don't want it and/or you do care about ACLs.
I don't think that is fair. It is the sysadmin that does the install
but the end user's privacy that is leaked to other end users if th
James Carlson wrote:
> Jim Li writes:
>> 2> Slocate will check file permissions and ownership before displaying
>> matched files so that files they don't have access to will be filtered
>> out. Tracker will display all matched files no matter what the
>> permissions and ownershiop are.
>
> I as
Darren J Moffat writes:
> James Carlson wrote:
> > I'm on the fence on this one. The way it "fails safe" is that you
> > don't install it if you don't want it and/or you do care about ACLs.
>
> I don't think that is fair.
I do. The system doesn't install with any ACLs on anything. The
system i
Darren J Moffat writes:
> James Carlson wrote:
> > Jim Li writes:
> >> 2> Slocate will check file permissions and ownership before displaying
> >> matched files so that files they don't have access to will be filtered
> >> out. Tracker will display all matched files no matter what the
> >> permi
Jim Li writes:
> 2> Slocate will check file permissions and ownership before displaying
> matched files so that files they don't have access to will be filtered
> out. Tracker will display all matched files no matter what the
> permissions and ownershiop are.
I assume that's an attempt at secur
Irene:
The description for this project says:
>This locate can index all files on your system, but only files
>and directories which the invoking user has access to will be
>displayed.
This doesn't really explain to me what exactly this project does very
well. I don'
Hi, all
The new proposal files is uploaded to
Internally
http://sac.eng/Archives/CaseLog/arc/LSARC/2008/447/proposal-v2.txt
Diff: http://sac.eng/Archives/CaseLog/arc/LSARC/2008/447/proposal.diff
Externally
http://www.opensolaris.org/os/community/arc/caselog/2008/447
if there's any further iss
>Comment 1: slocate.db is the index file which is be created by
>package install post, will be updated when using updatedb.
Why is this postinstall step needed ? Why can't an empty slocate.db
file with the correct permissions be created ?
Given 2 below it seems that slocate.db c
Hi James,
I've updated the one page and summarized the questions and answers.
Q1. Missed at least /etc/updatedb.conf and /var/lib/slocate/slocate.db
added the missed interfaces. see the updated one page.
Q2. Missed a contract. What is being used from /usr/lib/libast.so.1 and why?
The contract
Dan Mick writes:
> James Carlson wrote:
> > Jim Li writes:
> >> Q4. Suggested that each locate implementation has an update service in
> >> smf(5)
> >> and a cron job.
> >>
> >> Currently we are focusing on enriching the open source projects which can
> >> be used on Solaris. Don't have enough res
James Carlson wrote:
> Dan Mick writes:
>> James Carlson wrote:
>>> Jim Li writes:
Q4. Suggested that each locate implementation has an update service in
smf(5)
and a cron job.
Currently we are focusing on enriching the open source projects which can
be used on Solari
James Carlson wrote:
> Jim Li writes:
>> Q4. Suggested that each locate implementation has an update service in
>> smf(5)
>> and a cron job.
>>
>> Currently we are focusing on enriching the open source projects which can
>> be used on Solaris. Don't have enough resources to improve the projects or
On Mon, Jul 21, 2008 at 08:13:45AM -0400, James Carlson wrote:
> > Q5. Does user need special privileges to execute updatedb?
> >
> > needs Primary Administrator profile.
>
> In that case, I don't think it belongs in /usr/bin.
Presumably you only need privilege to index directories you don't ha
Jim Li writes:
> Q4. Suggested that each locate implementation has an update service in
> smf(5)
> and a cron job.
>
> Currently we are focusing on enriching the open source projects which can
> be used on Solaris. Don't have enough resources to improve the projects or
> provide extension functio
right, they are not final manpages to be shipped on solaris. These
manpages are linux manpage for everyone's reference.
Jim is working on the Solaris manpages, which will surely include the
attribute secton.
--Irene
Matt Keenan wrote:
> Neither of the man pages contain an Attributes section whic
Hi, Joerg
If you are using the external link below, then it's possible that the
materials hasn't been sync'ed to www.opensolaris.org yet :(.
It take some time to sync.
--Irene
Joerg Schilling wrote:
> Irene Huang wrote:
>
>
>> Hi, all
>>
>> The manpages for slocate and updatedb is available
Neither of the man pages contain an Attributes section which should detail
the interface stability. They should be modified to include this
information.
Matt
Irene Huang wrote:
> Hi, Joerg
>
> If you are using the external link below, then it's possible that the
> materials hasn't been sync'ed
Irene Huang wrote:
> Hi, all
>
> The manpages for slocate and updatedb is available at
> Internally
> http://sac.eng/Archives/CaseLog/arc/LSARC/2008/447/manpages/
>
> Externally
> http://www.opensolaris.org/os/community/arc/caselog/2008/447
I cannot see any man page - sorry.
J?rg
--
EMail
Hi, all
The manpages for slocate and updatedb is available at
Internally
http://sac.eng/Archives/CaseLog/arc/LSARC/2008/447/manpages/
Externally
http://www.opensolaris.org/os/community/arc/caselog/2008/447
--Irene
On Wed, 2008-07-16 at 11:31 +0200, Joerg Schilling wrote:
> Stephen Hahn wrote
On Fri, Jul 18, 2008 at 8:21 AM, Joerg Schilling <
Joerg.Schilling at fokus.fraunhofer.de> wrote:
> Irene Huang wrote:
>
> > Hi, all
> >
> > The manpages for slocate and updatedb is available at
> > Internally
> > http://sac.eng/Archives/CaseLog/arc/LSARC/2008/447/manpages/
> >
> > Externally
> >
Stephen,
> * Shi-Ying Irene Huang [2008-07-15 09:24]:
>
>> 4.1. Details:
>>
>> This locate can index all files on your system, but only files
>> and directories which the invoking user has access to will be
>> displayed.
>>
>
> In the discussions I've been in,
Darren,
>>> /usr/lib/libast.so.1 private 2006/550
>>> (SONMAE libast.so.1)
>>
>> That comes from ON and I don't see a contract. Where's this software
>> integrating?
>
> And what is being used from this library and why ?
>
Fts_open, fts_close, fts_open and fts_set provide the
James,
Thanks a million for your question and comment. see my response
inline. If there is anything unclear or wrong, please feel free to let
me know
Jim
> Shi-Ying Irene Huang writes:
>
>> SUNWslocateUncommittedpackage name
>> /usr/bin/slocate
Stephen Hahn wrote:
> * Shi-Ying Irene Huang [2008-07-15 09:24]:
> > 4.1. Details:
> >
> > This locate can index all files on your system, but only files
> > and directories which the invoking user has access to will be
> > displayed.
>
> In the discussions I've be
Jim Li writes:
> > Shi-Ying Irene Huang writes:
> > I think you may have missed at least /etc/updatedb.conf and
> > /var/lib/slocate/slocate.db. There may be other interfaces associated
> > with this package; I'm not positive, as it's been a while since I used
> > it.
> >
> >
> /etc/updatedb.co
James Carlson wrote:
>> /usr/lib/libast.so.1 private 2006/550
>> (SONMAE libast.so.1)
>
> That comes from ON and I don't see a contract. Where's this software
> integrating?
And what is being used from this library and why ?
--
Darren J Moffat
* Shi-Ying Irene Huang [2008-07-15 09:24]:
> 4.1. Details:
>
> This locate can index all files on your system, but only files
> and directories which the invoking user has access to will be
> displayed.
In the discussions I've been in, it's been suggested that each
Shi-Ying Irene Huang writes:
> SUNWslocateUncommittedpackage name
> /usr/bin/slocate Volatile CLI
> /usr/bin/updatedb Volatile CLI
I think you may have missed at least /etc/updatedb.conf and
/var/lib
Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI
This information is Copyright 2008 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
slocate for OpenSolaris
1.2. Name of Document Author/Supplier:
Author: Jim Li
1.3 Date of This Document:
50 matches
Mail list logo