02.10.2013 Views

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Each command in <strong>the</strong> procedure, above, has a “no” <strong>for</strong>m of <strong>the</strong> command. There<strong>for</strong>e, you have several<br />

options <strong>for</strong> disabling email to a particular recipient, although each has its own ramifications:<br />

• Using <strong>the</strong> no enable command stops messaging to <strong>the</strong> selected recipient, but does not remove <strong>the</strong> rest<br />

of <strong>the</strong> server configuration.<br />

• Using <strong>the</strong> no encrypt command stops encryption of FTMS emails to a selected server (recipient).<br />

• Using <strong>the</strong> no keyadd public_key command removes <strong>the</strong> association of a particular encryption key from<br />

a selected recipient.<br />

• Using <strong>the</strong> no recipient email address command removes <strong>the</strong> recipient from <strong>the</strong> server configuration,<br />

but <strong>the</strong> rest of <strong>the</strong> configuration remains so that you can enter a new recipient <strong>for</strong> <strong>the</strong> server.<br />

• Using <strong>the</strong> no server name from <strong>the</strong> (conf-callhome) prompt removes <strong>the</strong> server configuration,<br />

including <strong>the</strong> associated recipient. The one exception is <strong>the</strong> <strong>Force10</strong> server, which you cannot remove,<br />

but you can remove or modify <strong>the</strong> recipient and o<strong>the</strong>r settings.<br />

Using <strong>the</strong> keyadd command<br />

You have a choice of sending FTSA messages to individual email addresses in clear text or with<br />

public-key/private key encryption (PGP 5 compatible).<br />

To encrypt FTSA messages sent to <strong>Force10</strong> TAC, you simply execute <strong>the</strong> encrypt command, which causes<br />

a public key to be automatically installed on your SMTP server to provide and initiate that encryption.<br />

To encrypt messages to o<strong>the</strong>r email addresses that you might set up:<br />

1. Use a PGP 5-compatible program such as PGP or GnuPG to generate <strong>the</strong> public and private keys <strong>for</strong> a<br />

specific recipient. The user name that you enter in <strong>the</strong> program should be <strong>the</strong> one that you will use as<br />

<strong>the</strong> name value in <strong>the</strong> server command.<br />

2. Export <strong>the</strong> public key into a file.<br />

3. Upload <strong>the</strong> file into <strong>the</strong> switch flash memory (see <strong>the</strong> copy command in <strong>the</strong> <strong>FTOS</strong> Command<br />

Reference) or o<strong>the</strong>r local device.<br />

4. Select <strong>the</strong> key with <strong>the</strong> keyadd public_key command, where public_key is <strong>the</strong> filename of <strong>the</strong> key file<br />

that you have uploaded to <strong>the</strong> switch. For example: keyadd flash://mykey.gpg.<br />

To decrypt messages, copy <strong>the</strong> message into a file (<strong>for</strong> example “message1.pgp”) on <strong>the</strong> machine that has<br />

your private key, and enter <strong>the</strong> command that your encryption program uses to decrypt messages, such as<br />

“pgp message1.pgp”.<br />

Note: When you disable FTSA (no call-home command), or when you reload <strong>the</strong> switch, all recipient<br />

associations to <strong>the</strong>ir key files are erased.<br />

<strong>FTOS</strong> <strong>Configuration</strong> <strong>Guide</strong>, version 7.7.1.0 659

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!