Geek Freely: ftp

    Featured Post

    The whole point in this post is to run your own VPN service, and allow you to connect remote devices to your home network.

    To start off yo…

    Showing posts with label ftp.

    Showing posts with label ftp.

    So, for the longest time I tried to get

    working with iPhone and my home server (my problem was I was trying to use FTPS, instead of SFTP).  Using FileZilla I could always successfully connect using “require explicit FTP over TLS”:

    Based on this I figured it was an issue with the iPhone apps, I think it was error 425 (cannot build data connections).  Then I thought it was my , since I used , I figured maybe something was screwy – a draw back of bleeding edge geeky stuff, you question it.  Anyway, it was a port configuration issue by me.

    I needed to open port 22, not 21.  I also had to connect using different settings SFTP.

    As for iPhone client, I have tried a few; FTPOnTheGo, Files Connect, and Easy FTP.  Of them all I like FTPOnTheGo – I should probably look into the options again – considering iPad clients too.

    Since I originally stater this investigation and setup, I treated myself to a new router .  I might write a quick review on it actually…

    From the following site:

    Step 1: Generate a Private Key

    The openssl toolkit is used to generate an RSA Private Key and CSR

    (Certificate Signing Request). It can also be used to generate

    self-signed certificates which can be used for testing purposes or

    internal usage.

    The first step is to create your RSA Private

    Key. This key is a 1024 bit RSA key which is encrypted using Triple-DES

    and stored in a PEM format so that it is readable as ASCII text.

    openssl genrsa -des3 -out server.key 1024

    Follow the on-screen instuctions.

    Step 2: Generate a CSR (Certificate Signing Request)

    Once the private key is generated a Certificate Signing Request can be

    generated. The CSR is then used in one of two ways. Ideally, the CSR

    will be sent to a Certificate Authority, such as Thawte or Verisign who

    will verify the identity of the requestor and issue a signed

    certificate. The second option is to self-sign the CSR, which will be

    demonstrated in the next section.

    During the generation of the

    CSR, you will be prompted for several pieces of information. These are

    the X.509 attributes of the certificate. One of the prompts will be for

    “Common Name (e.g., YOUR name)”. It is important that this field be

    filled in with the fully qualified domain name of the server to be

    protected by SSL. If the website to be protected will be , then enter at this prompt. The command to generate the CSR is as follows:

    openssl req -new -key server.key -out server.csr

    Step 3: Remove Passphrase from Key

    One unfortunate side-effect of the pass-phrased private key is that

    Apache will ask for the pass-phrase each time the web server is started.

    Obviously this is not necessarily convenient as someone will not always

    be around to type in the pass-phrase, such as after a reboot or crash.

    mod_ssl includes the ability to use an external program in place of the

    built-in pass-phrase dialog, however, this is not necessarily the most

    secure option either. It is possible to remove the Triple-DES encryption

    from the key, thereby no longer needing to type in a pass-phrase. If

    the private key is no longer encrypted, it is critical that this file

    only be readable by the root user! If your system is ever compromised

    and a third party obtains your unencrypted private key, the

    corresponding certificate will need to be revoked. With that being said,

    use the following command to remove the pass-phrase from the key:

    cp server.key    openssl rsa -in -out server.key

    The newly created server.key file has no more passphrase in it.

    -rw-r–r– 1 root root 745 Jun 29 12:19 server.csr    -rw-r–r– 1 root root 891 Jun 29 13:22 server.key    -rw-r–r– 1 root root 963 Jun 29 13:22

    Step 4: Generating a Self-Signed Certificate

    At this point you will need to generate a self-signed certificate

    because you either don’t plan on having your certificate signed by a CA,

    or you wish to test your new SSL implementation while the CA is signing

    your certificate. This temporary certificate will generate an error in

    the client browser to the effect that the signing certificate authority

    is unknown and not trusted.

    To generate a temporary certificate which is good for 365 days, issue the following command:

    openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt

    I was trying to use symbolic links:

    ln -s /mnt/Personal/Music /mnt/user/Music

    But I needed to add them to the wheel group – which didn’t make sense, I tried doing everything relative, instead of absolute – like indicated but it didn’t work for me.  Adding them to wheel basically allowed them to navigate anywhere they wanted.

    If anyone has had success using symlinks with their proftpd server, do let me know.

    In the end I had to mount a null filesystem

    mount_nullfs /mnt/Personal/Music /mnt/user/Music

    This basically duplicates the filesystem, any changes made to the dupe will affect the original, so be very careful with your user privilages.

    To undo this “link” you can simple umount the dupe

    umount /mnt/user/Music

    I do not currently know of any ill side effects to this, but I would appreciate any feedback from the guru’s out there.

    I do have to run these commands every-time the system starts – this is a real drawback – I would love to use symbolic links, but have not been able to work it out.

    Subscribe to:


    Blog Archive


    Leave a Reply

    Your email address will not be published.