<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Quick_reference :: Tag :: JP&#39;s Domain</title>
    <link>https://www.jpsdomain.org/tags/quick_reference/index.html</link>
    <description></description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="https://www.jpsdomain.org/tags/quick_reference/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>GNATBox Firewall Installation Quick Reference</title>
      <link>https://www.jpsdomain.org/infosec/gnatbox/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://www.jpsdomain.org/infosec/gnatbox/index.html</guid>
      <description>Obsolete Content This content is obsolete, but I am leaving it here as a historical reference.&#xA;Introduction This is a quick reference guide for installing the free GNATBox Light firewall. GNATBox Light is a complete hardened, stateful, BSD-based firewall that fits on a single floppy disk (how cool is that?). See below for references. You can download a Word document with some sample Avery 5196 diskette labels at http://www.jpsdomain.org/public/ /GNATBox_Diskette_Labels.doc. Also check out my Home Networking diagram and explanation at http://www.jpsdomain.org/infosec/home_networks.html.</description>
    </item>
    <item>
      <title>POSIX Redirection</title>
      <link>https://www.jpsdomain.org/windows/redirection/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://www.jpsdomain.org/windows/redirection/index.html</guid>
      <description>Originally written for and copyright by Information Security Magazine, February 2002 &#34; Windows Security Scripting.&#34;&#xA;Note: Under DOS &amp; Win9x/ME some of the simple STDOUT redirection and pipes work, but none of the advanced STDERR or multiple command methods are supported.&#xA;IO Redirection in Windows NT, 2000, XP, UNIX (sh, bash and variants) File Descriptors FD Description 1 STDOUT 2 STDERR 3+ Additional files as opened by the process Redirection Command Description cmd1 | cmd1 Pipe STDOUT of cmd1 into STDIN of cmd2 \&gt; file Direct STDOUT to file, overwriting existing contents \&gt;\&gt; file Direct STDOUT to file, appending to existing contents `&gt; file` 2\&gt; file Direct STDERR to file, overwriting existing contents 2\&gt;\&gt; file Direct STDERR to file, appending to existing contents \&lt; file Get STDIN from file 2\&gt;&amp;1 Direct STDERR to the same place as STDOUT \&gt;&amp; file Direct both STDOUT and STDERR to file 2\&gt;&amp; Duplicate STDOUT to STDERR echo &#39;foo&#39; \&gt;&amp;2 Send output to STDERR instead of STDOUT Notes: Numbered file descriptions above may be used arbitrarily. noclobber is a UNIX setting that prevents overwriting (clobbering) existing files by redirection. UNIX /dev/null is equivalent to Windows NUL. Windows NUL is not case sensitive. ^ is the meta-character escape in DOS/Windows, so it may sometimes be necessary to use ^| (e.g. when using egrep in a batch file). You may use ^^ for a literal ^. Examples: Command Description dir c:\*.* &gt; myls.txt Redirect output of ls into myls.txt, overwriting or creating myls.txt if necessary dir c:\winnt\*.* &gt;&gt; myls.txt Append more output of ls into myls.txt noisy_cmd &gt; NUL Make STDOUT output from noisy_cmd go away noisy_cmd 2&gt; NUL Make STDERR output from noisy_cmd go away noisy_cmd &gt; NUL 2&gt;&amp;1 Make ALL output from noisy_cmd go away noisy_cmd 2&gt; NUL 1&gt;&amp;2 Make ALL output from noisy_cmd go away noisy_cmd | more Pipe noisy_cmd STDOUT into more (or less or whatever) noisy_cmd 2&gt;&amp;1 | more Pipe noisy_cmd STDOUT and STDERR into more (this is great for those “net” commands that scroll off the screen when you try to get help) echo some message 1&gt;&amp;2 Use the echo command to send output to STDERR (it usually goes to STDOUT). Running Multiple Commands in Windows NT, 2000, UNIX (sh, bash and variants) Use parentheses to nest as needed.</description>
    </item>
  </channel>
</rss>