From: samba-bugs@samba.org
To: cifs-qa@samba.org
Subject: [Bug 14506] New: cifs mount with missing krb5 key should give better error message
Date: Mon, 21 Sep 2020 09:57:04 +0000 [thread overview]
Message-ID: <bug-14506-10630@https.bugzilla.samba.org/> (raw)
https://bugzilla.samba.org/show_bug.cgi?id=14506
Bug ID: 14506
Summary: cifs mount with missing krb5 key should give better
error message
Product: CifsVFS
Version: 5.x
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: user space tools
Assignee: jlayton@samba.org
Reporter: bjacke@samba.org
QA Contact: cifs-qa@samba.org
Target Milestone: ---
when trying to mount a cifs share with sec=krb5 but with missing krb5 key, then
the mount command returns:
mount error(2): No such file or directory
This error message does not really help most of the users, I think.
If there is a sec=krb5 cifs mount with an *expired* key and you try to access
the mount point, the error message is better:
ls: Öffnen von Verzeichnis '.' nicht möglich: Der notwendige Schlüssel ist
nicht verfügbar
(in English like "opening directory "." not possible: the required key is not
availbale").
A similar message would be good at mount time if the required key is not
available.
--
You are receiving this mail because:
You are the QA Contact for the bug.
reply other threads:[~2020-09-21 9:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-14506-10630@https.bugzilla.samba.org/ \
--to=samba-bugs@samba.org \
--cc=cifs-qa@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).