http://bugzilla.novell.com/show_bug.cgi?id=512549 User jsmeix@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=512549#c1 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Status|ASSIGNED |NEEDINFO Info Provider| |mzugec@novell.com --- Comment #1 from Johannes Meixner <jsmeix@novell.com> 2009-06-24 00:32:55 MDT --- It is questionable if we really should implement it, see http://www.cups.org/newsgroups.php?s167+gcups.general+v186+T0+Q"authentication" ------------------------------------------------------------------------------- From: Michael R Sweet Date: 09:33 Jun 12 .. You can, but we really really don't want to encourage its use. The normal CUPS install now handles this by holding the job for authentication and Tim's GNOME stuff allows the user to provide credentials after the fact. Once we know the remote end wants a username and password (auth-info-required=username,password), the client-side code (read: GNOME and KDE print APIs) can ask the user for credentials and/or pull them from the local password store/wallet/ keychain/whatever. Let's not propagate the "one username and password for all users on a system" setup... ------------------------------------------------------------------------------- By the way: Regarding the values for username and password and all other values in a DeviceURI: Reserved characters in the values of an URI : / ? # [ ] @ ! $ & ' ( ) * + , ; = and a literal % character must be percent-encoded (% followed by two hex digits, e.g. % -> %25), see http://www.rfc-editor.org/rfc/rfc3986.txt and http://www.cups.org/newsgroups.php?s1+gcups.general+v4+T+Q"Samba+printers+bad+uri" and https://bugzilla.redhat.com/show_bug.cgi?id=507409 and http://www.cups.org/str.php?L3228 Characters that are allowed in a URI but do not have a reserved purpose are called unreserved. These include uppercase and lowercase letters, decimal digits, hyphen, period, underscore, and tilde. Michal, regarding URI syntax: Does YaST provide functions for percent-encoding and/or perhaps even for an URI syntax check? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=512549 User jsmeix@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=512549#c3 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |mzugec@novell.com --- Comment #3 from Johannes Meixner <jsmeix@novell.com> 2009-06-24 02:04:24 MDT --- What do you mean with "problem ... different syntax"? I am mainly interested in percent-encoding of the value sub-strings of an URI (e.g. values for username and password). I am not interested in percent-encoding of a whole URI. http://www.rfc-editor.org/rfc/rfc3986.txt reads: ------------------------------------------------------------------------- A URI is composed from a limited set of characters consisting of digits, letters, and a few graphic symbols. A reserved subset of those characters may be used to delimit syntax components within a URI while the remaining characters, including both the unreserved set and those reserved characters not acting as delimiters, define each component's identifying data. 2.1. Percent-Encoding A percent-encoding mechanism is used to represent a data octet in a component when that octet's corresponding character is outside the allowed set or is being used as a delimiter of, or within, the component. ------------------------------------------------------------------------- As far as I understand RFC 3986, the Example 141 in http://forgeftp.novell.com//yast/doc/SL11.1/modules/URL.html#EscapeString is plain wrong because it does percent-encoding for characters which are actually meant to be delimiters in the URI so that the resulting string in Example 141 is no longer a valid URI. Furthermore regarding http://forgeftp.novell.com//yast/doc/SL11.1/modules/URL.html "RFC 2396 (updated by RFC 2732)" is outdated, search for "3986" in http://www.rfc-editor.org/cgi-bin/rfcsearch.pl and you get --------------------------------------------------------------------- RFC3986 ... Obsoletes RFC2732, RFC2396, RFC1808, --------------------------------------------------------------------- It seems the YaST URL module needs a revision? Perhaps it is better when I implement my own percent-encoding function in yast2-printer in good compliance to RFC3986 than to incur bugs by using an partially outdated/obsoleted implementation? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=512549 User jsmeix@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=512549#c5 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX --- Comment #5 from Johannes Meixner <jsmeix@novell.com> 2009-11-13 07:31:34 MST --- I agree with Michael Sweet (see comment #1) and I will not implement it in YaST. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.