Bug 35068 - cups-printers.py doesn't remove printer information from Samba registry
cups-printers.py doesn't remove printer information from Samba registry
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Printserver
UCS 3.2
Other Linux
: P5 normal (vote)
: UCS 3.2-x
Assigned To: UCS maintainers
:
Depends on:
Blocks: 55492
  Show dependency treegraph
 
Reported: 2014-06-05 13:55 CEST by Arvid Requate
Modified: 2022-12-13 10:31 CET (History)
2 users (show)

See Also:
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:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2014-06-05 13:55:08 CEST
Samba and Windows clients communicate information about printers via the registry on the Samba server. This information can be retrieved from the Samba server remotely via regedt32 orlocally via this samba shell command:

net registry enumerate_recursive  'HKLM\Software\Microsoft\Windows NT\CurrentVersion\Print'

When printers are deleted via UMC this information is not cleaned up. This may potentially lead to configuration-issues when a new printer is created under the name of a previously deleted one. E.g. the name of the windows driver assigned for client side rendering may still be one for a perviously used printer hardware.

If this issues like this occur and are irritating to customers, we may remove the printer specific registry information from samba in the delete handler of the listener module cups-printers.py by something like this:

'net registry deletekey_recursive "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Print\Printers\%s"' % (printername,)
Comment 1 Stefan Gohmann univentionstaff 2017-06-16 20:40:30 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 2 Stefan Gohmann univentionstaff 2017-08-08 07:11:04 CEST
This issue has been filed against UCS 3.2.

UCS 3.2 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.