date:19990818

Re: Need some advice regarding portable user IDs

1999-08-18 Thread Marc Ramirez


On Tue, 17 Aug 1999, Wilfredo Sanchez wrote:

   A group of us at Apple are trying to figure out how to handle  
 situations where a filesystem with "foreign" user ID's are present.   
 The basic problem is that the user experience using Unix semantics  
 are not really pleasant.  I think some examples would help:

I was thinking about this the other day, while mousting a series of floppy
disks, and it seems to me that what you're looking for, at least for
removable media, is a sort of single-user UFS that says "Joe Schmoe owns
this file system." Assuming that neither you nor Joe have accounts on each
other's machines:

0) Non-root users should be able to mount disks.  This really goes without
saying for desktop systems.

1) You mount_suufs his disk with some sort of "foreign-user" option, and
the system chooses an unused, per device UID and GID, and all the
directories are mapped to that ownership.

2) You copy the files to a world wrx directory, and they all automagically
become foreign ownership.

3) Joe goes to his computer and mounts his disk, and voila, he owns
everything (it's his filesystem after all).

This handles the simple case of just shuffling files around.  If you
wanted more elaborate collaborations, you'd really have to give each other
accounts.  You could monkey around with keeping passwd files and such on
the medium and umapping, but you couldn't copy files from the Zip to the
local FS without future-user-clash.

This also affords Joe more than your normal level of security, assuming he
trusts root on all the systems involved.

Marc.

--
Marc Ramirez - OwnerGreat Big Throbbing Brains
[EMAIL PROTECTED]  http://www.gbtb.com
Our brains throb, so yours won't have to!



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: cvs commit: src/bin/test test.c

1999-08-18 Thread Sheldon Hearn



[Hi-jacked out of cvs-committers  cvs-all]

On Tue, 17 Aug 1999 17:18:53 MST, Brian Feldman wrote:

 green   1999/08/17 17:18:53 PDT
 
   Modified files:
 bin/test test.c 
   Log:
   The new test(1) did not use access() correctly. I don't know why, since
   supposedly it's ksh-derived, and it's not broken in pdksh. I've added
   a test for test running as root: if testing for -x, the file must be
   mode  0111 to get "success", rather than just existant.
   
   Reviewed by:chris

What were you actually trying to fix, here?  I didn't see any discussion
of this on hackers, current or bugs, nor in response to my initial
commit message.

Ciao,
Sheldon.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Need some advice regarding portable user IDs

1999-08-18 Thread Ignatios Souvatzis


On Wed, Aug 18, 1999 at 05:00:48AM -0400, Marc Ramirez wrote:
 
 I was thinking about this the other day, while mousting a series of floppy
 disks, and it seems to me that what you're looking for, at least for
 removable media, is a sort of single-user UFS that says "Joe Schmoe owns
 this file system."

our(*) msdos and ados filesystems (at least) do (sort of) this.

Regards,
-is

*) where we = NetBSD


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Need some advice regarding portable user IDs

1999-08-18 Thread Alban Hertroys


On 18 Aug, Marc Ramirez wrote:

 Oh!  I was under the impression that it just didn't work, even with
 correct perms, but I use FreeBSD.  Lemme try it... Can't mount, even
 with 0666 on /dev/fd0.  Maybe I'm being stupid.  Wouldn't be the first
 time!
 
 Marc.

No miracle, the mount command has uid 0 hardcoded in the source where
you are checked if you are allowed to use the mount command. 

I've been thinking of a neat way to re-organize that code myself for
some time now, and thought I had come up with a solution (It's the
reason I subscribed to this list in the first place).

With the current discussion, I figure it has some major shortcomings. It
adds some things too, though, like the permissions to audio devices,
etc.

Anyway, I wrote a "paper" about it that I can post here if anybody is
interested. In that case, which format s liked best: plain text, TeX or
postscript? I assume the first.

-- 
Alban Hertroys.
http://wit401310.student.utwente.nl
==
If there is a here-after,
then there are much more people dead than alive.
Even that much more that the number of living people
is insignificant in comparison to the dead ones.
Thus it is safe to say that we don't exist.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: lpd security check for changed-file vs NFS

1999-08-18 Thread David Scheidt


On Tue, 17 Aug 1999, Garance A Drosihn wrote:

 At 6:37 PM -0700 8/17/99, Matthew Dillon wrote:
 If you removed the stat test, I would simply get rid of the -s
 option entirely - require that all files be queued to the print
 spool.
 
 The administration would kill me.  I would prefer to avoid that.
 
 (note that the check isn't completely removed, it's "only" nullified
 for NFS-mounted files.  We use AFS for most things here, so the vast

Couldn't you turn it off only for NFS mounted files?  

David scheidt


 
 Any advice on how to kick AIX so the st_dev+st_ino check will work
 right is also welcome.  It baffles me why AIX does things the way it
 does.  It kinda looks like the values it uses are pointers to some

The joke about AIX is that it was created by aliens who were given the 
UNIX documentation, but no example system.  I have seen very little that
suggests this to be untrue.  



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

[Fwd: First FreeMWare release!]

1999-08-18 Thread Darren WIebe


Hello:

I thought that some of you might be interested in this.  If this message
should not have been posted to this list please let me know.

Darren Wiebe
[EMAIL PROTECTED]


Hey folks,

It's been awhile.  Sorry, I've been busy working on other
fronts, but I did have time to put together a first go
at the virtualization framework we need for FreeMWare.

  ftp://ftp.freemware.org/pub/freemware/fmw-990817b.tar.gz

Which if you're having problems, is really just:

  ftp://bochs.com/pub/freemware/fmw-990817b.tar.gz

Attached is the "fmw-990817b.README" that goes along with it.

-Kevin

This is the beginnings to the virtualization framework that we
need for FreeMWare.  I have compiled it and run it on:

  Linux 2.0.36   (came with Red Hat 5.2)
  Linux 2.2.5-15 (came with Red Hat 6.0)

I've made an attempt to keep things modularized in
respect to the host OS.  Anything OS specific should
be put in "kernel/host-xyz.c" or "include/host-xyz.h".

This code is extremely experimental, and will likely
result in a system crash, and who knows what other
ill effects.  Don't run it on a system with any
important data on it, and make liberal user of
the sync command!  Expect to have to use the power
button.

We have to clean up the ioctl interface, using
macros instead of passing raw numbers I pulled out
of a hat, etc, etc.  This was my first Linux kernel
driver, so don't assume I did anything correctly. :^)

-Kevin



Directions for install etc.
---

Go into the user directory and type make.

  user cd user
  user make

Go into the kernel directory and type make.

  user cd ../kernel
  user make

Make the device node for freemware, as root user:

  root mknod /dev/freemware0 c 63 0

Fire up the kernel module:

  root insmod fmw.o

As a regular user, fire up the user program:

  user cd ../kernel
  user ./user # defaults to 1 iteration
 -or
  user ./user 10  # any number of iterations here

Whenever you recompile the kernel stuff, or want to
get rid of the kernel module, remove the old
kernel module first.  As root:

  root rmmod fmw


Each time the host switches to the monitor/guest
environment and runs that context.  Normally, execution
will continue in that context until a hardware interrupt
occurs or other exception.  The monitor interrupt handler
switches back to the host context to handle the interrupt.
The monitor/guest context will not resume execution until
the next ioctl() call from the user program.

NOTE:
  By default, I have a macro called TEST_MODE set to 1,
  in kernel/monitor.c.  In this mode, rather than waiting until
  an interrupt hits, control will be passed immediately back
  to the the host.  This is to test that the switching back/forth
  between host/monitor+guest works, without interrupts.

  I have not yet got interrupts redirection working properly.
  If you set TEST_MODE to 0 and recompile, an interrupt seems to
  cause everything to switch back to the host context, but
  then the system hangs after a short period of time,
  or causes a kernel oops.  I have not tracked this down
  yet.  It does register in /proc/freemware, that a redirection
  of an IRQ0 occurred.  Something is getting screwed up with
  interrupts in the kernel perhaps, after the software interrupt
  call to invoke the host kernel interrupt handler for the
  hardware interrupt we received while in guest context.

  Any ideas on what the problem is?

Re: Need some advice regarding portable user IDs

1999-08-18 Thread Michael C. Richardson

"Wilfredo" == Wilfredo Sanchez [EMAIL PROTECTED] writes:
Wilfredo I think the desired behaviour would be that since this is
Wilfredo effectively now Joe's zip disk, he should be able to do as he
Wilfredo pleases. One proposal might be to give the console user the
Wilfredo equivalent of root's priveledges on any removeable media he inserts

Right now, with MSDOS floppies, with no userids, the user owning the
mount point gets his userid applied to the entire disk. This allows me to
mount my floppies, etc. on mount points that I own, and I own all
the resulting files. I think you want the same thing as an option for
UFS mounts.

Wilfredo Presumably the console user is the one fiddling with the external
Wilfredo media.

I don't think this is entirely true, and isn't a useful or enforceable
restriction.

Wilfredo As another example, a similar situation often comes up on the net
Wilfredo with tar files containing UIDs and GIDs other than zero.

Only with SYSV chown semantics that allow non-root to make files not
owned by them.

Wilfredo So perhaps there needs to be a way to mark a drive as local
Wilfredo (perhaps with a host ID of some sort?) and noticing when a volume is
Wilfredo "foreign" that you need to do something special. Certainly you might
Wilfredo want to ignore setuid bits, for starters. This could simply be
Wilfredo something like fstab, which lists the local drives, and everything
Wilfredo else isn't considered local.

This is solved by having the "nouid" or somesuch thing add to /etc/fstab
by the admin who knows which ones should be trusted. Linux provides "user"
to get the behaviour that we get for free.

Wilfredo Has anyone dived into this area already and have some experience
Wilfredo with it? It's confusing me pretty good.

See what ATT did with RFS. This may be a negative example (i.e. don't do
this).

:!mcr!:| Cow#1: Are you worried about getting Mad Cow Disease?
Michael Richardson | Cow#2: No. I'm a duck.
Home: A
HREF="http://www.sandelman.ottawa.on.ca/People/Michael_Richardson/Bio.html"[EMAIL PROTECTED]/A.
PGP key available.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

async v. sync v. default mode on ufs

1999-08-18 Thread Larry Lile



It was pointed out to me by a co-worker that FreeBSD has actually
three modes of operation for mounting ufs filesystems.  Could someone
please explain to me, and him, the differences between the three.

Also does anyone knows how these compare to sync and async on Linux?

Just a btw, you seem to be able to set sync and async on a filesystem
at the same time.  What gives?

dlane# mount -u -o sync,async,noatime /var dlane-printer# mount
/dev/wd0s1a on / (local, noatime, synchronous, writes: sync 405 async 23)
/dev/wd0s1e on /usr (local, noatime, synchronous, writes: sync 118365 
async 83882) 
/dev/wd0s1f on /var (asynchronous, local, noatime, synchronous, writes: 
sync 93 async 216) procfs on /proc (local)
dlane#

/var looks questionable...

I would never try that on purpose, but it just kinda happened, and when I 
looked at it I though "wow that's broken"!

Larry Lile
[EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Onstream?

1999-08-18 Thread Matthew Jacob




 In message [EMAIL PROTECTED] Christopher Masto writes:
 : Do they still not allow you to release the specs?  How is the code
 : going to become part of FreeBSD if they won't allow its release?
 
 I didn't sign an NDA to get my copy of the spec or the hardware...

Neither did I. But I was requested by Jim Jonez of Onstream to not release
the specs.

 
 I also don't have time to devote to the onstream IDE project.  I'm
 looking for someone with the kernel skills and track record to take
 over for me.

I thought Soren was doing it...




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Need some advice regarding portable user IDs

1999-08-18 Thread Marc Ramirez


On Wed, 18 Aug 1999, David Malone wrote:

 On Wed, Aug 18, 1999 at 07:39:11AM -0400, Marc Ramirez wrote:
  Oh!  I was under the impression that it just didn't work, even with
  correct perms, but I use FreeBSD.  Lemme try it... Can't mount, even
  with 0666 on /dev/fd0.  Maybe I'm being stupid.  Wouldn't be the first
  time!
 
 You have to turn it on with a sysctl: "sysctl -w vfs.usermount=1" I
 think.

So it is.

Thanks.

Marc.

--
Marc Ramirez - OwnerGreat Big Throbbing Brains
[EMAIL PROTECTED]  http://www.gbtb.com
Our brains throb, so yours won't have to!



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: VMWare: porting kernel modules to FreeBSD

1999-08-18 Thread Josef Karthauser


On Wed, Aug 18, 1999 at 09:16:29AM -0500, Chris Dillon wrote:
 On Wed, 18 Aug 1999, Mark Huizer wrote:
 
  Hi there,
  
  I had a look recently at the code for one of the kernel modules that VMWare
  requires (driver-only.tar), and it looks like something that should be
  portable to FreeBSD, although there is some messy stuff in it (assembly
  that seems to be using Linux specific stuff, brrr..) But anyway: it
  looks feasable.
  
  Is anyone already working on this, or are some people interested in
  helping with this?
  
  As far as I can see, the linux emulation is good enough to run the
  vmware program, "all" you need to do is implement /dev/vmmon and
  /dev/vmnet, given the fact that the code is written really unportable,
  so there is some rewriting to be done. Then with the KLD's
  vmmon,vmnet and linux you should be able to run vmware.
 
 WooHoo!  Well, I can't celebrate quite yet, but I'll definately be
 buying a copy of VMWare if anyone gets this to work (WAY above my
 head, so no help from me, sorry).  More than likely, many people other
 than myself would also buy a copy of VMWare for Linux just to run
 under FreeBSD, so maybe you can convince VMWare, Inc. to give you or
 whoever else decides to tackle this some monetary compensation?  It
 would also help to bring us a step closer to a native FreeBSD version
 of VMWare, since some (most?) of the work would already be done for
 them (the porting of vmmon and vmnet).

We will _definitely_ buy VMWare if we can run it on a FreeBSD host
system - I believe that I've told them so in the past.

Joe
-- 
Josef KarthauserFreeBSD: How many times have you booted today?
Technical Manager   Viagra for your server (http://www.uk.freebsd.org)
Pavilion Internet plc.  [[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: RE: Need some advice regarding portable user IDs

1999-08-18 Thread Wilfredo Sanchez


|   when new media is available and it will try to mount it.  The  
present
|   behaviour in Mac OS X Server is that everything mounted this  
way is
|   trusted, though the Finder should be requesting nosetuid; I should   
|   check that.  It's also possible that the kernel will number  
drives in
|   a different order (eg. /dev/sd0a this boot might be /dev/sd1a next   
|   boot), particularly if you are shuffling drives around. (Remember   
|   that hot-swap complicates this.)  So a string like "/dev/sd0a" in   
|   fstab is fragile, and it works out better if we keep that  
information
|   on the mounted media rather than on the root volume.
|
| What happens with conflicting names?

  Append "_1", "_2", etc.

-Fred


--
   Wilfredo Sanchez, [EMAIL PROTECTED]
Apple Computer, Inc., Core Operating Systems / BSD
  Technical Lead, Darwin Project
   1 Infinite Loop, 302-4K, Cupertino, CA 95014



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: OpenLDAP tests?

1999-08-18 Thread Jaye Mathisen



Found it.

This let the tests run fine for me.

===
RCS file: /repo/OpenLDAP/pkg/ldap/servers/slapd/daemon.c,v
retrieving revision 1.14.2.7.2.8
retrieving revision 1.14.2.7.2.9
diff -u -r1.14.2.7.2.8 -r1.14.2.7.2.9
--- servers/slapd/daemon.c  1999/03/02 18:30:05 1.14.2.7.2.8
+++ servers/slapd/daemon.c  1999/07/20 05:10:35 1.14.2.7.2.9
@@ -390,7 +390,6 @@
 void
 slap_set_shutdown( int sig )
 {
-   Debug( LDAP_DEBUG_ANY, "slapd got shutdown signal %d\n", sig, 0, 0
);
slapd_shutdown = 1;
ldap_pvt_thread_kill( listener_tid, LDAP_SIGUSR1 );
 
@@ -401,8 +400,6 @@
 void
 slap_do_nothing( int sig )
 {
-   Debug( LDAP_DEBUG_TRACE, "slapd got do_nothing signal %d\n", sig,
0, 0 );
-
/* reinstall self */
(void) SIGNAL( sig, slap_do_nothing );
 }







On Wed, 18 Aug 1999, Steven Ames wrote:

 Thanks! I'll check the site (but would appreciate your sending it to me
 also).
 
 -Steve
 
 On Tue, 17 Aug 1999, Jaye Mathisen wrote:
 
  
  There is a patch that fixes this, I found it, and submitted a bug report
  on their web page.
  
  I don't have it handy, but if you go to www.openldap.org and to their
  faq-o-matic, and it should be in there.
  
  I'll see if I can find it and send it to you in the mean time.
  
  On Tue, 17 Aug 1999, Steven Ames wrote:
  
   
   I've got a project at work where using LDAP would make my life
   much simpler. So... on my home PC (running FBSD 4.0-CURRENT 8.2.99)
   I installed openldap from the ports collection (V1.2.3...ports cvsuped
   about an hour ago from cvsup5.freebsd.org).
   
   I cd into the test area /usr/ports/work/ldap/tests and type 'make'.
   Looking good... until... on test0003-search it stops. It just holds.
   My CPU is up to 99% and its chewed up 18 minutes of CPU before I hit
   Ctrl-C and stopped it. I did a 'make clean' moved scripts/test0003-seach
   to scripts/test0009-search (so it would run last) and tried again.
   Same results on test0004-modify. *sigh*
   
   Do the tests just not run? I didn't dare to just go ahead and use it
   as I'm not familiar enough with LDAP to judge if a failure is my fault
   or a system problem. I'd feel a lot safer if the tests all passed so that
   if anything goes wrong from that point I can call it user error.
   
   Anyone?
   
   -Steve
   
   
   To Unsubscribe: send mail to [EMAIL PROTECTED]
   with "unsubscribe freebsd-hackers" in the body of the message
   
  
 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

1 2 >

1 - 100 of 141 matches

Mail list logo