Server seemingly randomly chooses between multiple certificates for IPPS
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- networking, security
Research direction
Reproduce the issue by sending successive IPPS jobs from CUPS and inspect /var/snap/ghostscript-printer-app/common/cups/ssl, including the certificates and keys for the three reported names. Compare which certificate the server presents on each connection and determine the intended certificate-selection behavior. Done means the certificate choice is no longer unexpectedly inconsistent across successive jobs.
Written by the indexing model from the issue text.
Description
When printing to a ghostscript-printer-app server via IPPS from CUPS, the server seems to use one of three common names for the certificate:
- The mDNS hostname (
print.local) - The DNS hostname (
print.intra.my.domain) - The IPv6 ULA (
fd11:367d:c329:80:****:**ff:fe**:****)
It seems to choose randomly between the three, even for jobs sent from the same client shortly after each other./var/snap/ghostscript-printer-app/common/cups/sslcontains different certificates and keys for all three; even after deleting these, it still seems to choose one of the three hostnames at random and generates new certificates as they are used.
This means that only the first print job from each client will reliably work - on subsequent jobs, if a different certificate is sent, the client won't trust the certificate as it is different from the one sent with the first job.
I have worked around this by manually issuing a single certificate that is valid for all three hostnames and symlinking it to all three hostnames in /var/snap/ghostscript-printer-app/common/cups/ssl, but this surely isn't intended behaviour.
- Dominant language
- PostScript
- Stars
- 44
- Forks
- 26
- Avg merge
- 9h 17m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenPrinting/ghostscript-printer-app
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
OpenPrinting/ghostscript-printer-app#25 · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
OpenPrinting/ghostscript-printer-app#21 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
OpenPrinting/ghostscript-printer-app#15 · 6 comments ·
All issues in OpenPrinting/ghostscript-printer-app
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/symphony#91 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
windows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ocaml-multicore/eio#991 · 1 comment ·
Maintainers usually reply within 1 day
-
pi: setup after uninstall picks port 8788, because its port check fails on TIME_WAITPossibly taken @vz-ibm claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
rossoctl/context-guru#1232 ·
Maintainers usually reply within 1 day