|
Introduction
If you have been pubbing for a few months you will remember the older
versions of FlashFXP (before 1.4) were unable to handle semicolons and
people used a lot of semicolons in their paths for a few months. It didn’t
matter whether the pub was NT or UNIX because the semicolon was a client
side glitch not server side. Well now there's another method fairly
similar using FlashFXP and scripting variables.
Necessary Tools
- FlashFXP - A
great ftp client designed with the FXP Groups in mind.
- BitBeamer -
An alternative ftp client that can be used to handle FlashFXP glitches.
Getting Started
First thing you need is a good pub to test stuff out on. Head over to
your local FXP board and find a pub. Once you've got that, load FlashFXP
and connect to it, then go to the pub directory, this is where you have
access to create and remove directories and files. This directory is
specified in a scans results.
404.404.404.404
-------------
DIR: /incoming/
DELETE STATS: deletable
RUNNING OS: Windows_NT version 4.0
RESUMABLE: No
FXP STATS: non-FXPable
The Command Tokens
*NOTE: In this section all directory names can be replaced with
whatever you want unless otherwise specified. The command tokens are
what's important, not the rest of the folder names.
In FlashFXP go to Commands, Edit Commands…, then click on Help.
Command Tokens:
- %f - Selected filenames
- %o - Selected Owners
- %g - Selected Groups
- %d - Prompt for text
Greetz go out to FlashFXP for providing us with this info. Ok so just
use any one of those command tokens in your path. I tend to use all of
them at a once. By using them it means that a person is unable to unlock
your path using FlashFXP and will have to use another program such as
BitBeamer.
Secondly, on NT pubs you can use %20
This also messes up FlashFXP and on NT pubs it sometimes turns out as a
normal space and can confuse deleters.
Example:
/incoming/ / tag / 404 / %f%o%g%d / %20%20 /goodies/
That will cause people, using FlashFXP, trouble when trying to do
things to your path.
Using Your Path
You can have a path containing Command Tokens and still use FlashFXP to
upload and download. The only trouble you might encounter is when trying
to execute a FlashFXP script within your path. If this occurs you can just
unlock your path using BitBeamer and make the changes then relock it or
move the contents to a different path.
Breaking Your Path
To remove your protection you must use BitBeamer 2025. I’ll leave it at
that since I already covered basic unlocking in
Dir Locking - UNIX Advanced.
If you need more advanced dir breaking info check out
Dir Locking - Breaking Dirs.
Closing Notes
I’m quite enjoying this protection. It’s really the only one I use now
in conjunction with multiple spaces and the odd illegal name. Since most
deleters are using FlashFXP this protection is fairly effective.
|