[OpenAFS] OpenAFS client 1.7.201 and later triggers printing of smiley faces on all printers shared via Samba

[Jeffrey Altman]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig4742DE0D66D87C5764937339
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 2/7/2012 9:20 AM, Bo Nygaard Bai wrote:
> We have observed that windows clients running an installation of the
> OpenAFS client version 1.7.201 and later will, unknown to the user,
> print garbage on all our printers. Every time a user opens/refreshes th=
e
> Samba share exporting the printers, each available printer will print 2=

> pages each containing a single line of output:
>=20
> ,\ =E2=98=BA=E2=98=BA

How is this data arriving at the printers?   You say later that the
Windows Printer Spooler is disabled so there must be a direct connection
from some application to the printers.

Use SysInternals Process Monitor and WireShark to track the source of
the data being written to the process that is doing so.

In 1.7.2 the network provider interface, AFSRDFSProvider.dll, properly
fails a query for printers in the \\AFS name space.  It reports that
there are none instead of listing the file shares.

> In case the above UTF-8 does not survive the mail system:
>=20
> <komma><backslash><space><smileyface><smileyface>
>=20
> Just viewing the share exporting the printers will trigger this.

OpenAFS doesn't browse or otherwise interact with printers so it must be
an application process doing so in response to a network provider browse
request using the WNet API set.

> We only see this when the OpenAFS Client Service is running and only
> after version 1.7.201. It even happens when the windows Print Spooler
> service is stopped but AFS is running.

If OpenAFS is halted the AFSRDFSProvider will report "not connected" to
all queries.

> Has anybody else seen this or have an explanation?

I have not.

> Should I file a bug report on this?

With whom?  That is the question.  Since the problem occurs with Samba
shared printers and not Microsoft Windows shared printers or Apple
Bonjour shared printers, perhaps its a bug in Samba.





--------------enig4742DE0D66D87C5764937339
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iQEcBAEBAgAGBQJPMV1GAAoJENxm1CNJffh4REkH/jEhzIgBmrphLIOrF6f4NlZh
ilrTQggrnjdLSkCrG+aXtdzi0Bd6FJb9Fy+gCgCCa9zSWIlSWqvS/cfOtcTt10h5
TrfsCfIvj5w3iGDifMHCKBZDBTw/f15D9awJiHCsPbnDClKrAZZ+Lme8k5KTHEps
bWn41SOkxxQSmZepQa8PtnQ7CP1PzXz7GubTXXzpqT9o0m5ZJT1nhgB3gjXMtG4F
a37ARf976MFA5hnH4cCC/u4981Z6ZXNPxseTMNacE9z3xx9RCaHx+Q2QB4l1n9ZN
JP/dtOAng9LtpVn7jwaVLQSbA1efaLgGo0zElTY+HkkPjB7y6ENjl6wn74tvrEA=
=H1ZT
-----END PGP SIGNATURE-----

--------------enig4742DE0D66D87C5764937339--