From: Christopher P. B. <ba...@um...> - 2005-09-15 01:26:23
Attachments:
smime.p7s
|
Hi list, I am in a strange wireless network situation here on campus. In order to use the wireless network, users must authenticate with their campus username and password on a secure webpage. I am using a belkin wireless card to access the network (which is successful), but when the authentication page comes up, I am unable to view it using the no_ssl version of links. Authenticating via this webpage is the only way the wireless routers will let one on the network. The only other alternative is a cisco vpn client, and my web research indicates that openvpn does not work well with cisco''s vpn system. How difficult would it be to compile links with ssl? Has anyone done this? Does anyone have another idea about how to log onto a ssl http page and log in? Cheers, Christopher |
From: Craig H. <cr...@gu...> - 2005-09-15 03:26:02
|
On Sep 14, 2005, at 6:26 PM, Christopher P. Baker wrote: > I am in a strange wireless network situation here on campus. In > order to use the wireless network, users must authenticate with > their campus username and password on a secure webpage. I am using > a belkin wireless card to access the network (which is successful), > but when the authentication page comes up, I am unable to view it > using the no_ssl version of links. Authenticating via this webpage > is the only way the wireless routers will let one on the network. > The only other alternative is a cisco vpn client, and my web > research indicates that openvpn does not work well with cisco''s > vpn system. > > How difficult would it be to compile links with ssl? Has anyone > done this? Does anyone have another idea about how to log onto a > ssl http page and log in? Do you need full-blown links, or would wget or curl or something be sufficient? Or even socat with ssl support? Any of them ought to be possible in theory, if you compile openssl and then turn on the required ssl options (probably by modifying the makefile for call configure with different options). C |
From: <ba...@ho...> - 2005-09-15 17:52:34
Attachments:
smime.p7s
|
So I looked into several options that allowed me to log in on the wireless network here on campus: ssl enabled curl and wget allow posting forms using the -d/--post- data option. the following worked well from my laptop: curl -d "uid=xxx" -d "upass=xxx" -d "desturl=http://www.umn.edu" -d "ip=xxx.xxx.xxx.xxx" -d "opt=auth" https://wireless.netaccess.umn.edu/ cgi-bin/x5.cgi? wget --post-data="uid=xxx&upass=xxx& etc etc" https:// wireless.netaccess.umn.edu/cgi-bin/x5.cgi? BUT, currently there is no (to my knowledge) version of curl with ssl support on the gumstix. Additionally, the busybox wget doesn't have ssl support and doesn't support the --post-data flag anyway. Would it be possible to compile curl-ssl for the gumstix? If not, that leaves me to use socat. Would it be possible to use socat to open up a connection to the https server and pipe something like the following to into socat: --snip-- POST /path/script.cgi HTTP/1.0 User-Agent: HTTPTool/1.0 Content-Type: application/x-www-form-urlencoded Content-Length: 32 home=Cosby&favorite+flavor=flies --snip-- where the information above was the information required by the authentication server? If this is possible, then I need to get socat compiled with openssl. I noticed that the socat.mk file has the --disable- openssl . Would recompilling it without this flag yield the socat ssl binary i need? This all seems like a round-about way of posting to a secure http web form. Any other ideas out there? Thanks for all of the help. Christopher On Sep 14, 2005, at 10:25 PM, Craig Hughes wrote: > On Sep 14, 2005, at 6:26 PM, Christopher P. Baker wrote: > > >> I am in a strange wireless network situation here on campus. In >> order to use the wireless network, users must authenticate with >> their campus username and password on a secure webpage. I am >> using a belkin wireless card to access the network (which is >> successful), but when the authentication page comes up, I am >> unable to view it using the no_ssl version of links. >> Authenticating via this webpage is the only way the wireless >> routers will let one on the network. The only other alternative >> is a cisco vpn client, and my web research indicates that openvpn >> does not work well with cisco''s vpn system. >> >> How difficult would it be to compile links with ssl? Has anyone >> done this? Does anyone have another idea about how to log onto a >> ssl http page and log in? >> > > Do you need full-blown links, or would wget or curl or something be > sufficient? Or even socat with ssl support? Any of them ought to > be possible in theory, if you compile openssl and then turn on the > required ssl options (probably by modifying the makefile for call > configure with different options). > > C > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App > Server.Download it for free - -and be entered to win a 42" plasma > tv or your very > own Sony(tm)PSP. Click here to play: http://sourceforge.net/ > geronimo.php > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Craig H. <cr...@gu...> - 2005-09-15 18:35:34
Attachments:
socat-ssl.patch
|
On Sep 15, 2005, at 10:51 AM, ba...@ho... wrote: > BUT, currently there is no (to my knowledge) version of curl with > ssl support on the gumstix. Additionally, the busybox wget doesn't > have ssl support and doesn't support the --post-data flag anyway. I have to admit I didn't actually look at the busybox config -- you're right, no easy ssl option there. > Would it be possible to compile curl-ssl for the gumstix? > > If not, that leaves me to use socat. > > Would it be possible to use socat to open up a connection to the > https server and pipe something like the following to into socat: > > --snip-- > > POST /path/script.cgi HTTP/1.0 > User-Agent: HTTPTool/1.0 > Content-Type: application/x-www-form-urlencoded > Content-Length: 32 > > home=Cosby&favorite+flavor=flies > > --snip-- > > where the information above was the information required by the > authentication server? > > If this is possible, then I need to get socat compiled with > openssl. I noticed that the socat.mk file has the --disable- > openssl . Would recompilling it without this flag yield the socat > ssl binary i need? The first thing you'd need to do is compile openssl so you have the necessary libs, and then compile socat without the --disable-openssl option (might need --with-ssl=/path/to/ssl or something) > This all seems like a round-about way of posting to a secure http > web form. Any other ideas out there? Well, you might be able to cheat, depending on how your network is set up. Can you make DNS queries before authenticating? How about ICMP packets? If you can get *any* traffic out to the network, and you have control of a fixed host on the network somewhere, you should be able to pass the relevant info (which looks like the IP address you've been assigned) to your fixed host, and have it respond by authenticating for you, eg: /etc/network/interfaces: ... iface wlan0 dhcp up remote_authenticate_me.sh ... /usr/bin/remote_authenticate_me.sh: MYHOSTIP=`ping -c 1 hostname.that.you.control | head -1 | awk '{print $3}' | sed -e 's/(\(.*\)):/\1/'` mv /etc/resolv.conf /tmp/resolv.conf echo nameserver $MYHOSTIP > /etc/resolv.conf ping -c 1 `ifconfig wlan0 | grep 'inet addr' | awk '{print $2}' | awk -F: '{print $2}'`.somesecret.fake mv /tmp/resolv.conf /etc/resolv.conf There you go, now all you have to do is set up a process on UDP port 53 on hostname.that.you.control which will respond to DNS queries which ask for an A record for *.somesecret.fake by issuing the https request for you ;) ...of course it's probably easier to just compile socat-ssl support, using the attached patch. C |
From: <ba...@ho...> - 2005-09-16 02:13:32
Attachments:
smime.p7s
|
very clever :) I'm going to try to compile this now ... CB On Sep 15, 2005, at 1:34 PM, Craig Hughes wrote: > On Sep 15, 2005, at 10:51 AM, ba...@ho... wrote: > > >> BUT, currently there is no (to my knowledge) version of curl with >> ssl support on the gumstix. Additionally, the busybox wget >> doesn't have ssl support and doesn't support the --post-data flag >> anyway. >> > > I have to admit I didn't actually look at the busybox config -- > you're right, no easy ssl option there. > > >> Would it be possible to compile curl-ssl for the gumstix? >> >> If not, that leaves me to use socat. >> >> Would it be possible to use socat to open up a connection to the >> https server and pipe something like the following to into socat: >> >> --snip-- >> >> POST /path/script.cgi HTTP/1.0 >> User-Agent: HTTPTool/1.0 >> Content-Type: application/x-www-form-urlencoded >> Content-Length: 32 >> >> home=Cosby&favorite+flavor=flies >> >> --snip-- >> >> where the information above was the information required by the >> authentication server? >> >> If this is possible, then I need to get socat compiled with >> openssl. I noticed that the socat.mk file has the --disable- >> openssl . Would recompilling it without this flag yield the socat >> ssl binary i need? >> > > The first thing you'd need to do is compile openssl so you have the > necessary libs, and then compile socat without the --disable- > openssl option (might need --with-ssl=/path/to/ssl or something) > > >> This all seems like a round-about way of posting to a secure http >> web form. Any other ideas out there? >> > > Well, you might be able to cheat, depending on how your network is > set up. Can you make DNS queries before authenticating? How about > ICMP packets? If you can get *any* traffic out to the network, and > you have control of a fixed host on the network somewhere, you > should be able to pass the relevant info (which looks like the IP > address you've been assigned) to your fixed host, and have it > respond by authenticating for you, eg: > > /etc/network/interfaces: > > ... > iface wlan0 dhcp > up remote_authenticate_me.sh > ... > > /usr/bin/remote_authenticate_me.sh: > MYHOSTIP=`ping -c 1 hostname.that.you.control | head -1 | awk > '{print $3}' | sed -e 's/(\(.*\)):/\1/'` > mv /etc/resolv.conf /tmp/resolv.conf > echo nameserver $MYHOSTIP > /etc/resolv.conf > ping -c 1 `ifconfig wlan0 | grep 'inet addr' | awk '{print $2}' | > awk -F: '{print $2}'`.somesecret.fake > mv /tmp/resolv.conf /etc/resolv.conf > > > There you go, now all you have to do is set up a process on UDP > port 53 on hostname.that.you.control which will respond to DNS > queries which ask for an A record for *.somesecret.fake by issuing > the https request for you ;) > > ...of course it's probably easier to just compile socat-ssl > support, using the attached patch. > > C > > > <socat-ssl.patch> > |
From: <ba...@ho...> - 2005-09-16 02:26:59
Attachments:
smime.p7s
|
for some reason, the patch you sent along didn't arrive in tact. patch says only garbage was found .... i issued the command patch make/socat.mk socat-ssl.patch is this correct? Inspection of the patch in vi revealed a lot of strange escape characters that didn't look like they belonged in normal text file. Any tips? Or, could you resend either the patch file or the mk file? Thanks, Christopher On Sep 15, 2005, at 1:34 PM, Craig Hughes wrote: > On Sep 15, 2005, at 10:51 AM, ba...@ho... wrote: > > >> BUT, currently there is no (to my knowledge) version of curl with >> ssl support on the gumstix. Additionally, the busybox wget >> doesn't have ssl support and doesn't support the --post-data flag >> anyway. >> > > I have to admit I didn't actually look at the busybox config -- > you're right, no easy ssl option there. > > >> Would it be possible to compile curl-ssl for the gumstix? >> >> If not, that leaves me to use socat. >> >> Would it be possible to use socat to open up a connection to the >> https server and pipe something like the following to into socat: >> >> --snip-- >> >> POST /path/script.cgi HTTP/1.0 >> User-Agent: HTTPTool/1.0 >> Content-Type: application/x-www-form-urlencoded >> Content-Length: 32 >> >> home=Cosby&favorite+flavor=flies >> >> --snip-- >> >> where the information above was the information required by the >> authentication server? >> >> If this is possible, then I need to get socat compiled with >> openssl. I noticed that the socat.mk file has the --disable- >> openssl . Would recompilling it without this flag yield the socat >> ssl binary i need? >> > > The first thing you'd need to do is compile openssl so you have the > necessary libs, and then compile socat without the --disable- > openssl option (might need --with-ssl=/path/to/ssl or something) > > >> This all seems like a round-about way of posting to a secure http >> web form. Any other ideas out there? >> > > Well, you might be able to cheat, depending on how your network is > set up. Can you make DNS queries before authenticating? How about > ICMP packets? If you can get *any* traffic out to the network, and > you have control of a fixed host on the network somewhere, you > should be able to pass the relevant info (which looks like the IP > address you've been assigned) to your fixed host, and have it > respond by authenticating for you, eg: > > /etc/network/interfaces: > > ... > iface wlan0 dhcp > up remote_authenticate_me.sh > ... > > /usr/bin/remote_authenticate_me.sh: > MYHOSTIP=`ping -c 1 hostname.that.you.control | head -1 | awk > '{print $3}' | sed -e 's/(\(.*\)):/\1/'` > mv /etc/resolv.conf /tmp/resolv.conf > echo nameserver $MYHOSTIP > /etc/resolv.conf > ping -c 1 `ifconfig wlan0 | grep 'inet addr' | awk '{print $2}' | > awk -F: '{print $2}'`.somesecret.fake > mv /tmp/resolv.conf /etc/resolv.conf > > > There you go, now all you have to do is set up a process on UDP > port 53 on hostname.that.you.control which will respond to DNS > queries which ask for an A record for *.somesecret.fake by issuing > the https request for you ;) > > ...of course it's probably easier to just compile socat-ssl > support, using the attached patch. > > C > > > <socat-ssl.patch> > |
From: Craig H. <cr...@gu...> - 2005-09-16 04:08:32
Attachments:
socat-ssl.patch
|
On Sep 15, 2005, at 7:26 PM, ba...@ho... wrote: > for some reason, the patch you sent along didn't arrive in tact. > patch says only garbage was found .... Oops, I generated the patch with "colordiff" on, so it inserted some ANSI coloring in there. Here's the patch again with that stuff stripped out. C |
From: <ba...@ho...> - 2005-09-19 17:51:35
Attachments:
smime.p7s
|
Just FYI, I ended up solving this problem by writing a very small http "post" application using the openssl library. Essentially it just opens up a secure connection to the https server, issues a post command and waits for the response. It works great! Thanks for all of the suggestions. Christopher On Sep 15, 2005, at 11:07 PM, Craig Hughes wrote: > On Sep 15, 2005, at 7:26 PM, ba...@ho... wrote: > > >> for some reason, the patch you sent along didn't arrive in tact. >> patch says only garbage was found .... >> > > Oops, I generated the patch with "colordiff" on, so it inserted > some ANSI coloring in there. Here's the patch again with that > stuff stripped out. > > C > > > <socat-ssl.patch> > |
From: Martin M. <ca...@we...> - 2005-09-15 18:51:01
|
Sicherheitshinweis Ein Sicherheitsproblem ist mit dieser Nachricht aufgetreten. Überprüfen Sie die unten stehenden hervorgehobenen Objekte: Die Nachricht wurde nicht gefälscht Sie halten die signierte digitale ID für vertrauenswürdig Die digitale ID ist nicht abgelaufen Die E-Mail-Adresse der digitalen ID entspricht nicht der Absenderadresse Signaturgeber: ba...@um... Absender: ba...@ho... Die digitale ID wurde nicht zurückgezogen oder es konnten keine Informationen diesbezüglich für dieses Zertifikat bestimmt werden. Es sind keine anderen Probleme mit der digitalen ID aufgetreten. Diese Meldung nicht mehr anzeigen. ----- Original Message ----- From: <ba...@ho...> To: <gum...@li...> Sent: Thursday, September 15, 2005 7:51 PM Subject: Re: [Gumstix-users] links with ssl? > So I looked into several options that allowed me to log in on the > wireless network here on campus: > > ssl enabled curl and wget allow posting forms using the -d/--post- data > option. the following worked well from my laptop: > curl -d "uid=xxx" -d "upass=xxx" -d "desturl=http://www.umn.edu" -d > "ip=xxx.xxx.xxx.xxx" -d "opt=auth" https://wireless.netaccess.umn.edu/ > cgi-bin/x5.cgi? > wget --post-data="uid=xxx&upass=xxx& etc etc" https:// > wireless.netaccess.umn.edu/cgi-bin/x5.cgi? > > BUT, currently there is no (to my knowledge) version of curl with ssl > support on the gumstix. Additionally, the busybox wget doesn't have ssl > support and doesn't support the --post-data flag anyway. > > Would it be possible to compile curl-ssl for the gumstix? > > If not, that leaves me to use socat. > > Would it be possible to use socat to open up a connection to the https > server and pipe something like the following to into socat: > > --snip-- > > POST /path/script.cgi HTTP/1.0 > User-Agent: HTTPTool/1.0 > Content-Type: application/x-www-form-urlencoded > Content-Length: 32 > > home=Cosby&favorite+flavor=flies > > --snip-- > > where the information above was the information required by the > authentication server? > > If this is possible, then I need to get socat compiled with openssl. I > noticed that the socat.mk file has the --disable- openssl . Would > recompilling it without this flag yield the socat ssl binary i need? > > This all seems like a round-about way of posting to a secure http web > form. Any other ideas out there? > > Thanks for all of the help. > > Christopher > > > On Sep 14, 2005, at 10:25 PM, Craig Hughes wrote: > >> On Sep 14, 2005, at 6:26 PM, Christopher P. Baker wrote: >> >> >>> I am in a strange wireless network situation here on campus. In order >>> to use the wireless network, users must authenticate with their campus >>> username and password on a secure webpage. I am using a belkin >>> wireless card to access the network (which is successful), but when the >>> authentication page comes up, I am unable to view it using the no_ssl >>> version of links. Authenticating via this webpage is the only way the >>> wireless routers will let one on the network. The only other >>> alternative is a cisco vpn client, and my web research indicates that >>> openvpn does not work well with cisco''s vpn system. >>> >>> How difficult would it be to compile links with ssl? Has anyone done >>> this? Does anyone have another idea about how to log onto a ssl http >>> page and log in? >>> >> >> Do you need full-blown links, or would wget or curl or something be >> sufficient? Or even socat with ssl support? Any of them ought to be >> possible in theory, if you compile openssl and then turn on the required >> ssl options (probably by modifying the makefile for call configure with >> different options). >> >> C >> >> >> >> >> ------------------------------------------------------- >> SF.Net email is sponsored by: >> Tame your development challenges with Apache's Geronimo App >> Server.Download it for free - -and be entered to win a 42" plasma tv or >> your very >> own Sony(tm)PSP. Click here to play: http://sourceforge.net/ >> geronimo.php >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > |
From: <ba...@ho...> - 2005-09-15 19:08:48
|
an addition ... I was also able to authenticate using the following command ... openssl s_client -connect wireless.netaccess.umn.edu:443 then, i issued the appropriate POST command (see below) into the window. has anyone tried the s_client feature in the gumstix version of openssl? (still looking for an elegant way to do this :) Cheers, Christopher On Sep 15, 2005, at 12:51 PM, ba...@ho... wrote: > So I looked into several options that allowed me to log in on the > wireless network here on campus: > > ssl enabled curl and wget allow posting forms using the -d/--post- > data option. the following worked well from my laptop: > curl -d "uid=xxx" -d "upass=xxx" -d "desturl=http://www.umn.edu" -d > "ip=xxx.xxx.xxx.xxx" -d "opt=auth" https:// > wireless.netaccess.umn.edu/cgi-bin/x5.cgi? > wget --post-data="uid=xxx&upass=xxx& etc etc" https:// > wireless.netaccess.umn.edu/cgi-bin/x5.cgi? > > BUT, currently there is no (to my knowledge) version of curl with > ssl support on the gumstix. Additionally, the busybox wget doesn't > have ssl support and doesn't support the --post-data flag anyway. > > Would it be possible to compile curl-ssl for the gumstix? > > If not, that leaves me to use socat. > > Would it be possible to use socat to open up a connection to the > https server and pipe something like the following to into socat: > > --snip-- > > POST /path/script.cgi HTTP/1.0 > User-Agent: HTTPTool/1.0 > Content-Type: application/x-www-form-urlencoded > Content-Length: 32 > > home=Cosby&favorite+flavor=flies > > --snip-- > > where the information above was the information required by the > authentication server? > > If this is possible, then I need to get socat compiled with > openssl. I noticed that the socat.mk file has the --disable- > openssl . Would recompilling it without this flag yield the socat > ssl binary i need? > > This all seems like a round-about way of posting to a secure http > web form. Any other ideas out there? > > Thanks for all of the help. > > Christopher > > > On Sep 14, 2005, at 10:25 PM, Craig Hughes wrote: > > > >> On Sep 14, 2005, at 6:26 PM, Christopher P. Baker wrote: >> >> >> >> >>> I am in a strange wireless network situation here on campus. In >>> order to use the wireless network, users must authenticate with >>> their campus username and password on a secure webpage. I am >>> using a belkin wireless card to access the network (which is >>> successful), but when the authentication page comes up, I am >>> unable to view it using the no_ssl version of links. >>> Authenticating via this webpage is the only way the wireless >>> routers will let one on the network. The only other alternative >>> is a cisco vpn client, and my web research indicates that openvpn >>> does not work well with cisco''s vpn system. >>> >>> How difficult would it be to compile links with ssl? Has anyone >>> done this? Does anyone have another idea about how to log onto a >>> ssl http page and log in? >>> >>> >>> >> >> Do you need full-blown links, or would wget or curl or something >> be sufficient? Or even socat with ssl support? Any of them ought >> to be possible in theory, if you compile openssl and then turn on >> the required ssl options (probably by modifying the makefile for >> call configure with different options). >> >> C >> >> >> >> >> ------------------------------------------------------- >> SF.Net email is sponsored by: >> Tame your development challenges with Apache's Geronimo App >> Server.Download it for free - -and be entered to win a 42" plasma >> tv or your very >> own Sony(tm)PSP. Click here to play: http://sourceforge.net/ >> geronimo.php >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> > > > |
From: <ba...@ho...> - 2005-09-15 19:09:31
Attachments:
smime.p7s
|
an addition ... I was also able to authenticate using the following command ... openssl s_client -connect wireless.netaccess.umn.edu:443 then, i pasted the appropriate POST command (see below) into the window. has anyone tried the s_client feature in the gumstix version of openssl? (still looking for an elegant way to do this :) Cheers, Christopher On Sep 15, 2005, at 12:51 PM, ba...@ho... wrote: > So I looked into several options that allowed me to log in on the > wireless network here on campus: > > ssl enabled curl and wget allow posting forms using the -d/--post- > data option. the following worked well from my laptop: > curl -d "uid=xxx" -d "upass=xxx" -d "desturl=http://www.umn.edu" -d > "ip=xxx.xxx.xxx.xxx" -d "opt=auth" https:// > wireless.netaccess.umn.edu/cgi-bin/x5.cgi? > wget --post-data="uid=xxx&upass=xxx& etc etc" https:// > wireless.netaccess.umn.edu/cgi-bin/x5.cgi? > > BUT, currently there is no (to my knowledge) version of curl with > ssl support on the gumstix. Additionally, the busybox wget doesn't > have ssl support and doesn't support the --post-data flag anyway. > > Would it be possible to compile curl-ssl for the gumstix? > > If not, that leaves me to use socat. > > Would it be possible to use socat to open up a connection to the > https server and pipe something like the following to into socat: > > --snip-- > > POST /path/script.cgi HTTP/1.0 > User-Agent: HTTPTool/1.0 > Content-Type: application/x-www-form-urlencoded > Content-Length: 32 > > home=Cosby&favorite+flavor=flies > > --snip-- > > where the information above was the information required by the > authentication server? > > If this is possible, then I need to get socat compiled with > openssl. I noticed that the socat.mk file has the --disable- > openssl . Would recompilling it without this flag yield the socat > ssl binary i need? > > This all seems like a round-about way of posting to a secure http > web form. Any other ideas out there? > > Thanks for all of the help. > > Christopher > > > On Sep 14, 2005, at 10:25 PM, Craig Hughes wrote: > > >> On Sep 14, 2005, at 6:26 PM, Christopher P. Baker wrote: >> >> >> >>> I am in a strange wireless network situation here on campus. In >>> order to use the wireless network, users must authenticate with >>> their campus username and password on a secure webpage. I am >>> using a belkin wireless card to access the network (which is >>> successful), but when the authentication page comes up, I am >>> unable to view it using the no_ssl version of links. >>> Authenticating via this webpage is the only way the wireless >>> routers will let one on the network. The only other alternative >>> is a cisco vpn client, and my web research indicates that openvpn >>> does not work well with cisco''s vpn system. >>> >>> How difficult would it be to compile links with ssl? Has anyone >>> done this? Does anyone have another idea about how to log onto a >>> ssl http page and log in? >>> >>> >> >> Do you need full-blown links, or would wget or curl or something >> be sufficient? Or even socat with ssl support? Any of them ought >> to be possible in theory, if you compile openssl and then turn on >> the required ssl options (probably by modifying the makefile for >> call configure with different options). >> >> C >> >> >> >> >> ------------------------------------------------------- >> SF.Net email is sponsored by: >> Tame your development challenges with Apache's Geronimo App >> Server.Download it for free - -and be entered to win a 42" plasma >> tv or your very >> own Sony(tm)PSP. Click here to play: http://sourceforge.net/ >> geronimo.php >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > |