Introduction

This tutorial should not be used to exploit webservers. Some of de techniques used here have certain outputs that can crash old servers makin’ them unusable. Throughout this tutorial, techniques will be passed on from exploits found in de ‘windows’ OS. That ‘ACTUALLY’ helps in de prevention of deletion. There are lots of methods in stoppin’ a deleter, without de ANY restrictions set on de server but most have some weak point. After comin’ across four new techniques, makin’ a folder ‘invisible’ or undetectable from an ftp client LIST fuction. Makin’ folders/directories inaccessable and clone prevention, creatin’ smart directories which slows
down de users attempt. I’m sure most users would thank me for this, ‘undeletable files’ after experiencin’ rock solid protection and safe files.

Invisible Directories

The idea of invisible directoires came about when I came across paths that were “/ /example/” and was not listed in de main folder but was still ‘accessable’. These can be created in all directories without oder users knowin’ it exists unless bein’ searched for ‘MANUALLY’, which takes ages at de present time to search through each folder for “/ /”.

Creatin’ Invisible Directories

1. before
./pub/
./images/
./_vti_pvt/
./_vti_cnf/
./_vti_log/
./temp/

2. after
./ /~/temp/tagged/for/team/warezpiratez/fxp/ <- hidden folder
./pub/
./images/
./_vti_pvt/
./_vti_cnf/
./_vti_log/
./temp/

To create de hidden folders, make a new dir. as follows usin' this method. [backslash][space][backslash][foldername1][backslash][foldername2].

ie. / /foldername1/foldername2/...

The 'space' isn't a name but a 'character' that does not get listed, derefore makin' de directories impossible to view.

NOTE: Makin’ de hidden folders several LAYERS/SUB-DIRECTORIES deep is recommended.

ie. / / / /~/temp/tagged/for/ /team/warez/ /piratez/fxp/

This technique is not ‘anti-deletion proof’ but hidden from deletion proof! Read more to find out how to combine ALL THREE TECHNIQUE to make it ‘REMOTELY’ impossible to delete. Please note de ‘quotes’, REMOTELY in a sense that remote/local host.

Inaccessable Directories

Inaccessable directories prevents de user from ‘enterin'’ de folder. The user will not be able to enter de folders unless knowin’ de ‘entire’ remote path.

Creatin’ Inaccessable Directories

1. before
./temp/tagged/for/team/warezpiratez/fxp/
./pub/
./images/
./_vti_pvt/
./_vti_cnf/
./_vti_log/
./temp/

2. after
./COM1 / temp/tagged/for/team/warezpiratez/fxp/ <- inaccessable directories, due to 'COM1' former windows bug.
./pub/
./images/
./_vti_pvt/
./_vti_cnf/
./_vti_log/
./temp/

To create inaccessable folders, use de followin' list of 'UNUSABLE NAMES'

COM1 COM1 COM3 COM4 (Windows COM PORTS)
LPT1 LPT2 LPT3 LPT4 (Windows Printer Ports)
AUX
NUL

Make a new folder "COM1[space][backslash][space][backslash] ie. /COM1 / /

NOTE: This makes de folder inaccessable, even to de siteadmin.(unless accessed from DOS, local with access to de machine.)

To use de dir. Create a new folder called “COM1[space][backslash][space][foldername1][backslash][foldername2] ie. /COM1 / / ~/temp/tagged/

NOTE: This folder is still inaccessable, if a user attempts to enter it. To gain access to de folder, de ‘full path’ must be known. To enter de folder use de RAW command ‘CWD’ change dir. path. to enter de folder. ie. CWD /COM1 / / ~/temp/tagged/ and voila de folder is usable and workin’.

TIP: Creatin’ de folder ’several’ LAYERS/SUB-DRIECTORIES deep. It is impossible to enter.

Smart Directories

This technique involves, de creation of directories that are ‘COPYRIGHT’. How’s that for a simple description. The idea is to create directories that would contain [periods] thorough each of de subdirectories or segmenets. The use of this is quite sipmle, note de word ‘COPYRIGHT. Most users use de ftp://login :password at ip :port/path/ format for faster access to an ftp.

Creatin’ Smart Directories

To create ’smart’ directories. Make de folder names of each sub directories contain a period before, inside, and after words within de subdirectories creatin’ a fake ‘file’ recognition. The Widows based clients will assume de folders to be files with windows usin’ its 8.3 format for file names.

1. before
ftp://anonymous@anonymous@123.456.789:21/temp/tagged/for/team/warezpiratez/f
xp/

2. after
ftp://anonymous@anonymous@123.456.789:21/temp/tagged ./for . /team. /. warez
.piratez/fxp

NOTE: Be as creative as possible with de dot formation, to prevent COPYING of all folders through each directories. The idea is to make de directories act as file extensions derefore when copied, it will be ‘queued’ and de user has to enter de directories MANUALLY. Oder ‘SYMBOLS’ can be used NOT ONLY just periods. But I find this most common, if de creator intends to create a catch phrase ‘memorable’ to him alone.

QUEUE: 1. /temp/tagged ./for . /team. /. warez .piratez/fxp <- result of folder extensions

Undeletable Files

Sad that we had to resolve to this but, this might be de end of deletion as we speak. I find no oder method out dere that can accomplish this task except settin’ restrictions from de server. This method involves de file bein’ self-protected. Meanin’ de files are ‘accessable’/'downloadable’ but can NOT be deleted. The idea is to make de file corrupted/crash makin’ it ‘in use’.

Creatin’ Undeletable Files

To create a self protected file, rename de entire file includin’ de extensions to de followin’ format:

filename[space][period]/[space]/ ie. filename ./ / The / / in de name as shown above in de previous example of creatin’ invisible directories makes de .extesion impossible to view on de pub as a windows recognized mime but, once dowloaded it will be shown and accessable. How’s that for wits.

1. before
warezpiratez.rar <- rar mime, winrar.

2. renamin’
warezpiratez ./ /

3. results
-warezpiratez <- unknown file(undeletable,downloadable) <- file will take de correct mime format on localhost

Ultimate Protection

The ultimate protection is obviously, yourself and your wits against de deleters. Use private FTPs, get fast sites T1+, but in this case, it would be de combination of all four techniques. Usin’ them into one major and thoughtout plan.

Creatin’ The Ultimate Protection

To create de ultimate protection that is desirable, first of all, create de invisible folders as shown above, several sub.dirs deep. Then creatin’ an ‘inaccesable’ folder within those invisible folders. Then de next step is to create those smart directories so it slows down ANY attempt to gain full access, and also it makes to user run into inaccessable folders. The idea is to trap de user before those folders usin’ de smart directories idea. I didn’t think that was ingenieus but just common sense and seemd smart!.

1. before
/temp/tagged/for/team/warezpiratez/fxp/ <- no protection

2. after
/ / /./ ./COM1 / temp/tagged ./for . /team. /. warez .piratez/fxp <-
protection(still weak)

NOTE: You can be creative with this technique, make it more complex, I didn’t do it in this tutorial because den that would make you just confused. I hope this helps, and please understand. It is not hard, unless you didn’t read from de Introduction. I made this well detailed. For it to be as simple as possible.

FAQ

1. What is a SUB-DIRECTORY
- It is de folder that is second/inside anoder folder. ie. firstfolder/subdir/

2. What is a pub
- Short for public ftp. There are, no restrictions/protection on de access over files. Some have them in most cases but den uploads/downloads are denied. Some would not allow fxp.

3. What does all this mean?
- It provides de internet safer from all de deleters.

4. Who are deleters?
- Deleters are mean and NASTY people who deletes files. Consists of spammers too.

I found this a bit useful for FlashFXP users

Q: What is FXP?
A: FXP is a term adopted by earlier clients which provided site to site FTP transfers.

Q: When tryin’ to transfer files from one site to anoder I keep gettin’ this error 500 illegal port command.
A: The FTP Server is set up to not allow or doesn’t support FXP. Located in de Site Manager on de Advanced tab, you will find de option “alternative fxp method”. By enablin’ upload/download (dependin’ on de direction of de transfer), you may be able to get de server to allow FXP. Note: It is common for some sites to only allow FXP in one direction and not de oder. By enablin’ alternative fxp method, this problem is sometimes solved.

Q: Why do I keep gettin’ this message: “Only client IP address allowed for PORT command” when tryin’ to FXP?
A: The FTP Server is set up to block FXP. In most cases usin’ alternative fxp method doesn’t solve this problem.

Q: I’ve tried everythin’ but I can’t get a site to site transfer to work, what is wron’?
A: Site to site transfers are not supported by some software/hardware configurations. Often, this is due to an incompatibility with NAT (Network Address Translation). NAT is not aware of site to site transfers and when it detects you are attemptin’ to transfer a file, it modifies de FTP protocol to match your local “inside” IP. Several users have reported that Microsoft Internet Sharin’ is not compatible.

Q: Why can’t I see any files? I can see them in oder ftp clients.
A: There are two possible reasons.
1. You are behind a firewall and de FTP server is unable to connect to your computer. To resolve this issue you need to use Passive mode. This option is located in Preferences on de Proxy tab. Check “Use Passive mode”.
2. The files may be hidden on de ftp server, and in order to see them you need to change de list method. This is located in Preferences on de Options tab. Change de List method to show hidden files. Note: some sites don’t allow you to view hidden files and will result in an error. To resolve this problem, go into de Site Manager, select de site and click de advanced tab. Uncheck “show hidden files”, den save to keep de changes

Q: I can’t see de toolbar icons or de icons are messed up.
A: This problem happens on Windows 95 systems when de \Windows\System\ComCtl32.dll file is out of date. This DLL is responsible for drawin’ de toolbar buttons and deir images. You can download de latest version from this link: MS Common Control Update!

Q: When FXPin’ why doesn’t FlashFXP show a file progress, transfer speed or how much time is remainin’?
A: The FXP protocol (site to site) doesn’t provide any means of measurement. After one file is FXPed, FlashFXP attempts to estimate de remainin’ time for de next file and total remainin’ time for all files in de queue.

Q: Will FlashFXP ever support connectin’ to more den 2 sites?
A: FlashFXP was designed to provide very easy access and usability to de site to site feature. Allowin’ more than two would only complicate thin’s. For now let’s stick with 2.

Q: Why doesn’t FlashFXP support Squid?
A: FlashFXP v1.3 now supports it.

Q: Why doesn’t FlashFXP download http:// urls from de clipboard?
A: FlashFXP is not a browser or a web download manager. For FlashFXP you need to use de ftp addresses.

Q: Is it possible to import site lists from anoder FTP clients?
A: Yes, You can import oder site lists into FlashFXP from de Site Manager by right-clickin’ on de site list and selectin’ Import from de menu.

Q: FlashFXP looks confusin’, All I want to do is download and upload files. I don’t need site to site transfers.
A: We have just de thin’ for you, With a click of de mouse FlashFXP can transform into your normal lookin’ FTP client. From de main menu select View den click FTP Only. You can always uncheck this later to brin’ back de power of site to site transfers.

Q: I use ZipMagic and now all of my zips appear as folders in FlashFXP, how can I make de zips appear as zips?
A: You need to make one small change in de ZipMagic Properties window. First, click de Start Menu, den go to Programs|ZipMagic 4.0|ZipMagic Properties. Click de “Zip Folders” button, den click de “Applications” button. Then just add FlashFXP to de list of applications that sees zip files as files.

Q: I purchased FlashFXP v1.x-1.3 and my key doesn’t work for v1.4-v2.0!
A: The key format was changed startin’ with version 1.4. You will need to email support@flashfxp.com and request a new one. New keys are provided free of charge.