ftpd 2.0.1 → 2.0.2

data/features/example/read_only.feature

@@ -1,63 +0,0 @@
-Feature: Example
-
-  As a programmer
-  I want to start a read-only server
-  So that nobody can modify the file system I expose
-
-  Background:
-    Given the example has argument "--read-only"
-    And the example server is started
-
-  Scenario: Fetch README
-    Given a successful login
-    When the client successfully gets text "README"
-    Then the local file "README" should match the remote file
-
-  Scenario: Fetch README
-    Given a successful login
-    When the client successfully gets text "README"
-    Then the local file "README" should match the remote file
-
-  Scenario: List
-    Given a successful login
-    When the client successfully lists the directory
-    Then the file list should be in long form
-    And the file list should contain "README"
-
-  Scenario: Name List
-    Given a successful login
-    When the client successfully name-lists the directory
-    Then the file list should be in short form
-    And the file list should contain "README"
-
-  Scenario: Put
-    Given a successful login
-    And the client has file "foo"
-    When the client puts text "foo"
-    Then the server returns an unimplemented command error
-
-  Scenario: Put unique
-    Given a successful login
-    And the client has file "foo"
-    When the client stores unique "foo"
-    Then the server returns an unimplemented command error
-
-  Scenario: Delete
-    Given a successful login
-    When the client deletes "README"
-    Then the server returns an unimplemented command error
-
-  Scenario: Mkdir
-    Given a successful login
-    When the client makes directory "foo"
-    Then the server returns an unimplemented command error
-
-  Scenario: Rename
-    Given a successful login
-    When the client renames "README" to "foo"
-    Then the server returns an unimplemented command error
-
-  Scenario: Rmdir
-    Given a successful login
-    When the client removes directory "foo"
-    Then the server returns an unimplemented command error

data/features/example/step_definitions/example_server.rb

@@ -1,13 +0,0 @@
-# frozen_string_literal: true
-
-def example_args
-  @example_args ||= []
-end
-
-Given /^the example has argument "(.*?)"$/ do |arg|
-  example_args << arg
-end
-
-Given /^the example server is started$/ do
-  @server = ExampleServer.new(example_args)
-end

data/features/ftp_server/abort.feature

@@ -1,13 +0,0 @@
-Feature: Abort
-
-  As a client
-  I want to know this command is not supported
-  So that I can avoid using it
-
-  Background:
-    Given the test server is started
-
-  Scenario: Unimplemented
-    Given a successful connection
-    When the client sends command "ABOR"
-    Then the server returns an unimplemented command error

data/features/ftp_server/allo.feature

@@ -1,33 +0,0 @@
-Feature: ALLO
-
-  As a client
-  I want to reserve file system space
-  So that my put will succeed
-
-  Background:
-    Given the test server is started
-
-  Scenario: With count
-    Given a successful login
-    When the client successfully sends "ALLO 1024"
-    Then the server returns a not necessary reply
-
-  Scenario: With count and record size
-    Given a successful login
-    When the client successfully sends "ALLO 1024 R 128"
-    Then the server returns a not necessary reply
-
-  Scenario: Not logged in
-    Given a successful connection
-    When the client sends "ALLO 1024"
-    Then the server returns a not logged in error
-
-  Scenario: Missing argument
-    Given a successful login
-    When the client sends "ALLO"
-    Then the server returns a syntax error
-
-  Scenario: Invalid argument
-    Given a successful login
-    When the client sends "ALLO XYZ"
-    Then the server returns a syntax error

data/features/ftp_server/append.feature

@@ -1,94 +0,0 @@
-Feature: Append
-
-  As a client
-  I want to append to a file
-  Because it is a log
-
-  Background:
-    Given the test server is started
-
-  Scenario: ASCII file with *nix line endings
-    Given a successful login
-    And the server has file "foo"
-    And the client has file "ascii_unix"
-    When the client successfully appends text "ascii_unix" onto "foo"
-    Then the remote file "foo" should match "foo" + "ascii_unix"
-
-  Scenario: ASCII file with windows line endings
-    Given a successful login
-    And the server has file "foo"
-    And the client has file "ascii_windows"
-    When the client successfully appends text "ascii_windows" onto "foo"
-    Then the remote file "foo" should match "foo" + "ascii_unix"
-
-  Scenario: Binary file
-    Given a successful login
-    And the server has file "foo"
-    And the client has file "binary"
-    When the client successfully appends binary "binary" onto "foo"
-    Then the remote file "foo" should match "foo" + "binary"
-
-  Scenario: Passive
-    Given a successful login
-    And the server has file "foo"
-    And the client has file "binary"
-    And the client is in passive mode
-    When the client successfully appends binary "binary" onto "foo"
-    Then the remote file "foo" should match "foo" + "binary"
-
-  Scenario: Destination missing
-    Given a successful login
-    And the client has file "binary"
-    When the client successfully appends binary "binary" onto "foo"
-    Then the remote file "foo" should match "binary"
-
-  Scenario: Subdir
-    Given a successful login
-    And the server has file "subdir/foo"
-    And the client has file "binary"
-    When the client successfully appends binary "binary" onto "subdir/foo"
-    Then the remote file "subdir/foo" should match "foo" + "binary"
-
-  Scenario: Non-root working directory
-    Given a successful login
-    And the server has file "subdir/foo"
-    And the client has file "binary"
-    And the client successfully cd's to "subdir"
-    When the client successfully appends binary "binary" onto "foo"
-    Then the remote file "subdir/foo" should match "foo" + "binary"
-
-  Scenario: Access denied
-    Given a successful login
-    And the client has file "foo"
-    When the client appends binary "foo" onto "forbidden"
-    Then the server returns an access denied error
-
-  Scenario: Missing directory
-    Given a successful login
-    And the client has file "binary"
-    When the client appends binary "binary" onto "subdir/foo"
-    Then the server returns a not found error
-
-  Scenario: Not logged in
-    Given a successful connection
-    And the client has file "foo"
-    When the client appends binary "foo" onto "foo"
-    Then the server returns a not logged in error
-
-  Scenario: Missing path
-    Given a successful login
-    When the client sends "APPE"
-    Then the server returns a syntax error
-
-  Scenario: File system error
-    Given a successful login
-    And the client has file "foo"
-    When the client appends text "foo" onto "unable"
-    Then the server returns an action not taken error
-
-  Scenario: Append not enabled
-    Given the test server lacks append
-    And a successful login
-    And the client has file "foo"
-    When the client appends text "foo" onto "bar"
-    Then the server returns an unimplemented command error

data/features/ftp_server/cdup.feature

@@ -1,36 +0,0 @@
-Feature: Change Directory
-
-  As a client
-  I want to change to the parent directory
-
-  Background:
-    Given the test server is started
-
-  Scenario: From subdir
-    Given a successful login
-    And the server has directory "subdir"
-    And the client successfully cd's to "subdir"
-    When the client successfully cd's up
-    Then the current directory should be "/"
-
-  Scenario: From root
-    Given a successful login
-    When the client successfully cd's up
-    Then the current directory should be "/"
-
-  Scenario: XCUP
-    Given a successful login
-    And the server has directory "subdir"
-    And the client successfully cd's to "subdir"
-    When the client successfully sends "XCUP"
-    Then the current directory should be "/"
-
-  Scenario: With argument
-    Given a successful login
-    When the client sends "CDUP abc"
-    Then the server returns a syntax 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/ftp_server/command_errors.feature

@@ -1,13 +0,0 @@
-Feature: Command Errors
-
-  As a client
-  I want good error messages
-  So that I can figure out what went wrong
-
-  Background:
-    Given the test server is started
-
-  Scenario: Unknown command
-    Given a successful connection
-    When the client sends command "foo"
-    Then the server returns a command unrecognized error

data/features/ftp_server/concurrent_sessions.feature

@@ -1,14 +0,0 @@
-Feature: Concurrent Sessions
-
-  As a client
-  I want to start a session when there is another session
-  So that my session doesn't have to wait on the other
-
-  Background:
-    Given the test server is started
-
-  Scenario: Stream
-    Given a successful login
-    And the server has file "ascii_unix"
-    And the second client connects and logs in
-    Then the second client successfully does nothing

data/features/ftp_server/delay_after_failed_login.feature

@@ -1,23 +0,0 @@
-Feature: Delay After Failed Login
-
-  As an administrator
-  I want to make brute force attacks less efficient
-  So that an attacker doesn't gain access
-
-  Scenario: Failed login attempts
-    Given the test server has a failed login delay of 0.2 seconds
-    And the test server is started
-    Given the client connects
-    And the client logs in with bad user
-    And the client logs in with bad user
-    And the client logs in
-    Then it should take at least 0.4 seconds
-
-  Scenario: Failed login attempts
-    Given the test server has a failed login delay of 0.0 seconds
-    And the test server is started
-    Given the client connects
-    And the client logs in with bad user
-    And the client logs in with bad user
-    And the client logs in
-    Then it should take less than 0.4 seconds

data/features/ftp_server/delete.feature

@@ -1,60 +0,0 @@
-Feature: Delete
-
-  As a client
-  I want to delete files
-  So that nobody can fetch them from the server
-
-  Background:
-    Given the test server is started
-
-  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"
-
-  Scenario: Delete a file in a subdirectory
-    Given a successful login
-    And the server has file "foo/bar"
-    When the client successfully deletes "foo/bar"
-    Then the server should not have file "foo/bar"
-
-  Scenario: Change current directory
-    Given a successful login
-    And the server has file "foo/bar"
-    And the client successfully cd's to "foo"
-    When the client successfully deletes "bar"
-    Then the server should not have file "foo/bar"
-
-  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: not found
-    Given a successful login
-    When the client deletes "foo"
-    Then the server returns a not found error
-
-  Scenario: Access denied
-    Given a successful login
-    When the client deletes "forbidden"
-    Then the server returns an access denied error
-
-  Scenario: File system error
-    Given a successful login
-    When the client deletes "unable"
-    Then the server returns an action not taken error
-
-  Scenario: Not logged in
-    Given a successful connection
-    When the client deletes "foo"
-    Then the server returns a not logged in error
-
-  Scenario: Delete not enabled
-    Given the test server lacks delete
-    And a successful login
-    And the server has file "foo"
-    When the client deletes "foo"
-    Then the server returns an unimplemented command error

data/features/ftp_server/directory_navigation.feature

@@ -1,59 +0,0 @@
-Feature: Change Directory
-
-  As a client
-  I want to change the current directory
-  So that I can use shorter paths
-
-  Background:
-    Given the test server is started
-
-  Scenario: Down to subdir
-    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: Up from subdir
-    Given a successful login
-    And the server has file "subdir/bar"
-    And the client successfully cd's to "subdir"
-    When the client successfully cd's to ".."
-    Then the current directory should be "/"
-
-  Scenario: Up from root
-    Given a successful login
-    When the client successfully cd's to ".."
-    Then the current directory should be "/"
-
-  Scenario: XPWD
-    Given a successful login
-    And the server has directory "subdir"
-    When the client successfully cd's to "subdir"
-    Then the XPWD directory should be "/subdir"
-
-  Scenario: XCWD
-    Given a successful login
-    And the server has directory "subdir"
-    When the client successfully sends "XCWD subdir"
-    Then the current directory should be "/subdir"
-
-  Scenario: Change to file
-    Given a successful login
-    And the server has file "baz"
-    When the client cd's to "baz"
-    Then the server returns a not a directory error
-
-  Scenario: No such directory
-    Given a successful login
-    When the client cd's to "subdir"
-    Then the server returns a not found error
-
-  Scenario: Access denied
-    Given a successful login
-    When the client cd's to "forbidden"
-    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/ftp_server/disconnect_after_failed_logins.feature

@@ -1,25 +0,0 @@
-Feature: Disconnect After Failed Logins
-
-  As an administrator
-  I want to make brute force attacks less efficient
-  So that an attacker doesn't gain access
-
-  Scenario: Disconnected after maximum failed attempts
-    Given the test server has a max of 3 failed login attempts
-    And the test server is started
-    Given the client connects
-    And the client logs in with bad user
-    And the client logs in with bad user
-    When the client logs in with bad user
-    Then the server returns a server unavailable error
-    And the client should not be connected
-
-  Scenario: No maximum configured
-    Given the test server has no max failed login attempts
-    And the test server is started
-    Given the client connects
-    And the client logs in with bad user
-    And the client logs in with bad user
-    And the client logs in with bad user
-    Then the server returns a login incorrect error
-    And the client should be connected