I've started a new thread because this discussion was going to get lost in the 200+ message thread-o-doom.
So so far we have the introduction of gnome-user-share, which uses an http process dynamically bound to a port running as the user to share stuff in a ~/Public file to the world w/out auth. It sounds like gnome-user-auth will go into core. The restrictions have been put forth:
* Functionality is provided by a package and removed by a package, w/out core deps.
* Functionality is controlled by a gconf entry which an admin can set to mandatory off (or just remove the package)
Some ideas that have floated for this package include:
* Functionality disabled until a file is placed in ~/Public prompting for a dialog box informing the user that the share is now active, with a link to more help in this.
* Gnome-panel icon to show state of sharing with a timeout value to stop the share (configurable)
* Integration with network-manager to enable/disable the share on specific networks
Thoughts?
Jesse Keating wrote:
I've started a new thread because this discussion was going to get lost in the 200+ message thread-o-doom.
So so far we have the introduction of gnome-user-share, which uses an http process dynamically bound to a port running as the user to share stuff in a ~/Public file to the world w/out auth. It sounds like gnome-user-auth will go into core. The restrictions have been put forth:
- Functionality is provided by a package and removed by a package, w/out
core deps.
- Functionality is controlled by a gconf entry which an admin can set to
mandatory off (or just remove the package)
Some ideas that have floated for this package include:
- Functionality disabled until a file is placed in ~/Public prompting
for a dialog box informing the user that the share is now active, with a link to more help in this.
- Gnome-panel icon to show state of sharing with a timeout value to stop
the share (configurable)
- Integration with network-manager to enable/disable the share on
specific networks
Thoughts?
What protocol will this be using? (http, ftp, tftp, etc)
On Sun, 2005-07-17 at 21:38 -0400, Arthur Pemberton wrote:
So so far we have the introduction of gnome-user-share, which uses an http process dynamically bound to a port running as the user to share stuff in a ~/Public file to the world w/out auth. It sounds like gnome-user-auth will go into core. The restrictions have been put forth:
[...]
What protocol will this be using? (http, ftp, tftp, etc)
As I stated above, it will be using http.
Jesse Keating wrote:
On Sun, 2005-07-17 at 21:38 -0400, Arthur Pemberton wrote:
So so far we have the introduction of gnome-user-share, which uses an http process dynamically bound to a port running as the user to share stuff in a ~/Public file to the world w/out auth. It sounds like gnome-user-auth will go into core. The restrictions have been put forth:
[...]
What protocol will this be using? (http, ftp, tftp, etc)
As I stated above, it will be using http.
Sorry. Would this be a daemon written just for this? or some other already written daemon? And would it be chrooted?
On Sun, 2005-07-17 at 22:15 -0400, Arthur Pemberton wrote:
Sorry. Would this be a daemon written just for this? or some other already written daemon? And would it be chrooted?
The tool itself is being developed by Gnome folks. I doubt it'll be chrooted and it will be using apache from what I can gather.
On Sun, 2005-07-17 at 17:46 -0700, Jesse Keating wrote:
I've started a new thread because this discussion was going to get lost in the 200+ message thread-o-doom.
So so far we have the introduction of gnome-user-share, which uses an http process dynamically bound to a port running as the user to share stuff in a ~/Public file to the world w/out auth. It sounds like gnome-user-auth will go into core.
I should say that I'm not saying it should go into Core now. It actually needs the GNOME Session Services stuff to land before it works (i.e. without a user needing to drop to a shell and run gnome-user-share manually). We're talking GNOME 2.14, not sure if that'll make FC5.
But yes, when it is included, we can discuss these issues.
On Sun, 2005-07-17 at 22:16 -0400, Colin Walters wrote:
I should say that I'm not saying it should go into Core now. It actually needs the GNOME Session Services stuff to land before it works (i.e. without a user needing to drop to a shell and run gnome-user-share manually). We're talking GNOME 2.14, not sure if that'll make FC5.
But yes, when it is included, we can discuss these issues.
Ok, I was just hoping to get some of these thoughts going before it gets to the point where these things cannot be changed or easily added.
On Sun, 2005-07-17 at 17:46 -0700, Jesse Keating wrote:
So so far we have the introduction of gnome-user-share, which uses an http process dynamically bound to a port running as the user to share stuff in a ~/Public file to the world w/out auth. It sounds like
Is this folder mandatory, or is the path something you may choose? It's just because it is unnecessary clutter imposed in the Desktop (when Desktop == $HOME), and would probably be better suited at some other place like Documents/Public or whatever.
Rui
On Mon, 2005-07-18 at 07:59 +0100, Rui Miguel Seabra wrote:
Is this folder mandatory, or is the path something you may choose? It's just because it is unnecessary clutter imposed in the Desktop (when Desktop == $HOME), and would probably be better suited at some other place like Documents/Public or whatever.
Um... is the Desktop == $HOME in future releases? I rather like Desktop/ being it's own directory. This follows suite from Apple OS X and Windows so it is less confusing for new people. Also I keep a lot of stuff in the root of my home dir, I don't want these displayed on my desktop.
Jesse Keating wrote:
On Mon, 2005-07-18 at 07:59 +0100, Rui Miguel Seabra wrote:
Is this folder mandatory, or is the path something you may choose? It's just because it is unnecessary clutter imposed in the Desktop (when Desktop == $HOME), and would probably be better suited at some other place like Documents/Public or whatever.
Um... is the Desktop == $HOME in future releases? I rather like Desktop/ being it's own directory. This follows suite from Apple OS X and Windows so it is less confusing for new people. Also I keep a lot of stuff in the root of my home dir, I don't want these displayed on my desktop.
no please leave it as it is now Desktop = $HOME would result in to many icons on the Desktop for many users.
On Lun 18 juillet 2005 14:03, dragoran wrote:
Jesse Keating wrote:
On Mon, 2005-07-18 at 07:59 +0100, Rui Miguel Seabra wrote:
Is this folder mandatory, or is the path something you may choose? It's just because it is unnecessary clutter imposed in the Desktop (when Desktop == $HOME), and would probably be better suited at some other place like Documents/Public or whatever.
Um... is the Desktop == $HOME in future releases? I rather like Desktop/ being it's own directory. This follows suite from Apple OS X and Windows so it is less confusing for new people. Also I keep a lot of stuff in the root of my home dir, I don't want these displayed on my desktop.
no please leave it as it is now Desktop = $HOME would result in to many icons on the Desktop for many users.
That's no reason to pollute the $HOME space for people that do use $HOME as desktop today.
$HOME != desktop is nothing but an hack to avoid having to clean up all the legacy apps that put random files here. It's not a license to perpetuate the mess in new Gnome facilities. New apps $HOME usage should set the example so $HOME can be reappropriated in the future.
On Lun 18 juillet 2005 02:46, Jesse Keating wrote:
I've started a new thread because this discussion was going to get lost in the 200+ message thread-o-doom.
So so far we have the introduction of gnome-user-share, which uses an http process dynamically bound to a port running as the user to share stuff in a ~/Public file to the world w/out auth. It sounds like gnome-user-auth will go into core. The restrictions have been put forth:
- Functionality is provided by a package and removed by a package, w/out
core deps.
- Functionality is controlled by a gconf entry which an admin can set to
mandatory off (or just remove the package)
Some ideas that have floated for this package include:
- Functionality disabled until a file is placed in ~/Public prompting
for a dialog box informing the user that the share is now active, with a link to more help in this.
- Gnome-panel icon to show state of sharing with a timeout value to stop
the share (configurable)
- Integration with network-manager to enable/disable the share on
specific networks
Thoughts?
You also need some kind of monitoring to show who's the b*rd that's connecting in the middle of a big download and sucking up all the bandswidth (and a way to selectively kill connections).
Monitoring needs are inversely proportional to the ease with which you can setup shares and make mistakes.
Regards,
man, 18.07.2005 kl. 02.46 skrev Jesse Keating:
I've started a new thread because this discussion was going to get lost in the 200+ message thread-o-doom.
So so far we have the introduction of gnome-user-share, which uses an http process dynamically bound to a port running as the user to share stuff in a ~/Public file to the world w/out auth. It sounds like gnome-user-auth will go into core. The restrictions have been put forth:
- Functionality is provided by a package and removed by a package, w/out
core deps.
- Functionality is controlled by a gconf entry which an admin can set to
mandatory off (or just remove the package)
Some ideas that have floated for this package include:
- Functionality disabled until a file is placed in ~/Public prompting
for a dialog box informing the user that the share is now active, with a link to more help in this.
- Gnome-panel icon to show state of sharing with a timeout value to stop
the share (configurable)
- Integration with network-manager to enable/disable the share on
specific networks
Thoughts?
Any kind of service discovery (akin to bonjour/windows SMB), so that other people would be easily able to find your share?
And for those who hasn't got a autodiscovering client, it should be really easy to find the correct address of the sharing computers display.
What about file uploads - making it possible for other people to upload data to your disk? (WebDAW perhaps?)
Sharing other folders than the standard one?
Making it possible to choose protocols at will - not only Apache/HTTP?
How will it intereact with people who use workstations with NFS mounted homes? Somehow i have a feeling that this is extremely fitting for dynamic workgroup configurations (laptops etc) and home/small office withot servers or tech skill...
Kyrre
-
Arthur Pemberton -
Colin Walters -
dragoran -
Jesse Keating -
Kyrre Ness Sjobak -
Nicolas Mailhot -
Rui Miguel Silva Seabra