Yes unbreakable encryption is clearly known to all cryptographers like you said: problem is if you decide to make it end to end in the application layer say by negotiating the key using the Diffie and Hellman algorithm, you may have to update so many of the existing applications. Take for instance the web; 1.you launch browser.sh or browser.exe or whatever has been configured to start a browser. the browser blocks or waits for a connection request. 2.you type http//:linux.or.ug and the browser parses it and does some error checking. 3.browser invokes TCP/IP (which maybe an insecure protocol) and issues a UDP connection request to port 53 of your configured DNS to resolve linux.or.ug (recall this is a UDP connection, if it times out, another one is sent, if the name can't be resolved at that DNS, another request is made to a second level DNS, etc) 4.assume we are successful and our browser gets the correct IP, it then tries to make a TCP connection to port 80 of that IP (if its told only secure connections are allowed, it then tries 443) 5.if connection successful, it issues HTTP GET index.jsp and a home page is returned then it may issue HTTP PUT to submit form contents... 6. sending mail works the same except that this time in step 2, DNS returns the MX record and the connection is made to SMTP port 25 or any of the other secure mail ports.
Securing step 1 can make use of sys admins and some authentication protocols like Kerberos which is open source though has some issues with key storage; Securing step 2 is programmer dependent (and some of those folks may not be trusted); Securing step 3 is harder since UDP has no concept of connections but DNSsec tries to secure this step; Securing step 4 without the PKI is harder; Securing Step 5 may not be needed, but with active eavesdroppers running NICs in promiscuous mode, you will have to encrypt. Things become even harder when you are using a NAT box and NAT needs to extract and examine the IP header which has already been encrypted by IPsec > Yet one thing has remained clear, through all the techniques which have > come and gone: End-to-end encryption is necessary for good security, or > even for acceptable security. If you trust the inherent link encryption, > you are doing something wrong, right? :) > > I could design an unbreakable encryption, right here in this message. > Let's > say you want to transmit 4GB of data. What you do is create a 4GB file of > random data. Truly random data, mind; measurement data of radioactive > decay > will suffice. Anyway, collect 4GB worth of this. Then have one copy of > this > at the origin and one at the destination. Then you XOR your sensitive data > with the garbage file and send it to the destination, where you XOR again > to get the original data, and then you shred and destroy every copy of the > garbage file. > > This system is somewhat impractical, but it is totally unbreakable, given > the secure transport and storage of the garbage file. If you share a key > through a secure channel, use that key only once, and then throw it away > in > a secure manner, the encryption is pretty darn secure. Every security > system should strive to be designed like this, yet many systems are not. > The first thing one does when assessing the security of a system is to see > where it deviates from this ideal, because then you see where the > weaknesses are. > > On 31 July 2012 18:54, <[email protected]> wrote: > >> things happen all the time, there was a time GSM was supposed to be the >> real buzz, but later on we were onto things like CDMA, then i hear 3G, >> 4G, >> 5G, etc, then WAP, and within a short time WAP2..... >> Today you see ECC, but does ECC in these gadgets, offer a better >> solution? >> Does a legal binding in some countries that eavesdropping on mobile >> phone >> channels is illegal:( assuming a null pointer to -> the revisions in >> PATRIOT Act, Identity Theft Enforcement and Restitution Act, etc ) offer >> any solutions? >> :) >> >> >> >> > That *should* be comforting, but it really isn't. Hearing someone >> advising >> > to avoid telnet and FTP is like hearing someone advising to avoid >> > trepanning. (Trepanning is an ancient "medical" procedure in which you >> use >> > a stone drill or a hammer and chisel to make a hole in the cranium to >> > release evil spirits.) Telnet and FTP is as good as ancient, and if a >> web >> > host uses FTP as the primary file transfer method then that web host >> > should >> > be avoided at all costs, since they apparently know nothing about >> security >> > and only the proverbial God knows what other idiotic things they to >> behind >> > the curtains. >> > >> > On 31 July 2012 16:53, <[email protected]> wrote: >> > >> >> :) Well, the good thing is that those guys often just try to cut >> corners >> >> but are always told: PPTP does the authentication in clear text, then >> >> secures the channel, you need to change: L2F is not secure for your >> >> tunnel, you need to change, L2TP is better, but in combination with >> >> IPSec, >> >> you need to update, try to minimize or even totally disable Telnet, >> FTP, >> >> and switch to SSH, make use of IDS/IPS tapping before and after the >> >> firewall, try to disable ICMP traffic, etc etc. To your surprise, you >> >> find >> >> different things in the corporate. >> >> >> >> >> >> > And we all know how much corporate costumes like to cut corners in >> all >> >> > departments they find foreign and incomprehensible. :) >> >> > >> >> > On 31 July 2012 16:11, <[email protected]> >> wrote: >> >> > >> >> >> Probably not so as far as security is concerned in low end >> markets, >> >> but >> >> >> in >> >> >> high end markets, the implementations can get really strict. :) >> >> >> >> >> >> >> >> >> >> >> >> > Well, it seems as though I will not have to crack AES by itself, >> >> eh? >> >> >> :) >> >> >> > >> >> >> > On 31 July 2012 15:59, <[email protected]> >> >> wrote: >> >> >> > >> >> >> >> :) WPA2 is based on AES, but with the ability to evolve in case >> >> >> >> weaknesses >> >> >> >> in the algorithm are found. AES by itself is still strong and i >> >> don't >> >> >> >> think you can crack it. The implementation of AES in different >> >> >> gadgets >> >> >> >> is >> >> >> >> where the exploits come in. Also issues to do with using key >> >> lengths >> >> >> >> longer than "the gov't" can crack make it weak, i think. >> >> >> >> >> >> >> >> >> >> >> >> > Um, no. This thread is about WPA2E, right? I quote: >> >> >> >> > >> >> >> >> > ChapCrack can take captured network traffic that contains a >> >> >> MS-CHAPv2 >> >> >> >> >> network handshake (PPTP VPN or WPA2 Enterprise handshake) >> and >> >> >> reduce >> >> >> >> the >> >> >> >> >> handshake's security to a single DES (Data Encryption >> Standard) >> >> >> key. >> >> >> >> > >> >> >> >> > >> >> >> >> > On 31 July 2012 15:40, <[email protected]> >> >> >> wrote: >> >> >> >> > >> >> >> >> >> Well, there seems to be a mix up here: we are discussing AES >> >> >> >> (Rijndael) >> >> >> >> >> not DES :) >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > Of course brute force will work. DES is fairly >> non-intensive, >> >> as >> >> >> >> far >> >> >> >> >> as >> >> >> >> >> > encryptions go. Moreover, using FPGAs to build dedicated >> DES >> >> >> >> cracking >> >> >> >> >> > machines is both feasible and relatively cheap. And, it >> has >> >> been >> >> >> >> done. >> >> >> >> >> The >> >> >> >> >> > latest iteration of the COPACOBANA does its business in >> the >> >> span >> >> >> of >> >> >> >> >> one >> >> >> >> >> > single day. This machine was built in 2006 and cost $10000 >> at >> >> >> the >> >> >> >> >> time. I >> >> >> >> >> > would not be surprised if the cost today would be less >> than >> >> one >> >> >> >> tenth >> >> >> >> >> of >> >> >> >> >> > that. Moreover, the maximum WPA key length is 64 >> characters, >> >> >> which >> >> >> >> is >> >> >> >> >> > pathetic, especially when restricted to the ASCII keymap. >> >> >> >> >> > >> >> >> >> >> > There already exists cloud services for DES cracking :) >> and >> >> it's >> >> >> >> not >> >> >> >> >> that >> >> >> >> >> > expensive, either. I don't think trusting the cloud >> service >> >> in >> >> >> >> >> question >> >> >> >> >> is >> >> >> >> >> > much of an issue: a key is useless unless you know where >> it >> >> >> fits. >> >> >> >> >> Also, >> >> >> >> >> if >> >> >> >> >> > you submit a DES key, chances are you are the attacker and >> >> that >> >> >> you >> >> >> >> >> > couldn't care less about any breaches in security your >> >> adversary >> >> >> >> might >> >> >> >> >> > experience ;) >> >> >> >> >> > >> >> >> >> >> > On 31 July 2012 14:03, >> <[email protected] >> > >> >> >> >> wrote: >> >> >> >> >> > >> >> >> >> >> >> :) Brute Force using that approach will never work; you >> >> could >> >> >> try >> >> >> >> >> >> exploiting weaknesses in mathematical implementations of >> the >> >> >> >> >> algorithm >> >> >> >> >> >> by >> >> >> >> >> >> programmers and mathematical weaknesses in the hardware. >> >> >> >> >> >> >> >> >> >> >> >> The cloud is a good thing , and makes business sense >> (though >> >> it >> >> >> >> may >> >> >> >> >> not >> >> >> >> >> >> be >> >> >> >> >> >> so, with the Patent Department): imagine how many under >> >> >> utilized >> >> >> >> >> servers >> >> >> >> >> >> out there yet they pay licenses, support fees, admin >> >> personnel, >> >> >> >> >> utility >> >> >> >> >> >> bills, etc (on some OSs, just running one server machine >> as >> >> an >> >> >> >> >> >> authentication server, can give you authentication >> >> capability >> >> >> for >> >> >> >> >> more >> >> >> >> >> >> than 25,000 users; now imagine how many under utilized >> >> database >> >> >> >> >> servers, >> >> >> >> >> >> email servers, etc out there). A cloud solution lowers >> your >> >> TCO >> >> >> >> and >> >> >> >> >> >> gives >> >> >> >> >> >> you better ROI. :) >> >> >> >> >> >> >> >> >> >> >> >> Of course, the IT department is not impressed by the >> above, >> >> >> >> because >> >> >> >> >> they >> >> >> >> >> >> need to access the hardware (and also want to control the >> IT >> >> >> >> budget), >> >> >> >> >> >> besides they don't trust the guys in the cloud, yet they >> are >> >> >> the >> >> >> >> same >> >> >> >> >> >> guys >> >> >> >> >> >> who trust facebook, google, the ISPs, the Telcos, the >> banks, >> >> >> etc >> >> >> >> :) >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > Well, I would of course use a cloud service for that :P >> >> >> either >> >> >> >> >> that, >> >> >> >> >> >> or >> >> >> >> >> >> > one >> >> >> >> >> >> > of the clusters at our university. >> >> >> >> >> >> > >> >> >> >> >> >> > On 31 July 2012 13:30, >> >> <[email protected] >> >> > >> >> >> >> >> wrote: >> >> >> >> >> >> > >> >> >> >> >> >> >> :) Ah, cracking AES 256 and "higher", don't think you >> >> have >> >> >> >> those >> >> >> >> >> >> >> resources; probably thats for departments with serious >> >> scary >> >> >> >> >> budget >> >> >> >> >> >> >> figures. >> >> >> >> >> >> >> >> >> >> >> >> >> >> Well, for the case of WEP, when a paper detailing its >> >> >> >> weaknesses >> >> >> >> >> was >> >> >> >> >> >> >> submitted to the internet community, they brushed it >> off >> >> >> saying >> >> >> >> >> what >> >> >> >> >> >> it >> >> >> >> >> >> >> detailed was only theoretical and could never occur in >> >> >> >> practice, >> >> >> >> >> yet >> >> >> >> >> >> >> when >> >> >> >> >> >> >> WEP was finally broken; the media reported it as an >> off >> >> the >> >> >> >> shelf >> >> >> >> >> >> hack >> >> >> >> >> >> >> activity. :) >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > Well, hum. :P >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > I wonder how long it'll take until all the WPA2 >> >> Enterprise >> >> >> >> >> networks >> >> >> >> >> >> >> have >> >> >> >> >> >> >> > been secured. Why do I have to be in the middle of >> >> >> >> >> twenty-years-ago >> >> >> >> >> >> >> state >> >> >> >> >> >> >> > * >> >> >> >> >> >> >> > now*? I want to be home and do some rampant WPA2E >> >> >> cracking! >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > On 31 July 2012 12:52, >> >> >> <[email protected] >> >> >> > >> >> >> >> >> >> wrote: >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> Does your MS interpretation sound like >> >> >> >> >> >> >> >> the x-400 e mail format or the seven layer OSI >> >> standard? >> >> >> :) >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > What do you mean "despite"? :P I've regularly >> been >> >> >> using >> >> >> >> my >> >> >> >> >> own >> >> >> >> >> >> VPN >> >> >> >> >> >> >> >> since >> >> >> >> >> >> >> >> > 2007 when I had to start using a PPTP connection >> >> >> >> regularly. >> >> >> >> >> "MS" >> >> >> >> >> >> >> >> > translates >> >> >> >> >> >> >> >> > to "closed, flawed, and eventually defeated" in >> my >> >> >> book. >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > On 31 July 2012 12:27, >> >> >> >> <[email protected] >> >> >> >> > >> >> >> >> >> >> >> wrote: >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> >> :) But PPTP has always had its issues despite >> its >> >> >> being >> >> >> >> from >> >> >> >> >> >> MS, >> >> >> >> >> >> >> L2F >> >> >> >> >> >> >> >> >> from >> >> >> >> >> >> >> >> >> the other vendor, the same case, L2TP an attempt >> to >> >> >> >> combine >> >> >> >> >> the >> >> >> >> >> >> >> above >> >> >> >> >> >> >> >> >> two >> >> >> >> >> >> >> >> >> also is good when run with IPSec doing the >> >> encryption, >> >> >> >> yet >> >> >> >> >> >> IPSec >> >> >> >> >> >> >> also >> >> >> >> >> >> >> >> >> has >> >> >> >> >> >> >> >> >> its own issues. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Maybe SSL can do, save for its reliance on the >> >> >> PKI..... >> >> >> >> and >> >> >> >> >> >> some >> >> >> >> >> >> >> >> >> restrictions on key usage... >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > Well, at least PPTP with MS-CHAPv2 >> authentication >> >> >> is. >> >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> http://www.cso.com.au/article/432039/tools_released_defcon_can_crack_widely_used_pptp_encryption_under_day/ >> >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> >> > I can't say I'm very surprised. I've always >> done >> >> all >> >> >> my >> >> >> >> >> >> business >> >> >> >> >> >> >> >> >> through >> >> >> >> >> >> >> >> >> a >> >> >> >> >> >> >> >> >> > (better) VPN when on such a network, simply >> >> because >> >> >> the >> >> >> >> >> "MS" >> >> >> >> >> >> in >> >> >> >> >> >> >> >> >> > "MS-CHAPv2" >> >> >> >> >> >> >> >> >> > always made me nervous. >> >> >> >> >> >> >> >> >> > _______________________________________________ >> >> >> >> >> >> >> >> >> > The Uganda Linux User Group: >> http://linux.or.ug >> >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> >> > Send messages to this mailing list by >> addressing >> >> >> >> e-mails >> >> >> >> >> to: >> >> >> >> >> >> >> >> >> > [email protected] >> >> >> >> >> >> >> >> >> > Mailing list archives: >> >> >> >> >> >> >> http://www.mail-archive.com/[email protected]/ >> >> >> >> >> >> >> >> >> > Mailing list settings: >> >> >> >> http://kym.net/mailman/listinfo/lug >> >> >> >> >> >> >> >> >> > To unsubscribe: >> >> http://kym.net/mailman/options/lug >> >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> >> > The Uganda LUG mailing list is generously >> hosted >> >> by >> >> >> >> >> INFOCOM: >> >> >> >> >> >> >> >> >> > http://www.infocom.co.ug/ >> >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> >> > The above comments and data are owned by >> whoever >> >> >> posted >> >> >> >> >> them >> >> >> >> >> >> >> >> >> (including >> >> >> >> >> >> >> >> >> > attachments if any). The mailing list host is >> not >> >> >> >> >> responsible >> >> >> >> >> >> >> for >> >> >> >> >> >> >> >> them >> >> >> >> >> >> >> >> >> in >> >> >> >> >> >> >> >> >> > any way. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> >> >> >> >> >> >> The Uganda Linux User Group: http://linux.or.ug >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Send messages to this mailing list by addressing >> >> >> e-mails >> >> >> >> to: >> >> >> >> >> >> >> >> >> [email protected] >> >> >> >> >> >> >> >> >> Mailing list archives: >> >> >> >> >> >> >> http://www.mail-archive.com/[email protected]/ >> >> >> >> >> >> >> >> >> Mailing list settings: >> >> >> >> http://kym.net/mailman/listinfo/lug >> >> >> >> >> >> >> >> >> To unsubscribe: >> http://kym.net/mailman/options/lug >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> The Uganda LUG mailing list is generously hosted >> by >> >> >> >> INFOCOM: >> >> >> >> >> >> >> >> >> http://www.infocom.co.ug/ >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> The above comments and data are owned by whoever >> >> >> posted >> >> >> >> them >> >> >> >> >> >> >> >> (including >> >> >> >> >> >> >> >> >> attachments if any). The mailing list host is >> not >> >> >> >> >> responsible >> >> >> >> >> >> for >> >> >> >> >> >> >> >> them >> >> >> >> >> >> >> >> >> in >> >> >> >> >> >> >> >> >> any way. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > _______________________________________________ >> >> >> >> >> >> >> >> > The Uganda Linux User Group: http://linux.or.ug >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > Send messages to this mailing list by addressing >> >> >> e-mails >> >> >> >> to: >> >> >> >> >> >> >> >> > [email protected] >> >> >> >> >> >> >> >> > Mailing list archives: >> >> >> >> >> >> http://www.mail-archive.com/[email protected]/ >> >> >> >> >> >> >> >> > Mailing list settings: >> >> >> http://kym.net/mailman/listinfo/lug >> >> >> >> >> >> >> >> > To unsubscribe: >> http://kym.net/mailman/options/lug >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > The Uganda LUG mailing list is generously hosted >> by >> >> >> >> INFOCOM: >> >> >> >> >> >> >> >> > http://www.infocom.co.ug/ >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > The above comments and data are owned by whoever >> >> posted >> >> >> >> them >> >> >> >> >> >> >> >> (including >> >> >> >> >> >> >> >> > attachments if any). The mailing list host is not >> >> >> >> responsible >> >> >> >> >> >> for >> >> >> >> >> >> >> them >> >> >> >> >> >> >> >> in >> >> >> >> >> >> >> >> > any way. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> >> >> >> >> >> The Uganda Linux User Group: http://linux.or.ug >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Send messages to this mailing list by addressing >> >> e-mails >> >> >> to: >> >> >> >> >> >> >> >> [email protected] >> >> >> >> >> >> >> >> Mailing list archives: >> >> >> >> >> >> http://www.mail-archive.com/[email protected]/ >> >> >> >> >> >> >> >> Mailing list settings: >> >> >> http://kym.net/mailman/listinfo/lug >> >> >> >> >> >> >> >> To unsubscribe: http://kym.net/mailman/options/lug >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> The Uganda LUG mailing list is generously hosted by >> >> >> INFOCOM: >> >> >> >> >> >> >> >> http://www.infocom.co.ug/ >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> The above comments and data are owned by whoever >> >> posted >> >> >> them >> >> >> >> >> >> >> (including >> >> >> >> >> >> >> >> attachments if any). The mailing list host is not >> >> >> >> responsible >> >> >> >> >> for >> >> >> >> >> >> >> them >> >> >> >> >> >> >> >> in >> >> >> >> >> >> >> >> any way. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > _______________________________________________ >> >> >> >> >> >> >> > The Uganda Linux User Group: http://linux.or.ug >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > Send messages to this mailing list by addressing >> >> e-mails >> >> >> to: >> >> >> >> >> >> >> > [email protected] >> >> >> >> >> >> >> > Mailing list archives: >> >> >> >> >> http://www.mail-archive.com/[email protected]/ >> >> >> >> >> >> >> > Mailing list settings: >> >> http://kym.net/mailman/listinfo/lug >> >> >> >> >> >> >> > To unsubscribe: http://kym.net/mailman/options/lug >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > The Uganda LUG mailing list is generously hosted by >> >> >> INFOCOM: >> >> >> >> >> >> >> > http://www.infocom.co.ug/ >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > The above comments and data are owned by whoever >> posted >> >> >> them >> >> >> >> >> >> >> (including >> >> >> >> >> >> >> > attachments if any). The mailing list host is not >> >> >> responsible >> >> >> >> >> for >> >> >> >> >> >> them >> >> >> >> >> >> >> in >> >> >> >> >> >> >> > any way. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> >> >> >> >> The Uganda Linux User Group: http://linux.or.ug >> >> >> >> >> >> >> >> >> >> >> >> >> >> Send messages to this mailing list by addressing >> e-mails >> >> to: >> >> >> >> >> >> >> [email protected] >> >> >> >> >> >> >> Mailing list archives: >> >> >> >> >> http://www.mail-archive.com/[email protected]/ >> >> >> >> >> >> >> Mailing list settings: >> >> http://kym.net/mailman/listinfo/lug >> >> >> >> >> >> >> To unsubscribe: http://kym.net/mailman/options/lug >> >> >> >> >> >> >> >> >> >> >> >> >> >> The Uganda LUG mailing list is generously hosted by >> >> INFOCOM: >> >> >> >> >> >> >> http://www.infocom.co.ug/ >> >> >> >> >> >> >> >> >> >> >> >> >> >> The above comments and data are owned by whoever >> posted >> >> them >> >> >> >> >> >> (including >> >> >> >> >> >> >> attachments if any). The mailing list host is not >> >> >> responsible >> >> >> >> for >> >> >> >> >> >> them >> >> >> >> >> >> >> in >> >> >> >> >> >> >> any way. >> >> >> >> >> >> >> >> >> >> >> >> >> > _______________________________________________ >> >> >> >> >> >> > The Uganda Linux User Group: http://linux.or.ug >> >> >> >> >> >> > >> >> >> >> >> >> > Send messages to this mailing list by addressing >> e-mails >> >> to: >> >> >> >> >> >> > [email protected] >> >> >> >> >> >> > Mailing list archives: >> >> >> >> http://www.mail-archive.com/[email protected]/ >> >> >> >> >> >> > Mailing list settings: >> http://kym.net/mailman/listinfo/lug >> >> >> >> >> >> > To unsubscribe: http://kym.net/mailman/options/lug >> >> >> >> >> >> > >> >> >> >> >> >> > The Uganda LUG mailing list is generously hosted by >> >> INFOCOM: >> >> >> >> >> >> > http://www.infocom.co.ug/ >> >> >> >> >> >> > >> >> >> >> >> >> > The above comments and data are owned by whoever posted >> >> them >> >> >> >> >> >> (including >> >> >> >> >> >> > attachments if any). The mailing list host is not >> >> responsible >> >> >> >> for >> >> >> >> >> them >> >> >> >> >> >> in >> >> >> >> >> >> > any way. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> >> >> >> The Uganda Linux User Group: http://linux.or.ug >> >> >> >> >> >> >> >> >> >> >> >> Send messages to this mailing list by addressing e-mails >> to: >> >> >> >> >> >> [email protected] >> >> >> >> >> >> Mailing list archives: >> >> >> >> http://www.mail-archive.com/[email protected]/ >> >> >> >> >> >> Mailing list settings: >> http://kym.net/mailman/listinfo/lug >> >> >> >> >> >> To unsubscribe: http://kym.net/mailman/options/lug >> >> >> >> >> >> >> >> >> >> >> >> The Uganda LUG mailing list is generously hosted by >> INFOCOM: >> >> >> >> >> >> http://www.infocom.co.ug/ >> >> >> >> >> >> >> >> >> >> >> >> The above comments and data are owned by whoever posted >> them >> >> >> >> >> (including >> >> >> >> >> >> attachments if any). The mailing list host is not >> >> responsible >> >> >> for >> >> >> >> >> them >> >> >> >> >> >> in >> >> >> >> >> >> any way. >> >> >> >> >> >> >> >> >> >> >> > _______________________________________________ >> >> >> >> >> > The Uganda Linux User Group: http://linux.or.ug >> >> >> >> >> > >> >> >> >> >> > Send messages to this mailing list by addressing e-mails >> to: >> >> >> >> >> > [email protected] >> >> >> >> >> > Mailing list archives: >> >> >> http://www.mail-archive.com/[email protected]/ >> >> >> >> >> > Mailing list settings: http://kym.net/mailman/listinfo/lug >> >> >> >> >> > To unsubscribe: http://kym.net/mailman/options/lug >> >> >> >> >> > >> >> >> >> >> > The Uganda LUG mailing list is generously hosted by >> INFOCOM: >> >> >> >> >> > http://www.infocom.co.ug/ >> >> >> >> >> > >> >> >> >> >> > The above comments and data are owned by whoever posted >> them >> >> >> >> >> (including >> >> >> >> >> > attachments if any). The mailing list host is not >> responsible >> >> >> for >> >> >> >> them >> >> >> >> >> in >> >> >> >> >> > any way. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> >> >> The Uganda Linux User Group: http://linux.or.ug >> >> >> >> >> >> >> >> >> >> Send messages to this mailing list by addressing e-mails to: >> >> >> >> >> [email protected] >> >> >> >> >> Mailing list archives: >> >> >> http://www.mail-archive.com/[email protected]/ >> >> >> >> >> Mailing list settings: http://kym.net/mailman/listinfo/lug >> >> >> >> >> To unsubscribe: http://kym.net/mailman/options/lug >> >> >> >> >> >> >> >> >> >> The Uganda LUG mailing list is generously hosted by INFOCOM: >> >> >> >> >> http://www.infocom.co.ug/ >> >> >> >> >> >> >> >> >> >> The above comments and data are owned by whoever posted them >> >> >> >> (including >> >> >> >> >> attachments if any). The mailing list host is not >> responsible >> >> for >> >> >> >> them >> >> >> >> >> in >> >> >> >> >> any way. >> >> >> >> >> >> >> >> >> > _______________________________________________ >> >> >> >> > The Uganda Linux User Group: http://linux.or.ug >> >> >> >> > >> >> >> >> > Send messages to this mailing list by addressing e-mails to: >> >> >> >> > [email protected] >> >> >> >> > Mailing list archives: >> >> http://www.mail-archive.com/[email protected]/ >> >> >> >> > Mailing list settings: http://kym.net/mailman/listinfo/lug >> >> >> >> > To unsubscribe: http://kym.net/mailman/options/lug >> >> >> >> > >> >> >> >> > The Uganda LUG mailing list is generously hosted by INFOCOM: >> >> >> >> > http://www.infocom.co.ug/ >> >> >> >> > >> >> >> >> > The above comments and data are owned by whoever posted them >> >> >> >> (including >> >> >> >> > attachments if any). The mailing list host is not responsible >> >> for >> >> >> them >> >> >> >> in >> >> >> >> > any way. >> >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> >> The Uganda Linux User Group: http://linux.or.ug >> >> >> >> >> >> >> >> Send messages to this mailing list by addressing e-mails to: >> >> >> >> [email protected] >> >> >> >> Mailing list archives: >> >> http://www.mail-archive.com/[email protected]/ >> >> >> >> Mailing list settings: http://kym.net/mailman/listinfo/lug >> >> >> >> To unsubscribe: http://kym.net/mailman/options/lug >> >> >> >> >> >> >> >> The Uganda LUG mailing list is generously hosted by INFOCOM: >> >> >> >> http://www.infocom.co.ug/ >> >> >> >> >> >> >> >> The above comments and data are owned by whoever posted them >> >> >> (including >> >> >> >> attachments if any). The mailing list host is not responsible >> for >> >> >> them >> >> >> >> in >> >> >> >> any way. >> >> >> >> >> >> >> > _______________________________________________ >> >> >> > The Uganda Linux User Group: http://linux.or.ug >> >> >> > >> >> >> > Send messages to this mailing list by addressing e-mails to: >> >> >> > [email protected] >> >> >> > Mailing list archives: >> http://www.mail-archive.com/[email protected]/ >> >> >> > Mailing list settings: http://kym.net/mailman/listinfo/lug >> >> >> > To unsubscribe: http://kym.net/mailman/options/lug >> >> >> > >> >> >> > The Uganda LUG mailing list is generously hosted by INFOCOM: >> >> >> > http://www.infocom.co.ug/ >> >> >> > >> >> >> > The above comments and data are owned by whoever posted them >> >> >> (including >> >> >> > attachments if any). The mailing list host is not responsible >> for >> >> them >> >> >> in >> >> >> > any way. >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> The Uganda Linux User Group: http://linux.or.ug >> >> >> >> >> >> Send messages to this mailing list by addressing e-mails to: >> >> >> [email protected] >> >> >> Mailing list archives: >> http://www.mail-archive.com/[email protected]/ >> >> >> Mailing list settings: http://kym.net/mailman/listinfo/lug >> >> >> To unsubscribe: http://kym.net/mailman/options/lug >> >> >> >> >> >> The Uganda LUG mailing list is generously hosted by INFOCOM: >> >> >> http://www.infocom.co.ug/ >> >> >> >> >> >> The above comments and data are owned by whoever posted them >> >> (including >> >> >> attachments if any). The mailing list host is not responsible for >> >> them >> >> >> in >> >> >> any way. >> >> >> >> >> > _______________________________________________ >> >> > The Uganda Linux User Group: http://linux.or.ug >> >> > >> >> > Send messages to this mailing list by addressing e-mails to: >> >> > [email protected] >> >> > Mailing list archives: http://www.mail-archive.com/[email protected]/ >> >> > Mailing list settings: http://kym.net/mailman/listinfo/lug >> >> > To unsubscribe: http://kym.net/mailman/options/lug >> >> > >> >> > The Uganda LUG mailing list is generously hosted by INFOCOM: >> >> > http://www.infocom.co.ug/ >> >> > >> >> > The above comments and data are owned by whoever posted them >> >> (including >> >> > attachments if any). The mailing list host is not responsible for >> them >> >> in >> >> > any way. >> >> >> >> >> >> _______________________________________________ >> >> The Uganda Linux User Group: http://linux.or.ug >> >> >> >> Send messages to this mailing list by addressing e-mails to: >> >> [email protected] >> >> Mailing list archives: http://www.mail-archive.com/[email protected]/ >> >> Mailing list settings: http://kym.net/mailman/listinfo/lug >> >> To unsubscribe: http://kym.net/mailman/options/lug >> >> >> >> The Uganda LUG mailing list is generously hosted by INFOCOM: >> >> http://www.infocom.co.ug/ >> >> >> >> The above comments and data are owned by whoever posted them >> (including >> >> attachments if any). The mailing list host is not responsible for >> them >> >> in >> >> any way. >> >> >> > _______________________________________________ >> > The Uganda Linux User Group: http://linux.or.ug >> > >> > Send messages to this mailing list by addressing e-mails to: >> > [email protected] >> > Mailing list archives: http://www.mail-archive.com/[email protected]/ >> > Mailing list settings: http://kym.net/mailman/listinfo/lug >> > To unsubscribe: http://kym.net/mailman/options/lug >> > >> > The Uganda LUG mailing list is generously hosted by INFOCOM: >> > http://www.infocom.co.ug/ >> > >> > The above comments and data are owned by whoever posted them >> (including >> > attachments if any). The mailing list host is not responsible for them >> in >> > any way. >> >> >> _______________________________________________ >> The Uganda Linux User Group: http://linux.or.ug >> >> Send messages to this mailing list by addressing e-mails to: >> [email protected] >> Mailing list archives: http://www.mail-archive.com/[email protected]/ >> Mailing list settings: http://kym.net/mailman/listinfo/lug >> To unsubscribe: http://kym.net/mailman/options/lug >> >> The Uganda LUG mailing list is generously hosted by INFOCOM: >> http://www.infocom.co.ug/ >> >> The above comments and data are owned by whoever posted them (including >> attachments if any). The mailing list host is not responsible for them >> in >> any way. >> > _______________________________________________ > The Uganda Linux User Group: http://linux.or.ug > > Send messages to this mailing list by addressing e-mails to: > [email protected] > Mailing list archives: http://www.mail-archive.com/[email protected]/ > Mailing list settings: http://kym.net/mailman/listinfo/lug > To unsubscribe: http://kym.net/mailman/options/lug > > The Uganda LUG mailing list is generously hosted by INFOCOM: > http://www.infocom.co.ug/ > > The above comments and data are owned by whoever posted them (including > attachments if any). The mailing list host is not responsible for them in > any way. _______________________________________________ The Uganda Linux User Group: http://linux.or.ug Send messages to this mailing list by addressing e-mails to: [email protected] Mailing list archives: http://www.mail-archive.com/[email protected]/ Mailing list settings: http://kym.net/mailman/listinfo/lug To unsubscribe: http://kym.net/mailman/options/lug The Uganda LUG mailing list is generously hosted by INFOCOM: http://www.infocom.co.ug/ The above comments and data are owned by whoever posted them (including attachments if any). The mailing list host is not responsible for them in any way.
