Cache filenames are (still) too long for ecryptfs
Bug #545197 reported by
Brad Crittenden
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lazr.restfulclient |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
ecryptfs has a ~150 character file path limit. The file paths generated can be much longer than that causing an exception when saving to the cache.
In lazr.restfulclient the 'safename' method was replicated and changed to limit the length to 149 characters. Unfortunately httplib2 later prepends the cachedir name to the truncated key. The cachedir can easily be more than 50 characters and pushes the file path to well beyond the limits.
Here is a traceback:
http://
summary: |
- Cache file paths are too long for encryptfs + Cache file paths are too long for ecryptfs |
Changed in lazr.restfulclient: | |
status: | New → Fix Released |
To post a comment you must log in.
This is the revenge of bug 512832.