Re: Network Manager Autologin
On Fri, 2008-11-07 at 16:37 -0500, Slokunshialgo wrote: > On Tue, 2008-11-04 at 13:46 -0500, Dan Williams wrote: > > On Tue, 2008-11-04 at 15:54 +0100, Pablo Martí wrote: > > > On Tue, Nov 4, 2008 at 3:21 PM, Alexander Sack <[EMAIL PROTECTED]> wrote: > > > > On Tue, Nov 04, 2008 at 03:11:13PM +0100, Pablo Martí wrote: > > > >> Sure! I also think that the Firefox approach is not the right one, is > > > >> just that I'm not very fond on NM's dispatcher > > > >> architecture/capabilities. I kinda like the description/mockup given > > > >> here [0]. Marcelo asked in nm-list 1 year ago and he was pointed to a > > > >> dispatcher script[1]. > > > >> > > > >> [0] > > > >> http://blog.marcelotoledo.org/2007/09/01/network-manager-with-wispr-support/ > > > >> [1] > > > >> http://mail.gnome.org/archives/networkmanager-list/2007-September/msg2.html > > > >> > > > > > > > > OK thanks for the links. I really think this can be done outside of NM > > > > applet to things started. > > > > > > > > Writing a wispr-applet that listens to D-Bus events from NM and which > > > > does the wispr probing and authentication business should be fairly > > > > easy. > > > > > > Thanks for the input Alexander, much appreciated. What do other > > > developers think of this approach? Tambet? Dan? > > > > Shouldn't be part of NM, but NM should expose all the necessary > > information to allow auto-login to be possible using external tools. > > This makes sense, and is what I was thinking > > > If that includes requesting WSP information explicitly from the DHCP > > server, that's great, we should add that. The DHCP information is > > already exposed over D-Bus and thus any app that listens for NM events > > should be able to get it. > > What exactly is WSP? I can't seem to find anything on it. > > > You can tie specific logins pretty easily to each connection's UUID, > > thus if you know that your "Starbucks" connection just came up (as > > opposed to any other connection) you could certainly match that up with > > stored credentials and try to auto-login with those first before doing > > any probing or whatever. Basically, if the AP is at least WPA > > encrypted, and NM connected, there's a 95% chance that nobody is > > spoofing the connection, and that you really are connected to Starbucks, > > so you can save some time probing by just trying stored Starbucks auth > > info first, maybe. > > > > Dan > > The problem I see with using WISPr is that not all networks support it > (the ones I have to log into, for example, don't), and if something was > to be made it should work on any network. > > I know that this may seem like I'm overly invested or interested in the > idea of using Firefox, but I'm looking at it from the standpoint of > flexibility: > - If it's not a WISPr network, it would still work > - If the site needs any special javascript, popups, etc. they can be > taken care of as per manual login > - If there are any weird login errors, it's easier for the user to see & > debug > > > Do we have per-user dispatcher scripts or are you suggesting to open > > the browser as root here :) ? > > > > - Alexander > > God no! > > Reading what you guys have said, how does this sound? > - Store the login page URL in NM, and transmit this along with other > info when connecting, in case anything else wants to use it Again, I don't think this should be or needs to be stored in NM at this time... NM connections have a UUID, so you can store the data in the daemon that keys off the UUID when connections change. Going forward we can try to design a more comprehensive "get me an internet connection" mechanism. Dan > - Have an external program listening for the DBus signals, and, when > picked up, check if FF is running. If not, start it > - Pass these along to Firefox, which would have an extension listening > for the external program > - FF would go to the page and automatically log in to the page, and > allow the user access to the network > > I'm saying to store the URL in NM in case somebody want to make > something for another browser, or using Python, curl, etc. it could > still use it. If it transmits the info and nothing puts it to use, no > harm is done. The external program would be running with user > permissions, not root, even if just to appease Alexander. > > I know I need to look into exactly what info is sent, but how does this > sound so far? > > --Jason > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager Autologin
On Tue, 2008-11-04 at 13:46 -0500, Dan Williams wrote: > On Tue, 2008-11-04 at 15:54 +0100, Pablo Martí wrote: > > On Tue, Nov 4, 2008 at 3:21 PM, Alexander Sack <[EMAIL PROTECTED]> wrote: > > > On Tue, Nov 04, 2008 at 03:11:13PM +0100, Pablo Martí wrote: > > >> Sure! I also think that the Firefox approach is not the right one, is > > >> just that I'm not very fond on NM's dispatcher > > >> architecture/capabilities. I kinda like the description/mockup given > > >> here [0]. Marcelo asked in nm-list 1 year ago and he was pointed to a > > >> dispatcher script[1]. > > >> > > >> [0] > > >> http://blog.marcelotoledo.org/2007/09/01/network-manager-with-wispr-support/ > > >> [1] > > >> http://mail.gnome.org/archives/networkmanager-list/2007-September/msg2.html > > >> > > > > > > OK thanks for the links. I really think this can be done outside of NM > > > applet to things started. > > > > > > Writing a wispr-applet that listens to D-Bus events from NM and which > > > does the wispr probing and authentication business should be fairly > > > easy. > > > > Thanks for the input Alexander, much appreciated. What do other > > developers think of this approach? Tambet? Dan? > > Shouldn't be part of NM, but NM should expose all the necessary > information to allow auto-login to be possible using external tools. This makes sense, and is what I was thinking > If that includes requesting WSP information explicitly from the DHCP > server, that's great, we should add that. The DHCP information is > already exposed over D-Bus and thus any app that listens for NM events > should be able to get it. What exactly is WSP? I can't seem to find anything on it. > You can tie specific logins pretty easily to each connection's UUID, > thus if you know that your "Starbucks" connection just came up (as > opposed to any other connection) you could certainly match that up with > stored credentials and try to auto-login with those first before doing > any probing or whatever. Basically, if the AP is at least WPA > encrypted, and NM connected, there's a 95% chance that nobody is > spoofing the connection, and that you really are connected to Starbucks, > so you can save some time probing by just trying stored Starbucks auth > info first, maybe. > > Dan The problem I see with using WISPr is that not all networks support it (the ones I have to log into, for example, don't), and if something was to be made it should work on any network. I know that this may seem like I'm overly invested or interested in the idea of using Firefox, but I'm looking at it from the standpoint of flexibility: - If it's not a WISPr network, it would still work - If the site needs any special javascript, popups, etc. they can be taken care of as per manual login - If there are any weird login errors, it's easier for the user to see & debug > Do we have per-user dispatcher scripts or are you suggesting to open > the browser as root here :) ? > > - Alexander God no! Reading what you guys have said, how does this sound? - Store the login page URL in NM, and transmit this along with other info when connecting, in case anything else wants to use it - Have an external program listening for the DBus signals, and, when picked up, check if FF is running. If not, start it - Pass these along to Firefox, which would have an extension listening for the external program - FF would go to the page and automatically log in to the page, and allow the user access to the network I'm saying to store the URL in NM in case somebody want to make something for another browser, or using Python, curl, etc. it could still use it. If it transmits the info and nothing puts it to use, no harm is done. The external program would be running with user permissions, not root, even if just to appease Alexander. I know I need to look into exactly what info is sent, but how does this sound so far? --Jason ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager Autologin
On Tue, 2008-11-04 at 15:54 +0100, Pablo Martí wrote: > On Tue, Nov 4, 2008 at 3:21 PM, Alexander Sack <[EMAIL PROTECTED]> wrote: > > On Tue, Nov 04, 2008 at 03:11:13PM +0100, Pablo Martí wrote: > >> Sure! I also think that the Firefox approach is not the right one, is > >> just that I'm not very fond on NM's dispatcher > >> architecture/capabilities. I kinda like the description/mockup given > >> here [0]. Marcelo asked in nm-list 1 year ago and he was pointed to a > >> dispatcher script[1]. > >> > >> [0] > >> http://blog.marcelotoledo.org/2007/09/01/network-manager-with-wispr-support/ > >> [1] > >> http://mail.gnome.org/archives/networkmanager-list/2007-September/msg2.html > >> > > > > OK thanks for the links. I really think this can be done outside of NM > > applet to things started. > > > > Writing a wispr-applet that listens to D-Bus events from NM and which > > does the wispr probing and authentication business should be fairly > > easy. > > Thanks for the input Alexander, much appreciated. What do other > developers think of this approach? Tambet? Dan? Shouldn't be part of NM, but NM should expose all the necessary information to allow auto-login to be possible using external tools. If that includes requesting WSP information explicitly from the DHCP server, that's great, we should add that. The DHCP information is already exposed over D-Bus and thus any app that listens for NM events should be able to get it. You can tie specific logins pretty easily to each connection's UUID, thus if you know that your "Starbucks" connection just came up (as opposed to any other connection) you could certainly match that up with stored credentials and try to auto-login with those first before doing any probing or whatever. Basically, if the AP is at least WPA encrypted, and NM connected, there's a 95% chance that nobody is spoofing the connection, and that you really are connected to Starbucks, so you can save some time probing by just trying stored Starbucks auth info first, maybe. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager Autologin
On Tue, Nov 4, 2008 at 4:10 PM, Tambet Ingo <[EMAIL PROTECTED]> wrote:
> On Tue, Nov 4, 2008 at 4:54 PM, Pablo Martí <[EMAIL PROTECTED]> wrote:
>> On Tue, Nov 4, 2008 at 3:21 PM, Alexander Sack <[EMAIL PROTECTED]> wrote:
>>> OK thanks for the links. I really think this can be done outside of NM
>>> applet to things started.
>>>
>>> Writing a wispr-applet that listens to D-Bus events from NM and which
>>> does the wispr probing and authentication business should be fairly
>>> easy.
>>
>> Thanks for the input Alexander, much appreciated. What do other
>> developers think of this approach? Tambet? Dan?
>
> I agree it should be done outside of NM. That's the point of having a
> stable (yeah, yeah, we'll get to that eventually) public DBus API.
Alright, thanks! I was still doubting between a separate process and a
dispatcher script, but it seems that the consensus is a separate
process. Thanks all for the input!
>
> Tambet
>
--
Pablo Martí
http://www.linkedin.com/in/pmarti || http://www.warp.es
python -c "print '706d6172746940776172702e6573'.decode('hex')"
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager Autologin
On Tue, Nov 4, 2008 at 4:54 PM, Pablo Martí <[EMAIL PROTECTED]> wrote: > On Tue, Nov 4, 2008 at 3:21 PM, Alexander Sack <[EMAIL PROTECTED]> wrote: >> OK thanks for the links. I really think this can be done outside of NM >> applet to things started. >> >> Writing a wispr-applet that listens to D-Bus events from NM and which >> does the wispr probing and authentication business should be fairly >> easy. > > Thanks for the input Alexander, much appreciated. What do other > developers think of this approach? Tambet? Dan? I agree it should be done outside of NM. That's the point of having a stable (yeah, yeah, we'll get to that eventually) public DBus API. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager Autologin
On Tue, Nov 4, 2008 at 3:21 PM, Alexander Sack <[EMAIL PROTECTED]> wrote:
> On Tue, Nov 04, 2008 at 03:11:13PM +0100, Pablo Martí wrote:
>> Sure! I also think that the Firefox approach is not the right one, is
>> just that I'm not very fond on NM's dispatcher
>> architecture/capabilities. I kinda like the description/mockup given
>> here [0]. Marcelo asked in nm-list 1 year ago and he was pointed to a
>> dispatcher script[1].
>>
>> [0]
>> http://blog.marcelotoledo.org/2007/09/01/network-manager-with-wispr-support/
>> [1]
>> http://mail.gnome.org/archives/networkmanager-list/2007-September/msg2.html
>>
>
> OK thanks for the links. I really think this can be done outside of NM
> applet to things started.
>
> Writing a wispr-applet that listens to D-Bus events from NM and which
> does the wispr probing and authentication business should be fairly
> easy.
Thanks for the input Alexander, much appreciated. What do other
developers think of this approach? Tambet? Dan?
Regards,
>
> - Alexander
>
>
--
Pablo Martí
http://www.linkedin.com/in/pmarti || http://www.warp.es
python -c "print '706d6172746940776172702e6573'.decode('hex')"
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager Autologin
On Tue, Nov 4, 2008 at 3:10 PM, Patryk Zawadzki <[EMAIL PROTECTED]> wrote:
> On Tue, Nov 4, 2008 at 3:06 PM, Pablo Martí <[EMAIL PROTECTED]> wrote:
>> No, the very first time you interact with the hotspot, you'll be
>> redirected to the login page anyway. You'll have to accept the ToS and
>> *pay*. The use-case discussed here is after paying for the access, not
>> having to explicitly log in the hotspot every time you want to use
>> afterwards
>
> Then it's entirely doable as a Firefox extension without any NM
> integration (check if the page is the login one, submit data and
> reload) or easily doable using python, dbus and curl (wait for
> connection, check SSID, if matching call curl with necessary POST
> payload - could be read from the keyring).
It is doable sure, but it depends on the context. What if you have no
firefox on the system. What if you just want to irssi a bit? Coupling
the solution to firefox is a no-go IMHO and is already done[0].
[0] http://coova.org/wiki/index.php/CoovaFX
--
Pablo Martí
http://www.linkedin.com/in/pmarti || http://www.warp.es
python -c "print '706d6172746940776172702e6573'.decode('hex')"
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager Autologin
On Tue, Nov 04, 2008 at 03:11:13PM +0100, Pablo Martí wrote: > Sure! I also think that the Firefox approach is not the right one, is > just that I'm not very fond on NM's dispatcher > architecture/capabilities. I kinda like the description/mockup given > here [0]. Marcelo asked in nm-list 1 year ago and he was pointed to a > dispatcher script[1]. > > [0] > http://blog.marcelotoledo.org/2007/09/01/network-manager-with-wispr-support/ > [1] > http://mail.gnome.org/archives/networkmanager-list/2007-September/msg2.html > OK thanks for the links. I really think this can be done outside of NM applet to things started. Writing a wispr-applet that listens to D-Bus events from NM and which does the wispr probing and authentication business should be fairly easy. - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager Autologin
El mar, 04-11-2008 a las 15:02 +0100, Patryk Zawadzki escribió: > On Tue, Nov 4, 2008 at 2:46 PM, Alexander Sack <[EMAIL PROTECTED]> wrote: > > On Tue, Nov 04, 2008 at 02:13:37PM +0100, Pablo Martí wrote: > >> The benefit is that the user is not redirected to the hotspot webpage, > >> but is logged in automatically. It might seem a silly difference, but > >> is a requested feature. Our customer requires WISPr/WSP capabilities > >> and I'm very interested in the outcome of this thread. > > I agree that it would be nice to be automatically logged in, but I > > don't clearly see how why we need firefox to do that authentication. > > > > Another idea would be to write a tray applet that recognizes when NM > > goes online and the probes whether it gets redirected to hotspot > > site. If thats the case the tray thing would authenticate and would > > allow users also to end that session later (from the tray). This could > > be done by nm applet itself, but as we dont really have a plugin > > infrastructure for that yet I would suggest to make that a standalone > > tray tool until we have more experience on what we really want > > here. Would that work? > > I think the important question is: isn't this a direct violation of > the ToS? By automatically doing something that was created to enforce > user interaction you are creating a tool that silently accepts all > licenses, terms and conditions without notifying the user. Uhmmm not really sure... It seems it tries to be a standard thing: "WISPr was the first step toward standardizing HotSpot authentication."[0] Moreover, this is not the first time this protocol is around this list[1], although the answer was the same as the beginning of this thread [0]http://en.wikipedia.org/wiki/WISPr [1]http://mail.gnome.org/archives/networkmanager-list/2007-September/msg0.html Kind regards, -- Daniel Baeyens ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager Autologin
On Tue, Nov 4, 2008 at 2:46 PM, Alexander Sack <[EMAIL PROTECTED]> wrote:
> On Tue, Nov 04, 2008 at 02:13:37PM +0100, Pablo Martí wrote:
>> On Tue, Nov 4, 2008 at 1:21 PM, Alexander Sack <[EMAIL PROTECTED]> wrote:
>> > On Tue, Nov 04, 2008 at 01:29:22PM +0200, Tambet Ingo wrote:
>> >> On Tue, Nov 4, 2008 at 1:00 PM, Alexander Sack <[EMAIL PROTECTED]> wrote:
>> >> > On Tue, Nov 04, 2008 at 10:44:59AM +0200, Tambet Ingo wrote:
>> >> >>
>> >> >> Add a dispatcher script that runs "xdg-open $url" for a specific SSID
>> >> >> you need it for and you're done.
>> >> >
>> >> > Do we have per-user dispatcher scripts or are you suggesting to open
>> >> > the browser as root here :) ?
>> >>
>> >> Ok, you're right, but listening for a DBus signal from a user process
>> >> isn't all that hard either. Or do you prefer NM executing firefox
>> >> directly (as root) like the original mail suggested?
>> >>
>> >
>> > Dbus would work. However, I dont really understand the use-case this
>> > is supposed to cover. The browser usually redirects to the login site
>> > anyway? What benefit would the user by such a firefox extension?
>>
>> The benefit is that the user is not redirected to the hotspot webpage,
>> but is logged in automatically. It might seem a silly difference, but
>> is a requested feature. Our customer requires WISPr/WSP capabilities
>> and I'm very interested in the outcome of this thread.
>
> I agree that it would be nice to be automatically logged in, but I
> don't clearly see how why we need firefox to do that authentication.
>
> Another idea would be to write a tray applet that recognizes when NM
> goes online and the probes whether it gets redirected to hotspot
> site. If thats the case the tray thing would authenticate and would
> allow users also to end that session later (from the tray). This could
> be done by nm applet itself, but as we dont really have a plugin
> infrastructure for that yet I would suggest to make that a standalone
> tray tool until we have more experience on what we really want
> here. Would that work?
Sure! I also think that the Firefox approach is not the right one, is
just that I'm not very fond on NM's dispatcher
architecture/capabilities. I kinda like the description/mockup given
here [0]. Marcelo asked in nm-list 1 year ago and he was pointed to a
dispatcher script[1].
[0] http://blog.marcelotoledo.org/2007/09/01/network-manager-with-wispr-support/
[1]
http://mail.gnome.org/archives/networkmanager-list/2007-September/msg2.html
>
>
> - Alexander
>
>
--
Pablo Martí
http://www.linkedin.com/in/pmarti || http://www.warp.es
python -c "print '706d6172746940776172702e6573'.decode('hex')"
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager Autologin
On Tue, Nov 4, 2008 at 3:06 PM, Pablo Martí <[EMAIL PROTECTED]> wrote: > No, the very first time you interact with the hotspot, you'll be > redirected to the login page anyway. You'll have to accept the ToS and > *pay*. The use-case discussed here is after paying for the access, not > having to explicitly log in the hotspot every time you want to use > afterwards Then it's entirely doable as a Firefox extension without any NM integration (check if the page is the login one, submit data and reload) or easily doable using python, dbus and curl (wait for connection, check SSID, if matching call curl with necessary POST payload - could be read from the keyring). -- Patryk Zawadzki ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager Autologin
On Tue, Nov 04, 2008 at 03:02:04PM +0100, Patryk Zawadzki wrote: > On Tue, Nov 4, 2008 at 2:46 PM, Alexander Sack <[EMAIL PROTECTED]> wrote: > > On Tue, Nov 04, 2008 at 02:13:37PM +0100, Pablo Martí wrote: > >> The benefit is that the user is not redirected to the hotspot webpage, > >> but is logged in automatically. It might seem a silly difference, but > >> is a requested feature. Our customer requires WISPr/WSP capabilities > >> and I'm very interested in the outcome of this thread. > > I agree that it would be nice to be automatically logged in, but I > > don't clearly see how why we need firefox to do that authentication. > > > > Another idea would be to write a tray applet that recognizes when NM > > goes online and the probes whether it gets redirected to hotspot > > site. If thats the case the tray thing would authenticate and would > > allow users also to end that session later (from the tray). This could > > be done by nm applet itself, but as we dont really have a plugin > > infrastructure for that yet I would suggest to make that a standalone > > tray tool until we have more experience on what we really want > > here. Would that work? > > I think the important question is: isn't this a direct violation of > the ToS? By automatically doing something that was created to enforce > user interaction you are creating a tool that silently accepts all > licenses, terms and conditions without notifying the user. > >From what i understand the user would still have to provide some form of credentials. Thus the user would be presented at minimum an initial login dialog, where he probably could opt-in for auto login in the future. - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager Autologin
On Tue, Nov 4, 2008 at 3:02 PM, Patryk Zawadzki <[EMAIL PROTECTED]> wrote:
> On Tue, Nov 4, 2008 at 2:46 PM, Alexander Sack <[EMAIL PROTECTED]> wrote:
>> On Tue, Nov 04, 2008 at 02:13:37PM +0100, Pablo Martí wrote:
>>> The benefit is that the user is not redirected to the hotspot webpage,
>>> but is logged in automatically. It might seem a silly difference, but
>>> is a requested feature. Our customer requires WISPr/WSP capabilities
>>> and I'm very interested in the outcome of this thread.
>> I agree that it would be nice to be automatically logged in, but I
>> don't clearly see how why we need firefox to do that authentication.
>>
>> Another idea would be to write a tray applet that recognizes when NM
>> goes online and the probes whether it gets redirected to hotspot
>> site. If thats the case the tray thing would authenticate and would
>> allow users also to end that session later (from the tray). This could
>> be done by nm applet itself, but as we dont really have a plugin
>> infrastructure for that yet I would suggest to make that a standalone
>> tray tool until we have more experience on what we really want
>> here. Would that work?
>
> I think the important question is: isn't this a direct violation of
> the ToS? By automatically doing something that was created to enforce
> user interaction you are creating a tool that silently accepts all
> licenses, terms and conditions without notifying the user.
No, the very first time you interact with the hotspot, you'll be
redirected to the login page anyway. You'll have to accept the ToS and
*pay*. The use-case discussed here is after paying for the access, not
having to explicitly log in the hotspot every time you want to use
afterwards
Pablo
>
> --
> Patryk Zawadzki
>
--
Pablo Martí
http://www.linkedin.com/in/pmarti || http://www.warp.es
python -c "print '706d6172746940776172702e6573'.decode('hex')"
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager Autologin
On Tue, Nov 4, 2008 at 2:46 PM, Alexander Sack <[EMAIL PROTECTED]> wrote: > On Tue, Nov 04, 2008 at 02:13:37PM +0100, Pablo Martí wrote: >> The benefit is that the user is not redirected to the hotspot webpage, >> but is logged in automatically. It might seem a silly difference, but >> is a requested feature. Our customer requires WISPr/WSP capabilities >> and I'm very interested in the outcome of this thread. > I agree that it would be nice to be automatically logged in, but I > don't clearly see how why we need firefox to do that authentication. > > Another idea would be to write a tray applet that recognizes when NM > goes online and the probes whether it gets redirected to hotspot > site. If thats the case the tray thing would authenticate and would > allow users also to end that session later (from the tray). This could > be done by nm applet itself, but as we dont really have a plugin > infrastructure for that yet I would suggest to make that a standalone > tray tool until we have more experience on what we really want > here. Would that work? I think the important question is: isn't this a direct violation of the ToS? By automatically doing something that was created to enforce user interaction you are creating a tool that silently accepts all licenses, terms and conditions without notifying the user. -- Patryk Zawadzki ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager Autologin
On Tue, Nov 04, 2008 at 02:13:37PM +0100, Pablo Martí wrote: > On Tue, Nov 4, 2008 at 1:21 PM, Alexander Sack <[EMAIL PROTECTED]> wrote: > > On Tue, Nov 04, 2008 at 01:29:22PM +0200, Tambet Ingo wrote: > >> On Tue, Nov 4, 2008 at 1:00 PM, Alexander Sack <[EMAIL PROTECTED]> wrote: > >> > On Tue, Nov 04, 2008 at 10:44:59AM +0200, Tambet Ingo wrote: > >> >> > >> >> Add a dispatcher script that runs "xdg-open $url" for a specific SSID > >> >> you need it for and you're done. > >> > > >> > Do we have per-user dispatcher scripts or are you suggesting to open > >> > the browser as root here :) ? > >> > >> Ok, you're right, but listening for a DBus signal from a user process > >> isn't all that hard either. Or do you prefer NM executing firefox > >> directly (as root) like the original mail suggested? > >> > > > > Dbus would work. However, I dont really understand the use-case this > > is supposed to cover. The browser usually redirects to the login site > > anyway? What benefit would the user by such a firefox extension? > > The benefit is that the user is not redirected to the hotspot webpage, > but is logged in automatically. It might seem a silly difference, but > is a requested feature. Our customer requires WISPr/WSP capabilities > and I'm very interested in the outcome of this thread. I agree that it would be nice to be automatically logged in, but I don't clearly see how why we need firefox to do that authentication. Another idea would be to write a tray applet that recognizes when NM goes online and the probes whether it gets redirected to hotspot site. If thats the case the tray thing would authenticate and would allow users also to end that session later (from the tray). This could be done by nm applet itself, but as we dont really have a plugin infrastructure for that yet I would suggest to make that a standalone tray tool until we have more experience on what we really want here. Would that work? - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager Autologin
On Tue, Nov 4, 2008 at 2:13 PM, Pablo Martí <[EMAIL PROTECTED]> wrote:
> On Tue, Nov 4, 2008 at 1:21 PM, Alexander Sack <[EMAIL PROTECTED]> wrote:
>> On Tue, Nov 04, 2008 at 01:29:22PM +0200, Tambet Ingo wrote:
>>> On Tue, Nov 4, 2008 at 1:00 PM, Alexander Sack <[EMAIL PROTECTED]> wrote:
>>> > On Tue, Nov 04, 2008 at 10:44:59AM +0200, Tambet Ingo wrote:
>>> >>
>>> >> Add a dispatcher script that runs "xdg-open $url" for a specific SSID
>>> >> you need it for and you're done.
>>> >
>>> > Do we have per-user dispatcher scripts or are you suggesting to open
>>> > the browser as root here :) ?
>>>
>>> Ok, you're right, but listening for a DBus signal from a user process
>>> isn't all that hard either. Or do you prefer NM executing firefox
>>> directly (as root) like the original mail suggested?
>>>
>>
>> Dbus would work. However, I dont really understand the use-case this
>> is supposed to cover. The browser usually redirects to the login site
>> anyway? What benefit would the user by such a firefox extension?
>
> The benefit is that the user is not redirected to the hotspot webpage,
> but is logged in automatically. It might seem a silly difference, but
> is a requested feature. Our customer requires WISPr/WSP capabilities
> and I'm very interested in the outcome of this thread.
s/WSP//g mental corruption here :)
>
> Pablo
>
>>
>>
>> - Alexander
>>
>> ___
>> NetworkManager-list mailing list
>> NetworkManager-list@gnome.org
>> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>>
>
>
>
> --
> Pablo Martí
> http://www.linkedin.com/in/pmarti || http://www.warp.es
> python -c "print '706d6172746940776172702e6573'.decode('hex')"
>
--
Pablo Martí
http://www.linkedin.com/in/pmarti || http://www.warp.es
python -c "print '706d6172746940776172702e6573'.decode('hex')"
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager Autologin
On Tue, Nov 4, 2008 at 1:21 PM, Alexander Sack <[EMAIL PROTECTED]> wrote:
> On Tue, Nov 04, 2008 at 01:29:22PM +0200, Tambet Ingo wrote:
>> On Tue, Nov 4, 2008 at 1:00 PM, Alexander Sack <[EMAIL PROTECTED]> wrote:
>> > On Tue, Nov 04, 2008 at 10:44:59AM +0200, Tambet Ingo wrote:
>> >>
>> >> Add a dispatcher script that runs "xdg-open $url" for a specific SSID
>> >> you need it for and you're done.
>> >
>> > Do we have per-user dispatcher scripts or are you suggesting to open
>> > the browser as root here :) ?
>>
>> Ok, you're right, but listening for a DBus signal from a user process
>> isn't all that hard either. Or do you prefer NM executing firefox
>> directly (as root) like the original mail suggested?
>>
>
> Dbus would work. However, I dont really understand the use-case this
> is supposed to cover. The browser usually redirects to the login site
> anyway? What benefit would the user by such a firefox extension?
The benefit is that the user is not redirected to the hotspot webpage,
but is logged in automatically. It might seem a silly difference, but
is a requested feature. Our customer requires WISPr/WSP capabilities
and I'm very interested in the outcome of this thread.
Pablo
>
>
> - Alexander
>
> ___
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>
--
Pablo Martí
http://www.linkedin.com/in/pmarti || http://www.warp.es
python -c "print '706d6172746940776172702e6573'.decode('hex')"
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager Autologin
On Tue, Nov 04, 2008 at 01:29:22PM +0200, Tambet Ingo wrote: > On Tue, Nov 4, 2008 at 1:00 PM, Alexander Sack <[EMAIL PROTECTED]> wrote: > > On Tue, Nov 04, 2008 at 10:44:59AM +0200, Tambet Ingo wrote: > >> > >> Add a dispatcher script that runs "xdg-open $url" for a specific SSID > >> you need it for and you're done. > > > > Do we have per-user dispatcher scripts or are you suggesting to open > > the browser as root here :) ? > > Ok, you're right, but listening for a DBus signal from a user process > isn't all that hard either. Or do you prefer NM executing firefox > directly (as root) like the original mail suggested? > Dbus would work. However, I dont really understand the use-case this is supposed to cover. The browser usually redirects to the login site anyway? What benefit would the user by such a firefox extension? - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager Autologin
On Tue, Nov 4, 2008 at 1:00 PM, Alexander Sack <[EMAIL PROTECTED]> wrote: > On Tue, Nov 04, 2008 at 10:44:59AM +0200, Tambet Ingo wrote: >> >> Add a dispatcher script that runs "xdg-open $url" for a specific SSID >> you need it for and you're done. > > Do we have per-user dispatcher scripts or are you suggesting to open > the browser as root here :) ? Ok, you're right, but listening for a DBus signal from a user process isn't all that hard either. Or do you prefer NM executing firefox directly (as root) like the original mail suggested? Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager Autologin
On Tue, Nov 04, 2008 at 10:44:59AM +0200, Tambet Ingo wrote: > > Add a dispatcher script that runs "xdg-open $url" for a specific SSID > you need it for and you're done. Do we have per-user dispatcher scripts or are you suggesting to open the browser as root here :) ? - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager Autologin
On Tue, Nov 4, 2008 at 1:41 AM, Slokunshialgo <[EMAIL PROTECTED]> wrote: > I know I posted something about this awhile ago, but thinking about it a > bit more, a couple of questions and ideas have arisen in my mind. For > those who may not have read this before, the idea is to have something > using NetworkManager to automatically log in to web-authenticated > networks (ie: hotspots in a cafe) when it connects to specific networks. > > I have three ideas on how to implement this, but they all revolve around > the idea of having a Firefox extension that would listen to dbus signals > being sent by nm, and when told to, would go to a specific webpage to > log in, using Firefox's password storage. > > 1) Have nm check to see if Firefox is open, if not, open it and send the > signal > 2) Make nm have nothing to do with the extension, but merely sending its > regular signals and FF picking them up > 3) Make nm send modified signals specifically for the autologin, letting > any program pick them up (such as network name, URL to visit, etc) > > Judging by before, I doubt #1 would be the best idea (forcing FF to be > installed is not good), #2 may or may not work, but I think #3 would be > best. To get around whether FF is open or not, a small program could be > written to start on login (separate from nm) that would listen for the > signals, start FF, and pass it along. > > As for the technical side of this, it's primarily, what sort of > information does nm send through dbus, and are multiple programs able to > pick up on it? > > Opinions, ideas, information? Add a dispatcher script that runs "xdg-open $url" for a specific SSID you need it for and you're done. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
