T h e   F i d o G a z e t t e!   Volume IV   Number VII    July, 2010
    | .----------------------. |      dr.debug: dr.debug @ filegate.net   |
    | | A monthly E-Zine     | |      bbslists: bbslists @ filegate.net   |
    | | published by Fidonet | |      articles: fidogazette @ filegate.net|
    | | to promote BBSing    | +------------------------------------------+
    | |          ____________. |                                          |
    | |         /  __          | "Anyone who has never made a mistake     |
    | |        /  /  \         |  has never tried anything new."          |
    | | WOOF! (  /|oo \        |                      Albert Einstein     |
    |  \_______\(_|  /_)       |                                          |
    |             \@/ \        |          Got Something To Say?           |
    |             .---.\    _  |              Say it in the               |
    | (jk)  _     |usb| \   \\ |           =The FidoGazette=              |
    |      / |    .___.  \   ))|                                          |
    |     /  |    /_ |  /  \// |         Editor: Janis Kracht             |
    |    |___|   // || _\   /  |         janis @ filegate . net           |
    |    .--`-. (_|(_|(____/   |         janis kracht 1:261/38            |
    |    |____| (jm)           |                                          |
     Happy 4th Of July to those in the United States, in Zone 1!    

    New and Returning Members..................................(2)
    The Old School Toolbox:
         SysOp Tools: Copping that Email fix...................(3)
    Tips and Tricks............................................(4)
    FidoGazette BBS List.......................................(6)
    IFDC FileGate File Distribution News.......................(7)
    Info (Where to Send Articles)..............................(8)
    Page i

    T h e   F i d o G a z e t t e!   Volume IV   Number VII    July, 2010


    A lot of people have left Fidonet over the years;  Many of us remember
    the size of the nodelist being such a consideration, that Coordinators
    were making sure that there wasn't any unneeded information in the
    nodelist.  It cost to send mail via phone lines in some areas back then,
    and it often made this a very expensive hobby.  
    These days, we are not so concerned with cost because of the protocols
    tcpip gives us - but tcpip (the internet) is both a blessing and a
    curse.  The Internet continues to take it's toll on our membership. 
    And yet we are still getting new applications every month. I think
    this is just what we need.  One of these days I'm going to track the
    new memberships to get some statistics (g).
    We need new blood to bring new users to our bbs systems, and we need
    new programmers to continue to build the tools we use.  That's what I'm
    hoping we can accomplish with some of these new folk.  We have networks
    that need NCs, and Regions that need RCs.  Volunteers are not always
    easy to come by. 
    So, if you know someone who needs some help getting things going, give
    them a hand.  It may be the person who writes the next speedy protocol,
    bbs program or mailer you need :)

    Page 1		
    T h e   F i d o G a z e t t e!   Volume IV   Number VII    July, 2010
    New and Returning Members
    From http://www.filegate.net/zone1/ and other mirror sites such as

    In the Works:
    Tony Napier       Region 10
    Nathan Neal       Region 14
    Sam Bright        Region 17
    John Meeks        Region 18
    Harvey Simpson    Region 18

    Page 2
    T h e   F i d o G a z e t t e!   Volume IV   Number VII    July, 2010
                      The Old School Toolbox

                     By Richard Webb, 1:116/901

             Remote Sysop Tools:  Copping That Email fix

    Again  remember  our scenario. In case you just joined us it goes like
    this.  Picture your community after the disaster, tornado, etc.  Cable
    TV and broadband internet are down for the count, generators are
    humming near residences that are so equipped, as well as near public
    institutions.  But, at one agency their internet services have been
    augmented with a machine on a beefy UPS well hardened against possible
    sources of harm.  This machine is connected to the public switched
    telephone network.

    We  mentioned  in  this  column last time some quick shuffle dance
    steps that can give this fido node's users their electronic mail
    capabilities back using an alternate gateway, and that's where we
    basically left you last time, so, on with the program (grin).

    A  lot  of  this presto change-o isn't going to work without the sysop
    being able to change some things up by remote.  To refresh your memory,
    the remote sysop needs to change up the netmgr configuration file to
    add another search mask to readdress internet email to another gateway. 
    In this space last time, we used a fictitious address of 1:290/10.1000
    for the internet email gate.  That gate which is locally operated using
    transnet or a similar tool is obviously not going to do anything,
    because there is no broadband internet connection currently.  So, we
    need to readdress this mail to a working gateway, then route it
    appropriately.  Netmgr and other such tools can easily accomplish this,
    especially if they use text files for configuration.

    Best  practice is to have the new config file already on the system,
    but with another name.  That way it's just a matter of back up the old
    one, put new one in place.  But, we need to have some security in
    place.  We don't want just anyone stumbling on this.

    It  starts  with  the  sysop's  netmail,  or  netmail from a trusted
    user.  A sysop from another local node, or a point is preferrable for
    this sort of thing, because it provides additional layers of security
    authentication warning even before the message is seen by netmgr or a
    similar tool.If links are configured properly there should be session
    and packet passwords in place between the two systems.

    First, we configure netmgr with a search mask that looks for mails from
    certain users, wild cards can be used, but should be used with care. 
    For this example, we've told netmgr to look for mail from Joe remote at
    1:290/10.2 addressed to mail room on 1:290/10.0 with a subject line of
    "password" which might be his areafix or session password.  Don't
    worry, there will be more authentication verification later on. 
    However, a different password for this function which is *not*
    one'otherwise used adds more security.

    So,  when  netmgr  sees  a  message  address to mail room on 1:290/10
    from Joe REmote at the proper address, with a subject line matching the
    agreed upon password a few things are going to happen.  First, the
    message will be saved to a specified text file, then, one or more
    semaphore files created which the batch or cmd file that manages the
    whole system can use later, or not depending on what happens next.

    For  this  little  mental  exercise we'll specify that we're running
    the registered version of netmgr.  This allows us to run an external
    program from a shell from within netmgr, and we've configured the
    actions that go with this search mask to do just that.  first, the .bat
    or .cmd process we will invoke begins a message back to Joe Remote at
    the proper address.  Then, we're going to get that authentication
    verification I mentioned earlier.

    AT this point we use either the ms dos  find  command  or  a version of
    grep or other text search tools to find specified text in the message
    which Joe REmote sent.  In the case of my system I've been known to use
    a unique character string, such as a pin number for an atm card I hold
    converted to hex.  since I used a password which is common to me as a
    point with me as the node, I want to have an extra step in there for
    the system to be doubly sure that *I and I alone sent that message.

    The text search facility we  used  generates  an  errorlevel depending
    on wehther the specified text was found.  IF it wasn't found, then the
    message back to JOe REmote tells him that it doesn't really think that
    *he* sent that message.  AT that point, it deletes the semaphore files
    that netmgr created earlier, closes the message to JOe after telling
    him that this process isn't going to happen, but he might want to have
    a look about and see if anybody's been tampering with his laptop
    lately, and exits.  NEtmgr then dutifully creates the message so the
    packer deletes it after it's scanned out.  The batch or .cmd file
    already took care of nuking the errant text file and any flag files
    netmgr created to trigger later processing.

    Had this authentication step been successful, we might  have performed
    further authentication steps if desired, or just sent a message to JOe
    remote letting him know this process would be taken care of shortly,
    and what was expected to be done.  We might have even created the batch
    file or .cmd on the fly from parts of the text of JOe's message, user's
    choice here.  With the right tools this can be fairly easy to

    If  the  link  which  triggers the configuration and control file
    switcharoo is properly configured utilizing session and packet
    passwording at this stage we've four levels of authenticity
    verification.  To recap, we've the session password correct, or no
    session would have taken place.  Then, the packet containing the action
    message wouldn't have been processed if the packet passwords were
    incorrect.  At the third level, netmgr or a similar tool would not have
    acted upon it had the password in the subject line been incorrect. 
    Finally, had the embedded text string in the message body been absent
    or incorrect the process would have aborted, with or without
    notification of the sender, sysop's choice here.

    If  one  feels  that  he  or  she must have a fifth layer of
    verification the sender's last four digits of the good ol' social
    security number, last four of voice number or some other character
    string can be searched for in the message body, but chances are good if
    the process has made it this far all the right pieces are in place. 
    But, be sure you use authenticity verification steps which can be
    verified, and preferrably only known to the person authorized to
    perform such functions.  For this reason I'd avoid publicly available
    information such as the authorized person's birthday, social security
    number, etc.  These aren't secure enough.

    But  then  comes  the  problem  of what to do about possible multiple
    remote processes that may need to be triggered by the same remote
    sysop.  Here's where you can be a bit creative, especially if you use
    some of the nifty little batch file enhancements that have been
    introduced in fidonet over the years in the batpower echo.  I've talked
    about some of these little tricks in past columns.


    Page 3

    T h e   F i d o G a z e t t e!   Volume IV   Number VII    July, 2010
    Tips and Tricks
    by Janis Kracht

    I saw this note on another Linux site, and thought it might be of
    interest to some linux users in Fidonet (Yeah, Benny (grin), but not me
    :) ).  If you are familiar with Kopete you probably already know how to
    do this.
    Facebook chat uses the XMPP protocol and you can add it as a Jabber
    account in Kopete.  Here's a quick note how to configure Kopete.

    First login to Facebook and visit
    http://www.facebook.com/sitetour/chat.php, click on Pidgin and have a
    look at the given details.  Important is the Facebook user name.

    Now open Kopete and the configuration dialog via Settings >> Configure.
    Add a new account with Add account.  Choose Jabber "XMPP, Jabber,
    Google Talk" and click Next.  As Jabber ID add
    yourfacebookusername@chat.facebook.com and ofcourse enter your Facebook
    password.  Unfortunately ssl is not possible so the rest of the
    configuration options can be left as default.

    Click Finish and that’s it, you’re online on Facebook everytime you
    are online with Kopete now.  Be aware that this probably adds a lot new
    contact to Kopete’s contact list ;) .
    Ed. Comment:  Not for me :) As I’ve said before, facebook just wants my
    name to sell it to some other organization (g).

    Page 4
    T h e   F i d o G a z e t t e!   Volume IV   Number V1      June, 2010
    F  O  O  D      Even sysops have to eat!
    By Janis Kracht, 1:261/38
    Want to contribute something here?  Send your submission to fidogazette
    'at' filegate.net or email janis at filegate.net, or janis kracht at
    1:261/38 (filegate.net) and it will get published here in the
    next issue :)

    ===Italian Meat Sauce With Sausage and Meatballs===
    From an Original Post in the Fidonet Cooking Echo
    by Janis Kracht
    ===Italian Meat Sauce With Sausage and Meatballs=== 
    Cooking Echo people, Ruth and Steve Haffly came over on Wednesday
    afternoon so I could show Ruth how I make Italian sauce and ravioli from
    scratch.  We had such a blast :) Even the pups were uh..  mostly good
    since we had company (g).  This is my recipe used to make the sauce
    for the ravioli.  To see the recipes for the ravioli dough, ricotta from
    scratch, and ricotta filling, have a look at the COOKING echo.

    1 pound Italian Sweet Sausage links
    2 28.oz cans of Italian whole peeled tomatoes or whatver large size 
      can you can find.  Pour the tomatos into a blender, one at a time,
      and pulse blend for a moment or two, to break them up.  I don't like
      the texture of Tomato sauce made with Tomato Puree..  it loses
    2 6-oz cans tomato paste
    1/4 cup olive oil
    2 cloves garlic, crushed and chopped
    2 tablespoons dry basil, or 4 or 5 fresh leaves minced
    Salt, pepper to taste, or about 1 tsp. salt, one or two grinds fresh 
      black pepper
    1 pinch of thyme
    1/2 tablespoon dry Oregano
    2  tablespoons Pesto (I usually keep a bowl of it in the 'ridge).
    15-20 meatballs (see below).

    In a large frying pan, brown the sausages on med-high heat until all
    sides are browned.  Set aside.

    In a clean very large pan (like a dutch oven), heat 3 or 4 tablespoons
    of oil.  People argue about what cookware makes the best sauce, but my
    mom and I both think you do best with a heavy stainless steel pot

    Add the garlic and carefully brown.  Don't let it burn. I crush the
    garlic with the flat side of a large knife, and then chop it up.

    Add the tomatoes and paste and stir well to mingle everything.  Fill
    the 2 cans from the tomato paste with water.  Add these containers of
    water to the sauce..  so about 12-some ounces.  It's going to simmer
    for a while.  Add the pesto to the sauce.  Turn the heat up to high for
    about 2-3 minutes or until you see it just start to boil, then lower it
    to medium, stirring.  You want to get this to a bare boil quickly, and
    then turn the heat down to a very slow slow simmer.

    Add the sausages to the pot.  Add the browned meatballs (see below). 
    Stir gently and remember if you are rough with the meatballs you'll
    destroy the sauce :)

    For the first hour,  keep an eye on the sauce, stirring gently, but
    frequently.  If it starts to boil, you need to put the sauce pan in
    some other larger pan (I use my cast iron huge frying pan).  When you
    see the sauce is starting to thicken a bit, partially cover the pot. 
    You don't want to lose all the moisture out of the sauce.

    The sauce should be done in about 3-4 hours.

    2 lbs.  hamburger (we only buy grass-fed beef)
    1 thick slice homemade bread, or Italian bread.  Pass under the running
      water faucet to wet it, then give the bread a light squeeze to get
      the excess water out.  Obviously if you use air-bread, you will end
      up with a blob of soggy yech.
    2 large eggs
    1 or 1 1/2 cups Italian flavored bread crumbs, or make your own
      breadcrumbs using spices such as parsely, basil, onion powder, garlic
      powder, garlic salt, thyme, red pepper.  Grind, season and toast in
      the oven if you make your own.
    2 large cloves garlic, finely minced.
    1 1/2 cups Italian Locatelli Romano cheese.
    1/2 cup fresh Italian flatleaf parsely, chopped
    1 tsp. salt
    1/2 tsp pepper
    1 cup olive oil

    Mix all ingredients except for the olive oil well, but don't overwork
    the hamburger.  Roll into balls in the cups of your hand, compressing
    and rolling until you have a 1 and 1/2 inch meatball.

    Heat the oil in a large frying pan, and start putting the meatballs in
    one at a time, slowly.  Shake the pan now and again, to cause the
    meatballs to roll and brown all over.  Or, you can just turn them with
    a spoon.  Keep cooking them until they are a dark golden brown.  If you
    take them out too soon, they will fall apart in the sauce.


    Page 5

    T h e   F i d o G a z e t t e!   Volume IV   Number VII    July, 2010
	!!!        G A Z E T T E   B B S   L I S T        !!!
	By bbslist @ filegate.net    
	Send updates, changes to address above or to janis @ filegate.net.
	System.......Prism BBS
	Software.....BBBS LiI v4.01 Flag #
	OS...........Linux (Gentoo)
	C/B Verify...None
	Access.......First Call access to Msg bases, 
	             and file areas.            
	             telnet access offers full features 
	             of the standard bbs such as doors,
	             qwkmail, BWmail,Files, etc.       
	             [web interface is limited really 
	             to reading messages and replying 
	             online, or downloading messages  
          	     in qwk packets, but not uploading
	             them], and file download access. 
	FTP:	     ftp.filegate.net, port 60721
    		     public access to file areas (please 
       		     note change of port for public access).
	System.......Time Warp of the Future BBS
	Software.....sbbs 3.15a (very beta)
	OS...........win. (xp pro. sp3)
	C/B Verify...None
	Access.......First Call access to Msg bases, and file areas.
	Telnet.......time.synchro.net:24 or time.darktech.org:24
	             or timewarpfuture.dyndns.org:24
	             telnet access offers full features 
	             of the standard bbs such as doors,
	             messages or file area etc.
	             Web interface is limited really to reading messages 
        	     and replying online, or downloading messages in qwk 
           	     packets, but not uploading them, and file download access. 
           	     SBBS files available.

	System.......Lionsden BBS
	OS...........Windows XP
	C/B Verify...None
	Access.......First Call access to Msg bases, and file areas.
	             telnet access offers full features
     		     of the standard bbs such as doors, 
     		     qwkmail, Files, etc.
	             You will redirected to a menu where you can 
	             choose one of three sites.  The first one is 
	             private and requires PW to get into.
	FTP..........FTP://lionsden.darktech.org Files only


	System.......Christian Fellowship
	Software.....PCBoard 15.3
	OS...........Windows XP pro
	C/B Verify...Manually via email or voice 
	             usually within 24 hours.
	Access.......Read only until verified. Once 
	             verified write access to Msg bases, file 
	             areas, chat and doors/games.
	Telnet.......cfbbs.dtdns.net or cfbbs.no-ip.com


	System.......Lightning BBS
	Software.....Virtual Advanced
	OS...........Windows XP
	C/B Verify...None
	Access.......First call access to doors, files and
  	             message reading.  Message posting requires 
	             Thanks to VADV-PHP you can access almost 
	             everything the BBS has to offer from the
	             web, with the exception of door games.


	System.......Roach Guts BBS 
	Software.....Maximus on Port 23 (primary)
	             Synchronet on Port 24 (temporary)
	OS...........Windows XP
	C/B Verify...None
	Access.......First call access to doors, files and
       		     message reading.  Message posting requires



    Page 6
    T h e   F i d o G a z e t t e!   Volume IV   Number VII
    July, 2010  
    IFDC FileGate News:
    New file echo in Perl FDN

    Jame Clay, coordinator of the Perl FDN has added a new file area.  This
    is the complete list of areas:
    % FDN:          Perl File Distribution Network (PerlNet)
    % Coordinator:  RJ Clay, 1:120/544 (jame@ftn.rocasa.us)
    % HUB: No
    % ------------------------------------------------------------------------
    % File Echo                   Description
    % ------------------------------------------------------------------------
    Area PERLMOD     0     !      Perl modules and extensions
    Area PERLBIN     0     !      Binaries for Perl and Perl utilities
    Area PERLSCR     0     !      Perl scripts
    Area PERLMISC    0     !      Perl FAQ's, Hints, and Tips
    Area PLHATCH     0     *&     PerlNet submissions for review
    Page 7
    T h e   F i d o G a z e t t e!   Volume IV   Number VII    July, 2010
    Fidogazette is published by Janis Kracht, Editor, with the help of
    Richard Webb 1:116/901 (Old School ToolBox), and Sean Dennis 1:18/200
    (The Slightly Crusty Sysop).  If you have an idea for a column or a
    series of articles, please contact me :)
    Where to Send Your Articles

    Unlike most editors, I surely do not  mind running my mouth when
    there is a sparcity of articles for the 'zine.  I'd MUCH rather
    you sent in material but I think until someone starts a
    discussion you feel like commenting about, you evil dullards
    (just kidding!!!) will no doubt complain about "no issues" (grin)
    So I will fill these issues with my meanderings and thoughts and
    hopefully we will grow into something of consequence here :)
    Don't be offended.. write an article!

    If you WOULD like to submit an article and prove me wrong about
    the dullard aspect of you guys and gals (bg), feel free to drop
    your article off at:

    By email attach to address: janis @ filegate.net 
    Fidonet attach:     Janis Kracht at 1:261/38     Modem: 607-655-5652 
    1:261/100 filegate.net port 24555  via binkp or telnet mailer  
    (don't send articles as routed attaches, send them direct to filegate.net).
    Standard binkp port only supports BinkP (24554).

    Give it a title, sign your name and network address if you have
    one and send it along!

    Don't worry about the format, I can take anything you send me
    and mutilate it further as you can see above.  Linux is nice
    that way (g).  Spell checking your own work will help though
    (something I'm typically guilty of (g)).
     To send reviews or recipes to the Food section, email or netmail Janis
     as above.

     To send a question to Dr. Debug, email a question to
     dr.debug @ filegate.net or post in the fidogazette echo! :)

     To send a listing to the fidogazette internet bbs list, send your
     bbs listing to bbslist @ filegate.net or post it in the fidogazette
     echo!  :)
    Page 8
    T h e   F i d o G a z e t t e!   Volume IV   Number VII    July, 2010