Re: Wine on OLPC

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ove Kaaven wrote: | Benjamin M. Schwartz skrev: |> Bug #2 suggests that it may be possible to solve this problem using |> dynamically generated symlinks. I will try that. | | The big reason .wine has to be owned by the right user is that the | win

Re: Wine on OLPC

Benjamin M. Schwartz skrev: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Ove Kaaven wrote: > | Benjamin M. Schwartz skrev: > |> I'm particularly surprised because I cannot imagine any reasonable > |> scenario in which allowing non-root users to run in .wine/ directories > |> that they do

Re: Wine on OLPC

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ove Kaaven wrote: | Benjamin M. Schwartz skrev: |> I'm particularly surprised because I cannot imagine any reasonable |> scenario in which allowing non-root users to run in .wine/ directories |> that they do not own is a security risk. There is no pri

Re: Wine on OLPC

Benjamin M. Schwartz skrev: > I'm particularly surprised because I cannot imagine any reasonable > scenario in which allowing non-root users to run in .wine/ directories > that they do not own is a security risk. There is no privilege escalation > here; the non-root user is still required by the k

Re: Wine on OLPC

On Saturday April 12 2008 04:54:44 Benjamin M. Schwartz wrote: > I need the ability to run in profiles as a user who is not the "owner" of > the files on disk. > ... > I would prefer not to maintain a patched fork of Wine just to get this > trivial feature. That doesn't benefit anyone. I'm sure w

Re: Wine on OLPC

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 James Hawkins wrote: | On Fri, Apr 11, 2008 at 7:45 PM, Benjamin M. Schwartz |> Then how about a patch that specifically prevents users from running wine |> as root over a profile that is not owned by root? I am trying to run wine |> as a non-root u

Re: Wine on OLPC

On Fri, Apr 11, 2008 at 7:45 PM, Benjamin M. Schwartz <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > James Hawkins wrote: > | On Fri, Apr 11, 2008 at 6:11 PM, Benjamin M. Schwartz > | <[EMAIL PROTECTED]> wrote: > |> -BEGIN PGP SIGNED MESSAGE- > |> Ha

Re: Wine on OLPC

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 James Hawkins wrote: | On Fri, Apr 11, 2008 at 6:11 PM, Benjamin M. Schwartz | <[EMAIL PROTECTED]> wrote: |> -BEGIN PGP SIGNED MESSAGE- |> Hash: SHA1 |> |> James Hawkins wrote: |> | On Fri, Apr 11, 2008 at 5:59 PM, Benjamin M. Schwartz |> |

Re: Wine on OLPC

On Fri, Apr 11, 2008 at 6:11 PM, Benjamin M. Schwartz <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > James Hawkins wrote: > | On Fri, Apr 11, 2008 at 5:59 PM, Benjamin M. Schwartz > |> Would you consider patches to exchange the uid check for a rwx access > ch

Re: Wine on OLPC

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 James Hawkins wrote: | On Fri, Apr 11, 2008 at 5:59 PM, Benjamin M. Schwartz |> Would you consider patches to exchange the uid check for a rwx access check? | No, that check was added to keep users from running Wine as root. Then why not prevent user

Re: Wine on OLPC

On Fri, Apr 11, 2008 at 5:59 PM, Benjamin M. Schwartz <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Dear Wine developers, > I am attempting to package Wine for OLPC. My goal is to enable packaging > individual windows programs into OLPC "Activity bundles" wit

Wine on OLPC

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Wine developers, I am attempting to package Wine for OLPC. My goal is to enable packaging individual windows programs into OLPC "Activity bundles" with wine. I have encountered a handful of problems along the way. One of them is bug #12507, for