All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim McCullough <jim.mccullough@gmail.com>
To: ivg2@cornell.edu
Cc: Luke Kenneth Casson Leighton <lkcl@lkcl.net>,
	Casey Schaufler <casey@schaufler-ca.com>,
	selinux@tycho.nsa.gov
Subject: Re: Desktop apps interoperability
Date: Wed, 30 Mar 2005 13:09:57 -0500	[thread overview]
Message-ID: <ae023b60050330100976b46528@mail.gmail.com> (raw)
In-Reply-To: <1112204662.8592.42.camel@cobra.ivg2.net>

There as been multiple instances on other lists where an "admin" or
"developer" has been totally ignorant of any type of security
practices.  Cases of do as I will and roll with the punches.  This
occurs on all platforms of development.   Freedom of implementation
should also require some common sense.  I like the content folders
Ivan suggested.   That would save people like me who are attention
defficiet a more structured schema for their fresh systems ( and prob.
save me a couple of hours on my own each build i have to do for myself
).
  
-- 
Jim McCullough

On Wed, 30 Mar 2005 12:44:22 -0500, Ivan Gyurdiev <ivg2@cornell.edu> wrote:
> On Wed, 2005-03-30 at 18:26 +0100, Luke Kenneth Casson Leighton wrote:
> > On Wed, Mar 30, 2005 at 09:04:26AM -0800, Casey Schaufler wrote:
> >
> > > Yes, and I'm sure that you can do a configuration
> > > of most application defaults that will be good
> > > enough to demo. Application developers tend to
> > > have their own ideas regarding data storage and
> > > it is a bad idea for a system developer to
> > > interfere with said application developer's
> > > freedom to inovate.
> >
> >  ... application developer's freedom to impose insecurity,
> >  through ignorance on the part of the app-developer, upon
> >  the users?
> >
> >  no offense intended: freedom in an abstract concept [e.g. "the american
> >  way"] _always_ has limits - laws / rules / policy is defined to confine
> >  that freedom, for good or worse.
> 
> I don't understand what this has to do with the application developer.
> This is a discussion of desktop applications that manipulate content
> relevant to the user - not internal settings. The settings that go
> under /home are another issue - that would require changing the app,
> but they don't have to be changed all at the same time.
> 
> All those apps *ask* you where to store the content. You create a
> document of some sort, and you have a choice of where to put it.
> This has nothing to do with the app developer. It's just another
> restriction imposed on the user. Hopefully there's a way to get
> away with it, while staying user-friendly. That's why I'm suggesting
> content folders be introduced and integrated w/ GNOME's Places
> menu, for example. That seems like a small first step to improving
> things... no?
> 
> Ok, some apps like gift don't ask where to save the content,
> but that's the exception and not the rule.
> 
> --
> Ivan Gyurdiev <ivg2@cornell.edu>
> Cornell University
> 
> 
> --
> This message was distributed to subscribers of the selinux mailing list.
> If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
> the words "unsubscribe selinux" without quotes as the message.
>

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2005-03-30 18:11 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-30 17:04 Desktop apps interoperability Casey Schaufler
2005-03-30 17:15 ` Stephen Smalley
2005-03-30 17:26 ` Luke Kenneth Casson Leighton
2005-03-30 17:44   ` Ivan Gyurdiev
2005-03-30 18:09     ` Jim McCullough [this message]
2005-03-30 22:09       ` Luke Kenneth Casson Leighton
2005-03-30 22:00     ` Luke Kenneth Casson Leighton
2005-03-31  9:25       ` Ivan Gyurdiev
2005-03-31  9:48         ` Ivan Gyurdiev
  -- strict thread matches above, loose matches on Subject: below --
2005-04-03 23:39 Casey Schaufler
2005-04-02  3:50 Casey Schaufler
2005-03-31 16:51 Casey Schaufler
2005-03-31 18:16 ` Stephen Smalley
2005-03-31 16:05 Casey Schaufler
2005-03-31 16:08 ` Stephen Smalley
2005-03-31 21:13   ` Tom
2005-03-31 21:05     ` Stephen Smalley
2005-04-01  5:28       ` Rogelio Serrano
2005-04-01  7:54         ` Tom
2005-03-31 17:40 ` Ivan Gyurdiev
2005-03-30 17:58 Casey Schaufler
2005-03-31 10:04 ` Ivan Gyurdiev
2005-03-30 17:53 Casey Schaufler
2005-03-30 17:56 ` Stephen Smalley
2005-03-30 17:27 Casey Schaufler
2005-03-30 15:52 Casey Schaufler
2005-03-30 16:13 ` Ivan Gyurdiev
2005-03-30 21:50   ` Tom
2005-03-30 22:12     ` Luke Kenneth Casson Leighton
2005-03-31  8:37       ` Tom
2005-03-31 10:05         ` Luke Kenneth Casson Leighton
2005-03-31  8:42     ` Ivan Gyurdiev
2005-03-30 15:05 Casey Schaufler
2005-03-30 15:29 ` Ivan Gyurdiev
2005-03-28 16:51 Casey Schaufler
2005-03-28  4:57 Ivan Gyurdiev
2005-03-28  5:03 ` Ivan Gyurdiev
2005-03-28  5:27   ` Ivan Gyurdiev
2005-03-28 10:01     ` Luke Kenneth Casson Leighton
2005-03-28 10:17       ` Rogelio Serrano
2005-03-29 11:33         ` Dale Amon
2005-03-29 13:54           ` Stephen Smalley
2005-03-29 15:39             ` Colin Walters
2005-03-28 11:26     ` Tom
2005-03-28 12:15       ` Ivan Gyurdiev
2005-03-28 13:11         ` Tom
2005-03-28 13:46           ` Ivan Gyurdiev
2005-03-28 14:09             ` Tom
2005-03-28 15:05               ` Ivan Gyurdiev
2005-03-28 15:12                 ` Stephen Smalley
2005-03-28 15:47                   ` Tom
2005-03-28 16:04                     ` Stephen Smalley
2005-03-28 16:20                       ` Tom
2005-03-28 16:39                         ` Stephen Smalley
2005-03-30  5:01                           ` Ivan Gyurdiev
2005-03-28 15:41                 ` Tom
2005-03-28 10:04 ` Luke Kenneth Casson Leighton
2005-03-28 13:36   ` Stephen Smalley
2005-03-28 18:27     ` Luke Kenneth Casson Leighton
2005-03-28 18:23       ` Stephen Smalley
2005-03-28 19:54         ` Luke Kenneth Casson Leighton
2005-03-28 19:46           ` Stephen Smalley
2005-03-28 13:43 ` Stephen Smalley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ae023b60050330100976b46528@mail.gmail.com \
    --to=jim.mccullough@gmail.com \
    --cc=casey@schaufler-ca.com \
    --cc=ivg2@cornell.edu \
    --cc=lkcl@lkcl.net \
    --cc=selinux@tycho.nsa.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.