ftpd 0.0.0.pre1

data/Gemfile

@@ -0,0 +1,9 @@
+source 'http://rubygems.org'
+
+group :development do
+  gem 'cucumber', '~> 1.2.1'
+  gem 'double-bag-ftps', '~> 0.1.0'
+  gem 'jeweler', '~> 1.8.4'
+  gem 'rake', '~> 10.0.3'
+  gem 'rspec', '~> 2.0.1'
+end

data/Gemfile.lock

@@ -0,0 +1,43 @@
+GEM
+  remote: http://rubygems.org/
+  specs:
+    builder (3.1.4)
+    cucumber (1.2.1)
+      builder (>= 2.1.2)
+      diff-lcs (>= 1.1.3)
+      gherkin (~> 2.11.0)
+      json (>= 1.4.6)
+    diff-lcs (1.2.0)
+    double-bag-ftps (0.1.0)
+    gherkin (2.11.6)
+      json (>= 1.7.6)
+    git (1.2.5)
+    jeweler (1.8.4)
+      bundler (~> 1.0)
+      git (>= 1.2.5)
+      rake
+      rdoc
+    json (1.7.6)
+    rake (10.0.3)
+    rdoc (3.12)
+      json (~> 1.4)
+    rspec (2.0.1)
+      rspec-core (~> 2.0.1)
+      rspec-expectations (~> 2.0.1)
+      rspec-mocks (~> 2.0.1)
+    rspec-core (2.0.1)
+    rspec-expectations (2.0.1)
+      diff-lcs (>= 1.1.2)
+    rspec-mocks (2.0.1)
+      rspec-core (~> 2.0.1)
+      rspec-expectations (~> 2.0.1)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  cucumber (~> 1.2.1)
+  double-bag-ftps (~> 0.1.0)
+  jeweler (~> 1.8.4)
+  rake (~> 10.0.3)
+  rspec (~> 2.0.1)

data/LICENSE.md

@@ -0,0 +1,9 @@
+Copyright 2012 Wayne Conrad
+
+This software is distributed under the [MIT License](http://opensource.org/licenses/MIT):
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,57 @@
+# FTPD
+
+ftpd is a pure Ruby FTP server library.  It supports implicit and
+explicit TLS, and can be used by a text fixture or FTP daemon.
+
+## UNFINISHED
+
+I created ftpd to support the test framework I wrote for Databill,
+LLC, which has given its kind permission to donate it to the
+community.
+
+I've moved the code from Databill's source tree, but it's not ready
+for prime time yet.  It needs pluggable authentication and file system
+drivers, refactoring, and the removal of bits of the Databill source
+tree which are temporarily included.
+
+## LIMITATIONS
+
+TLS is only supported in passive mode, not active.  Either the FTPS
+client used by the test doesn't work in active mode, or this server
+doesn't work in FTPS active mode (or both).
+
+## REFERENCES
+
+(This list of references comes from the README of the em-ftpd gem,
+which is licensed under the same MIT license as this gem, and is
+Copyright (c) 2008 James Healy)
+
+There are a range of RFCs that together specify the FTP protocol. In
+chronological order, the more useful ones are:
+
+    http://tools.ietf.org/rfc/rfc959.txt
+    http://tools.ietf.org/rfc/rfc1123.txt
+    http://tools.ietf.org/rfc/rfc2228.txt
+    http://tools.ietf.org/rfc/rfc2389.txt
+    http://tools.ietf.org/rfc/rfc2428.txt
+    http://tools.ietf.org/rfc/rfc3659.txt
+    http://tools.ietf.org/rfc/rfc4217.txt
+
+For an english summary that's somewhat more legible than the RFCs, and
+provides some commentary on what features are actually useful or
+relevant 24 years after RFC959 was published:
+
+    http://cr.yp.to/ftp.html
+
+For a history lesson, check out Appendix III of RCF959. It lists the
+preceding (obsolete) RFC documents that relate to file transfers,
+including the ye old RFC114 from 1971, "A File Transfer Protocol"
+
+## WHOAMI
+
+Wayne Conrad <wconrad@yagni.com>
+
+## CREDITS
+
+Thanks to Databill, LLC, which supported the creation of this library,
+and granted permission to donate it ot the community.

data/Rakefile

@@ -0,0 +1,8 @@
+# encoding: utf-8
+require 'rubygems'
+require 'bundler'
+
+$:.unshift(File.dirname(__FILE__) + '/lib')
+Dir['rake_tasks/**/*.rake'].each { |path| load path }
+
+task :default => [:cucumber]

data/VERSION

@@ -0,0 +1 @@
+0.0.0.pre1

data/features/command_errors.feature

@@ -0,0 +1,33 @@
+Feature: Command Errors
+
+  As a client
+  I want good error messages
+  So that I can figure out what went wrong
+
+  Scenario: Unknown command
+    Given a successful connection
+    When the client sends command "foo"
+    Then the server returns a command unrecognized error
+
+  Scenario Outline: Unimplemented command
+    Given a successful connection
+    When the client sends command "<command>"
+    Then the server returns an unimplemented command error
+    Examples:
+      | command |
+      | ABOR    |
+      | ACCT    |
+      | ALLO    |
+      | APPE    |
+      | HELP    |
+      | MKD     |
+      | REIN    |
+      | REST    |
+      | RMD     |
+      | RNFR    |
+      | RNTO    |
+      | SITE    |
+      | SMNT    |
+      | STAT    |
+      | STOU    |
+      | SYST    |

data/features/delete.feature

@@ -0,0 +1,34 @@
+Feature: Delete
+
+  As a client
+  I want to delete files
+  So that nobody can fetch them from the server
+
+  Scenario: Delete a file
+    Given a successful login
+    And the server has file "foo"
+    When the client successfully deletes "foo"
+    Then the server should not have file "foo"
+    And the client lists the directory
+    And the file list should not contain "foo"
+
+  Scenario: Missing path
+    Given a successful login
+    And the server has file "foo"
+    When the client deletes with no path
+    Then the server returns a path required error
+
+  Scenario: No such file
+    Given a successful login
+    When the client deletes "foo"
+    Then the server returns a not found error
+
+  Scenario: Path outside tree
+    Given a successful login
+    When the client deletes "../usr/bin"
+    Then the server returns an access denied error
+
+  Scenario: Not logged in
+    Given a successful connection
+    When the client deletes "foo"
+    Then the server returns a not logged in error

data/features/directory_navigation.feature

@@ -0,0 +1,34 @@
+Feature: Change Directory
+
+  As a client
+  I want to change the current directory
+  So that I can use shorter paths
+
+  Scenario: Change to subdirectory
+    Given a successful login
+    And the server has file "subdir/bar"
+    When the client successfully cd's to "subdir"
+    Then the current directory should be "/subdir"
+
+  Scenario: Change to parent
+    Given a successful login
+    And the server has file "subdir/bar"
+    And the server has file "baz"
+    And the client successfully cd's to "subdir"
+    When the client successfully cd's up
+    Then the current directory should be "/"
+
+  Scenario: No such directory
+    Given a successful login
+    When the client cd's to "subdir"
+    Then the server returns a no such file error
+
+  Scenario: Path outside tree
+    Given a successful login
+    When the client cd's to "../usr/bin"
+    Then the server returns an access denied error
+
+  Scenario: Not logged in
+    Given a successful connection
+    When the client cd's to "subdir"
+    Then the server returns a not logged in error

data/features/file_structure.feature

@@ -0,0 +1,40 @@
+Feature: File Structure
+
+  As a server
+  I want to accept the obsolute file structure (STRU) command
+  For compatability
+
+Scenario: File
+  Given a successful login
+  And the server has file "ascii_unix"
+  When the client successfully sets file structure "F"
+  And the client successfully gets text "ascii_unix"
+  Then the remote file "ascii_unix" should match the local file
+
+Scenario: Record
+  Given a successful login
+  And the server has file "ascii_unix"
+  When the client sets file structure "R"
+  Then the server returns a file structure not implemented error
+
+Scenario: Page
+  Given a successful login
+  And the server has file "ascii_unix"
+  When the client sets file structure "P"
+  Then the server returns a file structure not implemented error
+
+Scenario: Invalid
+  Given a successful login
+  And the server has file "ascii_unix"
+  When the client sets file structure "*"
+  Then the server returns an invalid file structure error
+
+Scenario: Not logged in
+  Given a successful connection
+  When the client sets file structure "F"
+  Then the server returns a not logged in error
+
+Scenario: Missing parameter
+  Given a successful login
+  When the client sets file structure with no parameter
+  Then the server returns a syntax error

data/features/get.feature

@@ -0,0 +1,62 @@
+Feature: Get
+
+  As a client
+  I want to get a file
+  So that I have it on my computer
+
+  Scenario: ASCII file with *nix line endings
+    Given a successful login
+    And the server has file "ascii_unix"
+    When the client successfully gets text "ascii_unix"
+    Then the local file "ascii_unix" should match the remote file
+    And the local file "ascii_unix" should have unix line endings
+
+  Scenario: ASCII file with windows line endings
+    Given a successful login
+    And the server has file "ascii_windows"
+    When the client successfully gets text "ascii_windows"
+    Then the local file "ascii_windows" should match the remote file
+    And the local file "ascii_windows" should have unix line endings
+
+  Scenario: Binary file
+    Given a successful login
+    And the server has file "binary"
+    When the client successfully gets binary "binary"
+    Then the local file "binary" should exactly match the remote file
+
+  Scenario: Passive
+    Given a successful login
+    And the server has file "ascii_unix"
+    And the client is in passive mode
+    When the client successfully gets text "ascii_unix"
+    Then the local file "ascii_unix" should match the remote file
+
+  Scenario: TLS
+    pending "TLS not supported in active mode (see README)"
+
+  Scenario: TLS, Passive
+    Given a successful login with TLS
+    And the server has file "ascii_unix"
+    And the client is in passive mode
+    When the client successfully gets text "ascii_unix"
+    Then the local file "ascii_unix" should match the remote file
+
+  Scenario: Path outside tree
+    Given a successful login
+    When the client gets text "../foo"
+    Then the server returns an access denied error
+
+  Scenario: Missing file
+    Given a successful login
+    When the client gets text "foo"
+    Then the server returns a no such file error
+
+  Scenario: Not logged in
+    Given a successful connection
+    When the client gets text "foo"
+    Then the server returns a not logged in error
+
+  Scenario: Missing path
+    Given a successful login
+    When the client gets with no path
+    Then the server returns a syntax error

data/features/list.feature

@@ -0,0 +1,77 @@
+Feature: List
+
+  As a client
+  I want to list files
+  So that I can see what file to transfer
+
+  Scenario: List implicit
+    Given a successful login
+    And the server has file "foo"
+    And the server has file "bar"
+    When the client lists the directory
+    Then the file list should be in long form
+    And the file list should contain "foo"
+    And the file list should contain "bar"
+
+  Scenario: List root
+    Given a successful login
+    And the server has file "foo"
+    And the server has file "bar"
+    When the client lists the directory "/"
+    Then the file list should be in long form
+    And the file list should contain "foo"
+    And the file list should contain "bar"
+
+  Scenario: List subdir
+    Given a successful login
+    And the server has file "subdir/foo"
+    When the client lists the directory "subdir"
+    Then the file list should be in long form
+    And the file list should contain "foo"
+
+  Scenario: List glob
+    Given a successful login
+    And the server has file "foo"
+    And the server has file "bar"
+    When the client lists the directory "f*"
+    Then the file list should be in long form
+    And the file list should contain "foo"
+    And the file list should not contain "bar"
+
+  Scenario: Passive
+    Given a successful login
+    And the server has file "foo"
+    And the server has file "bar"
+    And the client is in passive mode
+    When the client lists the directory
+    Then the file list should be in long form
+    And the file list should contain "foo"
+    And the file list should contain "bar"
+
+  Scenario: TLS
+    pending "TLS not supported in active mode (see README)"
+
+  Scenario: TLS, Passive
+    Given a successful login with TLS
+    And the server has file "foo"
+    And the server has file "bar"
+    And the client is in passive mode
+    When the client lists the directory
+    Then the file list should be in long form
+    And the file list should contain "foo"
+    And the file list should contain "bar"
+
+  Scenario: Path outside tree
+    Given a successful login
+    When the client lists the directory ".."
+    Then the server returns an access denied error
+
+  Scenario: Missing file
+    Given a successful login
+    When the client lists the directory "missing/file"
+    Then the server returns a no such file error
+
+  Scenario: Not logged in
+    Given a successful connection
+    When the client lists the directory
+    Then the server returns a not logged in error

data/features/login.feature

@@ -0,0 +1,54 @@
+Feature: Login
+
+  As a client
+  I want to log in
+  So that I can transfer files
+
+  Scenario: Normal connection
+    Given a successful login
+    Then the server returns no error
+    And the client should be logged in
+
+  Scenario: Bad user
+    Given the server is started
+    And the client connects
+    When the client logs in with a bad user
+    Then the server returns a login incorrect error
+    And the client should not be logged in
+
+  Scenario: Bad password
+    Given a successful connection
+    When the client logs in with a bad password
+    Then the server returns a login incorrect error
+    And the client should not be logged in
+
+  Scenario: Already logged in
+    Given a successful login
+    When the client logs in
+    Then the server returns a bad sequence error
+    And the client should be logged in
+
+  Scenario: PASS when already logged in
+    Given a successful login
+    When the client sends a password
+    Then the server returns a bad sequence error
+
+  Scenario: PASS after failed login
+    Given a failed login
+    When the client sends a password
+    Then the server returns a bad sequence error
+
+  Scenario: PASS without USER
+    Given a successful connection
+    And the client sends a password
+    Then the server returns a bad sequence error
+
+  Scenario: PASS without parameter
+    Given a successful connection
+    And the client sends a password with no parameter
+    Then the server returns a syntax error
+
+  Scenario: USRE without parameter
+    Given a successful connection
+    And the client sends a user with no parameter
+    Then the server returns a syntax error