Some of the authentication schemes for WPA/WPA2 Enterprise (e.g.
PEAP,TLS) are intended to operate with a CA certificate.  The
authentication dialog box has a CA Certificate entry for this.  We can
click on it to find the required CA certificate file (it's not found
automatically).

Clicking to choose the file, the Choose A CA Certificate File dialog
box opens up to the user's home directory by default, as if the user
is supposed to have obtained the CA cert from somewhere and saved it
among their files. Is this the normally expected behaviour?  I would
have thought it would be more common for networks to use the normal
public certificates of known CAs, such as those listed in
/etc/ssl/certs/ or /usr/share/ca-certificates/mozilla/. (For instance
at our institution we're instructed to select Thawte).  By way of
comparison, the Windows WPA client used here lists all the available
CAs as part of the user interface (rather than asking for a file to be
located).

Would you consider having the Choose A CA Certificate File dialog
point to, say, /etc/ssl/certs/, by default rather than the user's home
directory?  This would make it easier for users to see what to look
for, and thereby make it less likely that they'll click on "ignore" in
regards to the CA certificate, only to wonder why no connection is
being made.

Thanks,
Drew

Hi.

I put our own CA certs into
/usr/local/share/ca-certificates/domain.pl/something.pem
which then appears automagically in the /etc/ssl/certs/
(after running update-ca-certificates)
and everytime somebody (re-)configures VPN or WiFI, or other services,
always asks me, "Hey, where is this directory with certificatates?"

Makeing /etc/ssl/certs a default directory when opening file selection dialog,
will make it lot easier, and actually lot more secure (so users will not skip
this searching and ignore any warnings).

Thanks.