Obsolete
Status Update
No update yet.
Comments
no...@gmail.com
Important addition!!!!!
The App just stopped working again and is giving me the NeedIndexError again! This
coincided with my re-addition of the superset (ancestor only) index going from status
"building" to "serving".
So, I think it might be clear what is going on:
With an index setup like this:
indexes:
- kind: Segment
ancestor: yes
- kind: Segment
ancestor: yes
properties:
- name: rev
The second index seems to be hidden by the first one, since it is a subset of the
first. Deleting the first index exposes the second one.
After deleting the first index out of index.yaml and running "appcfg.py update", a
call to "appcfg.py vacuum_indexes" outputs this:
Fetching index definitions diff.
This index is no longer defined in your index.yaml file.
ancestor: true
kind: Segment
properties: []
Are you sure you want to delete this index? (N/y/a): y
Deleting selected index definitions.
Error 500: --- begin server output ---
Server Error (500)
A server error has occured.
--- end server output ---
After this, the app works again, despite the error.
This problem only seems to be happening if an ancestor is involved.
I hope this helps.
Thanks,
Markus
The App just stopped working again and is giving me the NeedIndexError again! This
coincided with my re-addition of the superset (ancestor only) index going from status
"building" to "serving".
So, I think it might be clear what is going on:
With an index setup like this:
indexes:
- kind: Segment
ancestor: yes
- kind: Segment
ancestor: yes
properties:
- name: rev
The second index seems to be hidden by the first one, since it is a subset of the
first. Deleting the first index exposes the second one.
After deleting the first index out of index.yaml and running "appcfg.py update", a
call to "appcfg.py vacuum_indexes" outputs this:
Fetching index definitions diff.
This index is no longer defined in your index.yaml file.
ancestor: true
kind: Segment
properties: []
Are you sure you want to delete this index? (N/y/a): y
Deleting selected index definitions.
Error 500: --- begin server output ---
Server Error (500)
A server error has occured.
--- end server output ---
After this, the app works again, despite the error.
This problem only seems to be happening if an ancestor is involved.
I hope this helps.
Thanks,
Markus
Description
In addition, each password in the password history appears to use the same salt. The practice creates a number of similar single-instance problems, rather than a multi-instance problem. "Multi-Instance Security and its Application to Password-Based Cryptography,"
749. private String getSalt() {
750. long salt = getLong(LOCK_PASSWORD_SALT_KEY, 0);
751. if (salt == 0) {
752. try {
753. salt = SecureRandom.getInstance("SHA1PRNG").nextLong();
754. setLong(LOCK_PASSWORD_SALT_KEY, salt);
755. Log.v(TAG, "Initialized lock password salt");
756. } catch (NoSuchAlgorithmException e) {
757. // Throw an exception rather than storing a password we'll never be able to recover
758. throw new IllegalStateException("Couldn't get SecureRandom number", e);
759. }
760. }
761. return Long.toHexString(salt);762. }