| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
This means we store/retrieve "http://www.gnome.org/" instead of
"http://www.gnome.org/login/". User+passwords are site-wide as long as the form
elements match. This also makes migrated gecko passwords work.
Bug #613065
|
| |
|
|
|
|
|
| |
Make sure we don't confuse form passwords with HTTP auth passwords. And also
check that username is not empty (at least that). Sometimes decryption fails
(not even nss tools work) and we get empty usernames. As you can see, we are
assuming here that usernames are always mandatory but passwords might not be.
|
| |
|
|
|
|
|
|
| |
Password form fields are marked with a *, but this * was not removed when
storing the field name so this led to all the passwords field names to be
migrated with the leading *.
Bug #608687
|
| |
|
|
| |
_ephy_profile_query_form_auth_data is async, doesn't return anything.
|
| |
|
|
|
|
| |
Realms where exported as "realm)" because of a missing -1.
Bug #608687
|
| |
|
|
|
| |
SoupURI creation may fail for invalid URIs, and we would crash trying
to work with the NULL pointers.
|
| |
|
|
|
| |
This is used to make all policy regarding what and how we save data be
in one place.
|
| |
|
|
|
| |
Otherwise we need to query keyring all the time to figure out if we
have to prefill forms.
|
| |
|
|
|
| |
We store the login/password pairs used in forms in the keyring, like
the HTTP auth data.
|
|
|
We'll use them from embed/ for form password saving, and embed/ can't
use code from src/
|
