Comment 8 for bug 120363

OK. First, what do you mean by basic TLS support in ubuntu? AFAICS the bits this bug depends on are already in place, everything but backporting this patch which doesn't appear to be that much work (I'm using it locally against your current NM0.7 package in intrepid).

To answer your second question, I wrote the patches for wpasupplicant to support configuring smartcards over dbus, that was included upstream many moons ago and is in the wpasupplicant version already shipping in intrepid. The patch that I'm asking to include gives libnm-util the ability to handle the necessary configuration parameters to send to wpasupplicant; it doesn't make setting them available in the applet yet but at least makes them usable from the system-settings facility or directly settable over dbus which on its own a huge benefit and makes NM completely usable for connecting to my 802.1x protected TLS network via the private key and certificate stored in my TPM chip, which is emulated as a smartcard to the system via opencryptoki. This is specifically intended for those of us who either realize that storing private keys on the filesystem is unsafe and want to better protect our security by using cryptographic hardware storage, or those of us at organizations who have a policy that these private keys must be stored in such format, e.g. for Windows, use of the MS crypto API storage which is bound to the TPM on the laptop. Does that answer your question?