Remove lpoptions parsing code
A destination's lpoptions are stored by CUPS in the |options| field. Therefore, the existing manual parsing of the lpoptions files is unnecessary and dangerous as it exposes a surface through which untrusted inputs can be read. Additionally, the existing code assumes that the lpoptions files' locations are perpetually static, while the CUPS programming manual makes no guarantees about them. Bug: 466717 Change-Id: I655716af573ba3e58656eb01e477614384af7e51 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2238955Reviewed-by:Sean Kau <skau@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Commit-Queue: Daniel Hosseinian <dhoss@chromium.org> Cr-Commit-Position: refs/heads/master@{#779495}
Showing
Please register or sign in to comment