One of the things that would be useful in an access tracer is reporting not just what was accessed, butwhere it was accessed from. A basic starter for this is knowing whatfunction called you.

CPython has enough introspection faculties to give youthis information, but it's not entirely documented how todig it out. The big tool for this is the inspect module , and wecan use it to define a function:

import inspect

def getcallerinfo():    fr = inspect.currentframe()    try:         fr

Here's a question: which type of documentation is the ever-popular FAQ format?

My answer is that in practice, FAQs are a collection of tutorials; theytell you how to do various specific frequently asked operations. Thishas important implications if your primary documentation format is FAQs,because FAQs effectively have drawbacks from both sides; they're notas well organized or as comprehensive as reference documents, and theydon't give you an overall view the way a single unified tutorial does.

(That they

The problem with GNU Texinfo is not that it is a bad format fordocumentation as such. The problem is what sort of documentationgets written in GNU texinfo format.

To simplify, there are at least two forms of documentation: tutorialsand references. Where I draw the line between the two is that is thattutorial documentation is intended to be read from start to finish,while reference documentation is intended to be skimmed and skippedthrough.

Writing something as a tutorial has at least three effects that arerelevant here:

• it

So you've carefully isolated your management interfaces , making sure that packets can't leak fromone side to another because they literally can't see the other side.You're safe, right?

Well, not quite. While an attacker can't get their own packets across toyour management interface, they may still be able to trick things onyour machine into generating outgoing packets for them. There's a numberof cases:

• packets with a management origin to your management IP: this should