FXP.One:Clients: Difference between revisions

From Lundman Wiki
mNo edit summary
mNo edit summary
Line 1: Line 1:
Welcome to the FXP.One project.


Blogs have literally taken in the internet by storm. It seems as if just about everyone has a blog.  Blogs are so popular that it there is a good chance that you have one.  While blogs are nice, it is sometimes difficult to get them seen. Many blog owners, maybe even yourself, are unsure how to go about generating more internet traffic.  Luckily for you and other blog owners, there are a number of different ways that you can work to increase the number of page views that your blog receives. 


The first step in getting traffic to your blog is to make sure that you have an interesting topic.  If you are writing about your personal experiences, you may find that not everyone wants to read about them, that is unless you lead an adventurous life. However, if you blog on a wider range of topics, such as working from home, saving money, or being a good partner, you are automatically likely to get a bigger audience. This is because more internet users, especially ones that you do not know, would be more willing to read information on these topics, rather than your daily adventures or lack of adventures.
Before you start, this is not just another FTP/FXP client. It does not
work that way.


Once you have found a topic that you would like to write about, you will need to start creating your blog, if you haven’t already.  When making your blog it is important that you write content that will be useful to your blog’s general topic. It is also important to include lots of content. Content is what most search engines use when picking up websites. In the event that your blog gets indexed by a search engine, you will find that your blog’s traffic should automatically increase. This is because a large number of internet users use search engines to find what they are looking for.


Although a high search engine ranking may help to increase the amount of traffic your blog sees, it is sometimes difficult to do. Most individuals do not go further than the third or fourth page, when looking at search engine results.  This means that if your blog is not considered to be high ranking, you may not get the results that you were hoping for.  However, this does not mean that you should give up. Instead, it means that you just have to find another way to promote your blog. It is reliable to have a video from professionals, check this Reputable [http://traccfilms.co.uk/video-production-services/ Video Production Company] will identify where your audience spends time online to direct them to your video – and then to your site.
FXP.One consists of an engine, and
you would need (at least) one GUI to control it.




One of the many other ways that you can go about promoting your blog is through the use of online video websites, particularly the ones that are free to use. Online video websites are websites that allow internet users to upload videos that they have created. Once uploaded, these videos can be viewed by thousands, if not millions, of internet users.  If you are looking for a fun and low-cost way to market your blog, you are advised to give online video websites some though.
==FXP.One engine==


Before uploading your video, to an online video website, you will have to make your video. To do so, you will need a recording device.  The best devices to use include camcorders and webcams. When making your online video, it is important not to make your video sound too pushy or like spam. It may be a good idea to state the purpose of your blog and what can be found there. You may also want to record yourself or someone else visiting your blog to showcase your blog’s features.  You could also take still shots, also commonly known as screen shots.  These shots will allow you to post pictures of your blog pages. Having those pictures float through your online video is a great way to show internet users what your blog is all about.
The idea was to put all the hard code into an engine that is really
easy to interface with. This has worked surprisingly well, in that you
can FTP/FXP entirely by using "telnet". This means writing a client,
which is essentially just a Display Shell, quite trivial. This
includes people who wants to just script clients, like by using perl,
python and so on.


Once you have finished making your video, you will need to upload that video to your computer. Once your recording device is hooked up to your computer, it should be recognized by a moving making software program. These programs will not only allow you to save your video, but edit it as well.  Once your video is saved, you will need to follow the uploading directions for each online video website that you would like your video or videos to be uploaded to.  
This also means you do NOT have to run the engine on the same machine that you run the GUI client(s).  


It is important to note that you are not guaranteed to see an increase in your blog’s traffic, but why not at least give it a shot? With most video websites being free to use, there shouldn’t be any risks associated with incorporating your blog into your next online video.
For example, if you had a stable host, perhaps even with a static IP
making the credentials for authentication easier, you could run the
engine there. Then connect to it by the client of your choice.
 
You can disconnect this client (the engine will keep working if you do
not tell it to stop) and start a new (and possibly different) client
elsewhere, and resume control of your previous work.
 
But you can run the engine and client at the same time, and quitting
at the same time, making it appear like a normal FTP/FXP client.
 
 
'''If you are looking for a Windows binary, please download the bundle from the latest [[UFxp]] client'''
 
==Compiling and Install the engine==
  % wget http://www.lundman.net/ftp/fxp-one-1.4.tar.gz
  % tar -xvf fxp-one-1.4.tar.gz
  % cd FXP.One/
  % ./configure
  % make
  % make install
 
Now create your SSL keys
 
  % openssl req -new -x509 -nodes -out lion.pem -keyout lion.pem
 
 
Create your .FXP.One folder and copy lion.pem into it
 
  % mkdir .FXP.One && cp lion.pem .FXP.One/ 
 
Start the FXP.One engine
 
  % FXP.One
 
(Please use gnuMake; which might be called make, gmake, gnumake etc on your system)
 
This should always compile the '''FXP.One engine'''. If ''configure'' can find the correct '''CDK''' library and '''ncurses''' on your system it will also compile the '''ncurses''' client '''FXP.cOne'''. Otherwise it will skip compiling this client.
 
'''Openssl-devel'''If you see a error like this:
''checking whether we need extra options to link OpenSSL... configure: error: Found linkable OpenSSL in , but it doesn't run, even with -R.  Maybe specify another using --with-ssl-dir?''
 
You will need to openssl-devel for your system. On most Red Hat Variants it can be done with yum.
 
yum -y install openssl-devel
 
 
If you want to run '''clomps-irc''' you will need libpcre and headers, so most likely the -dv version if there is one:
 
apt-get install libpcre3-dev
 
 
 
 
'''''SSL Issues'''''
 
If your trying to connect from your client and get errors about ssl it probably means that they versions of ssl you have on your engine and your client are not compatible.
 
For example on the client end we have ssl version OpenSSL 0.9.8e-fips-rhel5 and on the server and OpenSSL 09.8k on another. There are many reasons why this will not work and many more why it should. In this case you will need to compile OpenSSL 0.9.8K on the server you wish to use FXP.Oned on and build FXP.Oned against that version of ssl. It the example below we will build openssl-0.9.8k in a local directory and compile FXP.Oned to use it.
 
To do this go to the openssl.org downloads page and download the version you want to use.
http://openssl.org/source/
wget http://openssl.org/source/openssl-0.9.8k.tar.gz
tar -xvzf openssl-1.0.0g.tar.gz
cd openssl-1.0.0g
./config -shared
make
 
Now go back to your FXP.Oned directory,
make clean
./configure LIBS=-ldl --with-ssl-dir=/home/erin/srcs/openssl-1.0.0g
make
make install
 
==Running the engine==
 
 
'''You will most likely need to create an SSL certificate for the engine since the default is only to accept secure connections.'''
 
 
Since the engine will be saving your remote FTP site information, as
well as any User/Passwords you chose on disk, you should consider
encrypting these files.
 
FXP.One engine will do this for you. When you start the engine, it
will as for a "Key". This is the Key that it will use to encrypt all
its data files. If you do not want encryption, just press return.
 
For the first time you run FXP.One, just make up whatever Key you
want.
 
When you start the engine in future, you have to specify the correct
Key or it will not be able to read your data files. (And you will not
be able to login).
 
To start again, you need to delete all .FXP.One files, and the engine
will create these again.
 
When the user file does not exist, the FXP.One engine will
automatically create a login as "admin" with password "admin".
 
 
NOTE: If you edit .FXP.One.settings file, you can change the option
"ssl=1". By default it will only allow SSL connections. If you change
it to "ssl=0" you make it optional. This allows you to telnet to the
engine should you wish to check it out. Please read the
"engine/API.txt" for more information on the FXP.One protocol.
 
NOTE: Please be aware that all skiplist, movefirstlist and passlists
are separated by the "/" character.
That is, "fmovefirst=*.sfv/*.nfo".

Revision as of 02:59, 5 March 2012

Welcome to the FXP.One project.


Before you start, this is not just another FTP/FXP client. It does not work that way.


FXP.One consists of an engine, and you would need (at least) one GUI to control it.


FXP.One engine

The idea was to put all the hard code into an engine that is really easy to interface with. This has worked surprisingly well, in that you can FTP/FXP entirely by using "telnet". This means writing a client, which is essentially just a Display Shell, quite trivial. This includes people who wants to just script clients, like by using perl, python and so on.

This also means you do NOT have to run the engine on the same machine that you run the GUI client(s).

For example, if you had a stable host, perhaps even with a static IP making the credentials for authentication easier, you could run the engine there. Then connect to it by the client of your choice.

You can disconnect this client (the engine will keep working if you do not tell it to stop) and start a new (and possibly different) client elsewhere, and resume control of your previous work.

But you can run the engine and client at the same time, and quitting at the same time, making it appear like a normal FTP/FXP client.


If you are looking for a Windows binary, please download the bundle from the latest UFxp client

Compiling and Install the engine

 % wget http://www.lundman.net/ftp/fxp-one-1.4.tar.gz
 % tar -xvf fxp-one-1.4.tar.gz
 % cd FXP.One/
 % ./configure
 % make 
 % make install

Now create your SSL keys 

 % openssl req -new -x509 -nodes -out lion.pem -keyout lion.pem


Create your .FXP.One folder and copy lion.pem into it 

 % mkdir .FXP.One && cp lion.pem .FXP.One/

Start the FXP.One engine 

  % FXP.One

(Please use gnuMake; which might be called make, gmake, gnumake etc on your system)

This should always compile the FXP.One engine. If configure can find the correct CDK library and ncurses on your system it will also compile the ncurses client FXP.cOne. Otherwise it will skip compiling this client.

Openssl-develIf you see a error like this: 

checking whether we need extra options to link OpenSSL... configure: error: Found linkable OpenSSL in , but it doesn't run, even with -R.  Maybe specify another using --with-ssl-dir?

You will need to openssl-devel for your system. On most Red Hat Variants it can be done with yum. 

yum -y install openssl-devel


If you want to run clomps-irc you will need libpcre and headers, so most likely the -dv version if there is one: 

apt-get install libpcre3-dev



SSL Issues

If your trying to connect from your client and get errors about ssl it probably means that they versions of ssl you have on your engine and your client are not compatible.

For example on the client end we have ssl version OpenSSL 0.9.8e-fips-rhel5 and on the server and OpenSSL 09.8k on another. There are many reasons why this will not work and many more why it should. In this case you will need to compile OpenSSL 0.9.8K on the server you wish to use FXP.Oned on and build FXP.Oned against that version of ssl. It the example below we will build openssl-0.9.8k in a local directory and compile FXP.Oned to use it.

To do this go to the openssl.org downloads page and download the version you want to use. 

http://openssl.org/source/
wget http://openssl.org/source/openssl-0.9.8k.tar.gz
tar -xvzf openssl-1.0.0g.tar.gz 
cd openssl-1.0.0g 
./config -shared
make

Now go back to your FXP.Oned directory, 

make clean 
./configure LIBS=-ldl --with-ssl-dir=/home/erin/srcs/openssl-1.0.0g
make 
make install

Running the engine

You will most likely need to create an SSL certificate for the engine since the default is only to accept secure connections.


Since the engine will be saving your remote FTP site information, as well as any User/Passwords you chose on disk, you should consider encrypting these files.

FXP.One engine will do this for you. When you start the engine, it will as for a "Key". This is the Key that it will use to encrypt all its data files. If you do not want encryption, just press return.

For the first time you run FXP.One, just make up whatever Key you want.

When you start the engine in future, you have to specify the correct Key or it will not be able to read your data files. (And you will not be able to login).

To start again, you need to delete all .FXP.One files, and the engine will create these again.

When the user file does not exist, the FXP.One engine will automatically create a login as "admin" with password "admin".


NOTE: If you edit .FXP.One.settings file, you can change the option "ssl=1". By default it will only allow SSL connections. If you change it to "ssl=0" you make it optional. This allows you to telnet to the engine should you wish to check it out. Please read the "engine/API.txt" for more information on the FXP.One protocol.

NOTE: Please be aware that all skiplist, movefirstlist and passlists are separated by the "/" character. That is, "fmovefirst=*.sfv/*.nfo".

Retrieved from "http://lundman.net/wiki/index.php?title=FXP.One:Clients&oldid=4348"