Univention Bugzilla – Full Text Bug Listing |
Summary: | Uploading a printer driver with missing files leads to an "access denied" message | ||
---|---|---|---|
Product: | UCS | Reporter: | Janis Meybohm <meybohm> |
Component: | Samba4 | Assignee: | Felix Botner <botner> |
Status: | CLOSED FIXED | QA Contact: | Arvid Requate <requate> |
Severity: | normal | ||
Priority: | P5 | CC: | gohmann, petersen, requate, walkenhorst |
Version: | UCS 3.1 | ||
Target Milestone: | UCS 3.2-3-errata | ||
Hardware: | Other | ||
OS: | Linux | ||
See Also: | https://forge.univention.org/bugzilla/show_bug.cgi?id=38172 | ||
What kind of report is it?: | --- | What type of bug is this?: | --- |
Who will be affected by this bug?: | --- | How will those affected feel about the bug?: | --- |
User Pain: | Enterprise Customer affected?: | ||
School Customer affected?: | ISV affected?: | ||
Waiting Support: | Flags outvoted (downgraded) after PO Review: | ||
Ticket number: | Bug group (optional): | ||
Max CVSS v3 score: | |||
Bug Depends on: | |||
Bug Blocks: | 36216 | ||
Attachments: | The x86 version of this driver is broken |
Description
Janis Meybohm
2013-10-01 10:46:55 CEST
Seen again at 2014032021007797 Ok, one idea would be to diff two network traces from an upload of this driver, one to a native Windows System and the other to a Samba(4?only?) DC and spot the difference in server response that triggers different Client GUI actions ("Choose file for x86 driver" dialog vs. "access denied" message). Trying to upload a broken printdriver (e.g. DriverFile missing in inf file) on a windows dc results in WERR_APP_INIT_FAILURE. With samba as dc, WERR_ACCESS_DENIED is returned. move_driver_file_to_download_area() in source3/printing/nt_printing.c now returns the werror() of the return nt_status from the copy_file (which fails for the broken driver). With samba i get the following error on the client when trying to install the broken driver: Ein Treiber Kyocera Classic Universaldriver, Typ 3 - Benutzermodus, x86 konnte nicht installiert werden. Der Vorgang konnte nicht abgeschlossen werden (Fehler 0x00000002). With a windows ad (w2k8r2en): Ein Treiber Kyocera Classic Universaldriver, Typ 3 - Benutzermodus, x86 konnte nicht installiert werden. Der Vorgang konnte nicht abgeschlossen werden (Fehler 0x0000023f). (In reply to Janis Meybohm from comment #0) > Reproducing this process on a Windows 2008 R2 printserver leads to a "Choose > file for x86 driver" dialog instead of "access denied" so I assume the > behaviour of samba is not correct in this place. I never got a "Choose file for ..." dialog. YAML: 2014-09-04-samba.yaml 3.2-0-0-ucs/2\:4.1.0-1-errata3.2-3/97_bug32771_broken_printdriver_error_code_fix.patch 4.0-0-0-ucs/2\:4.2.0~alpha1-2/97_bug32771_broken_printdriver_error_code_fix.patch Ok, looks good. 0x0000023f is WERR_APP_INIT_FAILURE, which is not very helpful, so I guess returning the real underlying error code (WERR_BADFILE) is better. Advisory is also Ok. |