<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:xhtml="http://www.w3.org/1999/xhtml">
  <title>
      Printing to Lab Printers from Dorms/Home
     | Two 〈Foo〉s Walk into a 〈Bar〉</title>
  
  <updated>2007-02-14T00:00:00-05:00</updated>
  <author>
    <name>Chris Povirk</name>
    <email>beigetangerine@gmail.com</email>
    <uri>http://twofoos.org/</uri>
  </author>
  <link rel="alternate" type="application/xhtml+xml" hreflang="en" href="http://twofoos.org/content/labprinting/"/>
  <link rel="self" type="application/atom+xml" href="http://twofoos.org/content/labprinting/feed/"/>
  <rights>Copyright © 2003–2015 Chris Povirk.  All Rights Reserved.</rights>
  <id>http://twofoos.org/</id>
  <generator uri="http://twofoos.org/content/splat/" version="1.0">SPLAT</generator>
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
<entry>
    <updated>2007-02-14T00:00:00-05:00</updated>
    <summary>
            Update: Gentoo ebuild and non‐Pitt information</summary>
    <title type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">Printing to Lab Printers from Dorms/Home</div>
    </title>
    <link rel="alternate" type="application/xhtml+xml" href="http://twofoos.org/content/labprinting/#update_2007-02-14T00:00:00-05:00"/>
    <id>http://twofoos.org/content/labprinting/#update_2007-02-14T00:00:00-05:00</id>
    <category term="linux"/>
    <category term="pitt"/>
    <content type="xhtml" xml:base="http://twofoos.org/">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <strong>Gentoo ebuild and non‐Pitt information</strong>
        <div>
    <xhtml:h5>Gentoo ebuild</xhtml:h5>
    <div>
    <p>If you're using Gentoo and don't mind dealing with <a href="http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&amp;chap=5#doc_chap2">Portage overlays</a>, you can download a Gentoo ebuild and throw it in your overlay, probably under <code>net-print</code>.  Pitt users will want to set the <code>pitt</code> <span class="caps">USE</span> flag so that the ebuild will install a Pitt printer–setup script you can run to add all the campus printers easily.  The ebuild will pull in <acronym>CUPS</acronym> and Expect if necessary.  Just <code>emerge sshlpd</code> and follow the post‐install instructions for information about how to add the printers.</p>

    <ul>
      <li><a href="/resources/sshlpd-1.ebuild"><code>sshlpd-1.ebuild</code></a></li>
    </ul>
    </div>
    </div>
        <div>
    <xhtml:h4>Non‐Pitt Users</xhtml:h4>
    <div>
    <p>I was surprised to hear from someone outside of the university who found a use for <code>sshlpd</code>.  The code is designed to be fairly general, so if you need <acronym>LPD</acronym> over S<acronym>SH</acronym>, you may find the script useful.  There are, however, a couple of changes that need to be made.</p>
    <ul>
      <li>The location of <code>lpr</code> on the remote computer is hard‐coded.  You must edit <code>$REMOTE_LPR</code> in the <code>sshlpd</code> script to point to the <code>sshlpd</code> executable.  I should find a better way of doing this, but nothing immediately came to mind, so you'll need to edit the Perl script for now.</li>
      <li>The company I heard from uses <acronym>SSH</acronym> key‐based authentication, which allows <acronym>SSH</acronym> connections to be securely created without requiring the user to enter a password at each connection.  (Ideally the Pitt version would function this way, but it appears that the university has turned off key‐based authentication on the server.)  In any case, key‐based authentication makes Expect, <code>/etc/sshpassword</code>, and a little bit of Perl code unnecessary.  If you have key‐based authentication set up and want to use <code>sshlpd</code>, then you will want to install Stephen DeGabriele's <a href="/resources/keybasedauthentication.patch">patch to remove Expect password‐handling</a>.</li>
    </ul>
    </div>
    </div>
      </div>
    </content>
  </entry></feed>
