files.com 1.1.49 → 1.1.51

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 62ffe766397a8a89cc19a752a643c1c441a3fb701ab6b51866fdf2fb2a165ca4
-  data.tar.gz: eca84037c412e2e99723b2138cac95553311b81d52ff9dc2b3ebbc7dfea03a7b
+  metadata.gz: c8bd9cc3feb73431ee538e9295167cdebb8ce110bf18ee89ef2c8b163efb881b
+  data.tar.gz: 858411d5c41eebb73365462ca7c4816a20a586b1270b75391fce1c7d692bd12e
 SHA512:
-  metadata.gz: f56e2155cc61b60d2e18108b14b239436246cb7309c53d86340782597c9ad9f86f54f86d2bece6106ec6f6781b785c4c5b020c54b2fa03d2ffeefe41674a165a
-  data.tar.gz: 28595ea44b467bfc32ca25d0a4dc2d51040573da41823e1285dd819e05d26c3e9375f204556c4d5dcb4f307761d2c518ca194ce3b2c54e72a4ab828a82534d42
+  metadata.gz: 9775894e1107eba82c28bda7d817ce175550dfcdfe0d085b9692a39e182485eb583798cb120918da878ad06eb10eb8f0ed21b75d338932a17bd69a4dad0e1018
+  data.tar.gz: 958e5c54dbdf03f378c37f88a3c99a171c954872ed54233f4a93d74e43de3881a4010c7fb4ca8003eacf4ca361303e160e2995a231fa58ff17fdbbfdee909a48

data/_VERSION

@@ -1 +1 @@
-1.1.49
+1.1.51

data/docs/site.md

@@ -169,6 +169,7 @@
   "sftp_host_key_type": "default",
   "active_sftp_host_key_id": 1,
   "sftp_insecure_ciphers": true,
+  "sftp_insecure_diffie_hellman": true,
   "sftp_user_root_enabled": true,
   "sharing_enabled": true,
   "show_request_access_link": true,
@@ -391,7 +392,8 @@
 * `sftp_enabled` (boolean): Is SFTP enabled?
 * `sftp_host_key_type` (string): Sftp Host Key Type
 * `active_sftp_host_key_id` (int64): Id of the currently selected custom SFTP Host Key
-* `sftp_insecure_ciphers` (boolean): Are Insecure Ciphers allowed for SFTP?  Note:  Setting TLS Disabled -> True will always allow insecure ciphers for SFTP as well.  Enabling this is insecure.
+* `sftp_insecure_ciphers` (boolean): If true, we will allow weak and known insecure ciphers to be used for SFTP connections.  Enabling this setting severly weakens the security of your site and it is not recommend, except as a last resort for compatibility.
+* `sftp_insecure_diffie_hellman` (boolean): If true, we will allow weak Diffie Hellman parameters to be used within ciphers for SFTP that are otherwise on our secure list.  This has the effect of making the cipher weaker than our normal threshold for security, but is required to support certain legacy or broken SSH and MFT clients.  Enabling this weakens security, but not nearly as much as enabling the full `sftp_insecure_ciphers` option.
 * `sftp_user_root_enabled` (boolean): Use user FTP roots also for SFTP?
 * `sharing_enabled` (boolean): Allow bundle creation
 * `show_request_access_link` (boolean): Show request access link for users without access?  Currently unused.
@@ -407,7 +409,7 @@
 * `ssl_required` (boolean): Is SSL required?  Disabling this is insecure.
 * `subdomain` (string): Site subdomain
 * `switch_to_plan_date` (date-time): If switching plans, when does the new plan take effect?
-* `tls_disabled` (boolean): Are Insecure TLS and SFTP Ciphers allowed?  Enabling this is insecure.
+* `tls_disabled` (boolean): DO NOT ENABLE. This setting allows TLSv1.0 and TLSv1.1 to be used on your site.  We intend to remove this capability entirely in early 2024.  If set, the `sftp_insecure_ciphers` flag will be automatically set to true.
 * `trial_days_left` (int64): Number of days left in trial
 * `trial_until` (date-time): When does this Site trial expire?
 * `use_provided_modified_at` (boolean): Allow uploaders to set `provided_modified_at` for uploaded files?
@@ -490,6 +492,7 @@ Files::Site.update(
   ssl_required: true, 
   tls_disabled: true, 
   sftp_insecure_ciphers: true, 
+  sftp_insecure_diffie_hellman: true, 
   disable_files_certificate_generation: true, 
   user_lockout: true, 
   user_lockout_tries: 1, 
@@ -633,8 +636,9 @@ Files::Site.update(
 * `left_navigation_visibility` (object): Visibility settings for account navigation
 * `session_expiry` (double): Session expiry in hours
 * `ssl_required` (boolean): Is SSL required?  Disabling this is insecure.
-* `tls_disabled` (boolean): Are Insecure TLS and SFTP Ciphers allowed?  Enabling this is insecure.
-* `sftp_insecure_ciphers` (boolean): Are Insecure Ciphers allowed for SFTP?  Note:  Setting TLS Disabled -> True will always allow insecure ciphers for SFTP as well.  Enabling this is insecure.
+* `tls_disabled` (boolean): DO NOT ENABLE. This setting allows TLSv1.0 and TLSv1.1 to be used on your site.  We intend to remove this capability entirely in early 2024.  If set, the `sftp_insecure_ciphers` flag will be automatically set to true.
+* `sftp_insecure_ciphers` (boolean): If true, we will allow weak and known insecure ciphers to be used for SFTP connections.  Enabling this setting severly weakens the security of your site and it is not recommend, except as a last resort for compatibility.
+* `sftp_insecure_diffie_hellman` (boolean): If true, we will allow weak Diffie Hellman parameters to be used within ciphers for SFTP that are otherwise on our secure list.  This has the effect of making the cipher weaker than our normal threshold for security, but is required to support certain legacy or broken SSH and MFT clients.  Enabling this weakens security, but not nearly as much as enabling the full `sftp_insecure_ciphers` option.
 * `disable_files_certificate_generation` (boolean): If set, Files.com will not set the CAA records required to generate future SSL certificates for this domain.
 * `user_lockout` (boolean): Will users be locked out after incorrect login attempts?
 * `user_lockout_tries` (int64): Number of login tries within `user_lockout_within` hours before users are locked out

data/docs/snapshot.md

@@ -69,6 +69,19 @@ Files::Snapshot.create(
 * `paths` (array(string)): An array of paths to add to the snapshot.
 
 
+---
+
+## Finalize Snapshot
+
+```
+Files::Snapshot.finalize(id)
+```
+
+### Parameters
+
+* `id` (int64): Required - Snapshot ID.
+
+
 ---
 
 ## Update Snapshot
@@ -101,6 +114,21 @@ Files::Snapshot.delete(id)
 * `id` (int64): Required - Snapshot ID.
 
 
+---
+
+## Finalize Snapshot
+
+```
+snapshot = Files::Snapshot.list.first
+
+snapshot.finalize
+```
+
+### Parameters
+
+* `id` (int64): Required - Snapshot ID.
+
+
 ---
 
 ## Update Snapshot

data/lib/files.com/errors.rb

@@ -156,6 +156,7 @@ module Files
   class UserNotFoundError < NotFoundError; end
 
   class ProcessingFailureError < APIError; end
+  class AlreadyCompletedError < ProcessingFailureError; end
   class AutomationCannotBeRunManuallyError < ProcessingFailureError; end
   class BundleOnlyAllowsPreviewsError < ProcessingFailureError; end
   class BundleOperationRequiresSubfolderError < ProcessingFailureError; end

data/lib/files.com/models/site.rb

@@ -599,11 +599,16 @@ module Files
       @attributes[:active_sftp_host_key_id]
     end
 
-    # boolean - Are Insecure Ciphers allowed for SFTP?  Note:  Setting TLS Disabled -> True will always allow insecure ciphers for SFTP as well.  Enabling this is insecure.
+    # boolean - If true, we will allow weak and known insecure ciphers to be used for SFTP connections.  Enabling this setting severly weakens the security of your site and it is not recommend, except as a last resort for compatibility.
     def sftp_insecure_ciphers
       @attributes[:sftp_insecure_ciphers]
     end
 
+    # boolean - If true, we will allow weak Diffie Hellman parameters to be used within ciphers for SFTP that are otherwise on our secure list.  This has the effect of making the cipher weaker than our normal threshold for security, but is required to support certain legacy or broken SSH and MFT clients.  Enabling this weakens security, but not nearly as much as enabling the full `sftp_insecure_ciphers` option.
+    def sftp_insecure_diffie_hellman
+      @attributes[:sftp_insecure_diffie_hellman]
+    end
+
     # boolean - Use user FTP roots also for SFTP?
     def sftp_user_root_enabled
       @attributes[:sftp_user_root_enabled]
@@ -679,7 +684,7 @@ module Files
       @attributes[:switch_to_plan_date]
     end
 
-    # boolean - Are Insecure TLS and SFTP Ciphers allowed?  Enabling this is insecure.
+    # boolean - DO NOT ENABLE. This setting allows TLSv1.0 and TLSv1.1 to be used on your site.  We intend to remove this capability entirely in early 2024.  If set, the `sftp_insecure_ciphers` flag will be automatically set to true.
     def tls_disabled
       @attributes[:tls_disabled]
     end
@@ -830,8 +835,9 @@ module Files
     #   left_navigation_visibility - object - Visibility settings for account navigation
     #   session_expiry - double - Session expiry in hours
     #   ssl_required - boolean - Is SSL required?  Disabling this is insecure.
-    #   tls_disabled - boolean - Are Insecure TLS and SFTP Ciphers allowed?  Enabling this is insecure.
-    #   sftp_insecure_ciphers - boolean - Are Insecure Ciphers allowed for SFTP?  Note:  Setting TLS Disabled -> True will always allow insecure ciphers for SFTP as well.  Enabling this is insecure.
+    #   tls_disabled - boolean - DO NOT ENABLE. This setting allows TLSv1.0 and TLSv1.1 to be used on your site.  We intend to remove this capability entirely in early 2024.  If set, the `sftp_insecure_ciphers` flag will be automatically set to true.
+    #   sftp_insecure_ciphers - boolean - If true, we will allow weak and known insecure ciphers to be used for SFTP connections.  Enabling this setting severly weakens the security of your site and it is not recommend, except as a last resort for compatibility.
+    #   sftp_insecure_diffie_hellman - boolean - If true, we will allow weak Diffie Hellman parameters to be used within ciphers for SFTP that are otherwise on our secure list.  This has the effect of making the cipher weaker than our normal threshold for security, but is required to support certain legacy or broken SSH and MFT clients.  Enabling this weakens security, but not nearly as much as enabling the full `sftp_insecure_ciphers` option.
     #   disable_files_certificate_generation - boolean - If set, Files.com will not set the CAA records required to generate future SSL certificates for this domain.
     #   user_lockout - boolean - Will users be locked out after incorrect login attempts?
     #   user_lockout_tries - int64 - Number of login tries within `user_lockout_within` hours before users are locked out

data/lib/files.com/models/snapshot.rb

@@ -72,6 +72,17 @@ module Files
       @attributes[:paths] = value
     end
 
+    # Finalize Snapshot
+    def finalize(params = {})
+      params ||= {}
+      params[:id] = @attributes[:id]
+      raise MissingParameterError.new("Current object doesn't have a id") unless @attributes[:id]
+      raise InvalidParameterError.new("Bad parameter: id must be an Integer") if params[:id] and !params[:id].is_a?(Integer)
+      raise MissingParameterError.new("Parameter missing: id") unless params[:id]
+
+      Api.send_request("/snapshots/#{@attributes[:id]}/finalize", :post, params, @options)
+    end
+
     # Parameters:
     #   expires_at - string - When the snapshot expires.
     #   name - string - A name for the snapshot.
@@ -160,6 +171,17 @@ module Files
       Snapshot.new(response.data, options)
     end
 
+    # Finalize Snapshot
+    def self.finalize(id, params = {}, options = {})
+      params ||= {}
+      params[:id] = id
+      raise InvalidParameterError.new("Bad parameter: id must be an Integer") if params[:id] and !params[:id].is_a?(Integer)
+      raise MissingParameterError.new("Parameter missing: id") unless params[:id]
+
+      Api.send_request("/snapshots/#{params[:id]}/finalize", :post, params, options)
+      nil
+    end
+
     # Parameters:
     #   expires_at - string - When the snapshot expires.
     #   name - string - A name for the snapshot.

data/lib/files.com/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Files
-  VERSION = "1.1.49"
+  VERSION = "1.1.51"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: files.com
 version: !ruby/object:Gem::Version
-  version: 1.1.49
+  version: 1.1.51
 platform: ruby
 authors:
 - files.com
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2024-04-22 00:00:00.000000000 Z
+date: 2024-04-23 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: addressable