trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: December 2014

Re: [trinity-users] Re: WEP connection problem

From: "Timothy Pearson" <kb9vqf@...>
Date: Mon, 22 Dec 2014 16:19:57 -0600
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224

> On 19 December 2014 at 22:07, Robert Peters <robertpeters9@...>
> wrote:
>> Hello,
>> My Lubuntu installation has been able to connect to a network secured
>> with WPA2 and to another with WEP.  My TDE installation, from the
>> recent Exegnu live CD, can connect to the same WPA2 network but not to
>> the WEP one - the authentication fails.  Right now the WEP network is
>> the only one available to me, and I hope to be able to use it to
>> upgrade TDE.   Does the following info suggest anything?
> <snip>
>
> Ok, looks like no solution for this one.  I've thought of 3 ways around
> it:
> - (using Lubuntu) manually fetch network-manager-tde and all its
> dependencies and install them in my TDE installation, in hopes of
> using it to make the connection.
> - try to find a wired connection or a network that uses WPA.
> - get the Ubuntu live CD, which looks more current than the Debian one
> that I installed from.
> Q: what is the effective difference between using the Debian and Ubuntu
> distros?
>
> Robert

Off the top of my head Ubuntu ships with non-free firmware by default and
allows insecure operations (such as using WEP--WEP is practically useless
and provides no real protection) by default.  Debian has a more privacy-
and security-conscious stance, and does not ship non-free firmware by
default among other restrictions.

Personally I prefer the Debian approach, but that is due to my years of
experience with Linux and my preference to know of potential security
problems.  Most users (including myself when I was just getting started so
long ago) instead find this frustrating and spend long hours with Google
trying to figure out why things are not working. ;-)

Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iFYEARELAAYFAlSYmQ0ACgkQLaxZSoRZrGGKHQDeOiyDZ8nk5sR5W9hSkq+ivcv4
/DY6T+tkUWT+zADfRGsGaJ4hoMv64EXkQfIrCf+nAMP/7VmMUXyBsw==
=yMEL
-----END PGP SIGNATURE-----