1. Disallowing root logins over ssh is fine, but don't they even allow su or sudo? In fact, you should be using those even if you're logging in locally.

Yes, absolutely. But I'm looking to grab a giant list of users from our 90-some *nix boxes. I could use a client-server design, but decided it'd be just as easy to cat /etc/passwd over a (non-privileged) ssh connection and parse the return results on whatever machine the script is being run from.

Make more sense? I'm avoiding Unix::PasswdFile becuase it requires root privileges to use, and I don't want the script to be run as root.

-s.

In reply to Re: Re: SCALAR output instead of attribute name. by sschneid
in thread SCALAR output instead of attribute name. by sschneid

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.