Login or Register to Ask a Question and Join Our Community


UNIX and Linux RSS News

Day 11 in the SCO v. Novell Trial, Monday, March 22, 2010, Tibbitts, LaSala - as text

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Day 11 in the SCO v. Novell Trial, Monday, March 22, 2010, Tibbitts, LaSala - as text
# 1  
Old 10-26-2010
Day 11 in the SCO v. Novell Trial, Monday, March 22, 2010, Tibbitts, LaSala - as text
This is the transcript of day 11 of the SCO v. Novell trial, as text, the second Utah trial that began on Monday, March 8, 2010 and ran for 15 days, Monday through Friday, for three weeks, with the Hon. Ted Stewart presiding. This day, then, is Monday, March 22, the beginning of the final week of the trial, and the witnesses that day were SCO's general counsel, Ryan Tibbitts, SCO's final witness, and then Novell begins to put on its case, beginning with its first witness, Joseph A. LaSala. Here is Groklaw's eyewitness report from the trial for that day.

The most important piece of all the Tibbitts testimony is when he testified that SCO needs the UNIX and UnixWare copyrights not only for the products business but for SCOsource. May I point out that this directly contradicts what SCO's CEO Darl McBride told the world in June 2003, when he said SCO didn't need the copyrights to go after Linux users? This is something I don't see Novell mentioning, at least in today's materials, but it's a significant piece. Let me show you the details, please. In case you were wondering why the court and the jury didn't credit SCO's witnesses, maybe it's because they contradicted each other.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT SUSE

group.conf

GROUP.CONF(5)							 Linux-PAM Manual						     GROUP.CONF(5)

NAME

       group.conf - configuration file for the pam_group module

DESCRIPTION

       The pam_group PAM module does not authenticate the user, but instead it grants group memberships (in the credential setting phase of the
       authentication module) to the user. Such memberships are based on the service they are applying for.

       For this module to function correctly there must be a correctly formatted /etc/security/group.conf file present. White spaces are ignored
       and lines maybe extended with '' (escaped newlines). Text following a '#' is ignored to the end of the line.

       The syntax of the lines is as follows:

       services;ttys;users;times;groups

       The first field, the services field, is a logic list of PAM service names that the rule applies to.

       The second field, the tty field, is a logic list of terminal names that this rule applies to.

       The third field, the users field, is a logic list of users or a netgroup of users to whom this rule applies.

       For these items the simple wildcard '*' may be used only once. With netgroups no wildcards or logic operators are allowed.

       The times field is used to indicate "when" these groups are to be given to the user. The format here is a logic list of day/time-range
       entries. The days are specified by a sequence of two character entries, MoTuSa for example is Monday Tuesday and Saturday. Note that
       repeated days are unset MoMo = no day, and MoWk = all weekdays bar Monday. The two character combinations accepted are Mo Tu We Th Fr Sa Su
       Wk Wd Al, the last two being week-end days and all 7 days of the week respectively. As a final example, AlFr means all days except Friday.

       Each day/time-range can be prefixed with a '!' to indicate "anything but". The time-range part is two 24-hour times HHMM, separated by a
       hyphen, indicating the start and finish time (if the finish time is smaller than the start time it is deemed to apply on the following
       day).

       The groups field is a comma or space separated list of groups that the user inherits membership of. These groups are added if the previous
       fields are satisfied by the user's request.

       For a rule to be active, ALL of service+ttys+users must be satisfied by the applying process.

EXAMPLES

       These are some example lines which might be specified in /etc/security/group.conf.

       Running 'xsh' on tty* (any ttyXXX device), the user 'us' is given access to the floppy (through membership of the floppy group)

	   xsh;tty*&!ttyp*;us;Al0000-2400;floppy

       Running 'xsh' on tty* (any ttyXXX device), the user 'sword' is given access to games (through membership of the floppy group) after work
       hours.

	   xsh; tty* ;sword;!Wk0900-1800;games, sound
	   xsh; tty* ;*;Al0900-1800;floppy

SEE ALSO

       pam_group(8), pam.d(5), pam(8)

AUTHOR

       pam_group was written by Andrew G. Morgan <morgan@kernel.org>.

Linux-PAM Manual						    04/01/2010							     GROUP.CONF(5)