files.com 1.1.302 → 1.1.304

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a7f79167aaa5c8c730a4262b6d77c4a2ff401fc5659c47ba044ce9f2ceef6158
-  data.tar.gz: e236d26bba6a097d7a21e766afce433e8e52364084feddf546a2d319232cfdc3
+  metadata.gz: 153496038068ea420584558acfd94d1e009da55b5f1fce648b124013e5bf34c6
+  data.tar.gz: b48616e026a5e3d7b07e4939817042b03e22081178012a018d1c59426662f4f1
 SHA512:
-  metadata.gz: 8757a060f171ef957da512457759aa3696e5281c555e562e0020636be1aca2fe7a55a87d5ab34ebda42c00b60441f507504efe5413389dd93496a4fb96f814d0
-  data.tar.gz: 5b1a85d8263ea7c82878b4d94e36aecc0480cbdf18cbbd8e45c4d9ae7c487a361bcb9a4aa8da416e705a94633974945e57f7e0aaf08def642145a1ac350950b8
+  metadata.gz: d6037d527897e51064f33880e58c70ea2ae5d50753d4ef097bca37ca057cbebedf1726c4cf024d5a4cb1416e45dd6983d9d71d20e5283c5ba50069f41618f85c
+  data.tar.gz: af2c2dd0cdf99d0cf1458b9f7689d085b8e547b640ac97d074a87223d356b7acc409b66fe743a4d11c81006c988c7a44680ab297c64aed4873872086d6e327a5

data/_VERSION

@@ -1 +1 @@
-1.1.302
+1.1.304

data/docs/site.md

@@ -171,7 +171,6 @@
     "site_id": 1,
     "ssl_required": true,
     "timeout_at": "2000-01-01T01:00:00Z",
-    "tls_disabled": false,
     "two_factor_setup_needed": false,
     "allowed_2fa_method_sms": true,
     "allowed_2fa_method_totp": true,
@@ -211,7 +210,6 @@
   "ssl_required": true,
   "subdomain": "mysite",
   "switch_to_plan_date": "2000-01-01T01:00:00Z",
-  "tls_disabled": true,
   "trial_days_left": 1,
   "trial_until": "2000-01-01T01:00:00Z",
   "use_dedicated_ips_for_smtp": true,
@@ -457,7 +455,6 @@
 * `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): This setting enables Legacy Support for Insecure Ciphers across SFTP and FTP.  See our documentation for more information.  Contrary to its name, this setting does not disable TLS (it used to do that a long time ago), but rather enables certain ciphers which are known to be insecure but required for broad MFT compatibility.
 * `trial_days_left` (int64): Number of days left in trial
 * `trial_until` (date-time): When does this Site trial expire?
 * `use_dedicated_ips_for_smtp` (boolean): If using custom SMTP, should we use dedicated IPs to deliver emails?
@@ -548,7 +545,6 @@ Files::Site.update(
   migrate_remote_server_sync_to_sync: false, 
   session_expiry: 1.0, 
   ssl_required: false, 
-  tls_disabled: false, 
   sftp_insecure_ciphers: false, 
   sftp_insecure_diffie_hellman: false, 
   disable_files_certificate_generation: false, 
@@ -709,7 +705,6 @@ Files::Site.update(
 * `migrate_remote_server_sync_to_sync` (boolean): If true, we will migrate all remote server syncs to the new Sync model.
 * `session_expiry` (double): Session expiry in hours
 * `ssl_required` (boolean): Is SSL required?  Disabling this is insecure.
-* `tls_disabled` (boolean): This setting enables Legacy Support for Insecure Ciphers across SFTP and FTP.  See our documentation for more information.  Contrary to its name, this setting does not disable TLS (it used to do that a long time ago), but rather enables certain ciphers which are known to be insecure but required for broad MFT compatibility.
 * `sftp_insecure_ciphers` (boolean): If true, we will allow weak and known insecure ciphers to be used for SFTP connections.  Enabling this setting severely 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.

data/docs/user_cipher_use.md

@@ -5,22 +5,24 @@
 ```
 {
   "id": 1,
+  "user_id": 1,
+  "username": "example",
   "protocol_cipher": "TLSv1.2; ECDHE-RSA-AES256-GCM-SHA384",
   "created_at": "2000-01-01T01:00:00Z",
   "insecure": true,
   "interface": "restapi",
-  "updated_at": "2000-01-01T01:00:00Z",
-  "user_id": 1
+  "updated_at": "2000-01-01T01:00:00Z"
 }
 ```
 
 * `id` (int64): UserCipherUse ID
+* `user_id` (int64): ID of the user who performed this access
+* `username` (string): Username of the user who performed this access
 * `protocol_cipher` (string): The protocol and cipher employed
 * `created_at` (date-time): The earliest recorded use of this combination of interface and protocol and cipher (for this user)
 * `insecure` (boolean): Is this cipher considered insecure?
 * `interface` (string): The interface accessed
 * `updated_at` (date-time): The most recent use of this combination of interface and protocol and cipher (for this user)
-* `user_id` (int64): ID of the user who performed this access
 
 
 ---

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

@@ -764,11 +764,6 @@ module Files
       @attributes[:switch_to_plan_date]
     end
 
-    # boolean - This setting enables Legacy Support for Insecure Ciphers across SFTP and FTP.  See our documentation for more information.  Contrary to its name, this setting does not disable TLS (it used to do that a long time ago), but rather enables certain ciphers which are known to be insecure but required for broad MFT compatibility.
-    def tls_disabled
-      @attributes[:tls_disabled]
-    end
-
     # int64 - Number of days left in trial
     def trial_days_left
       @attributes[:trial_days_left]
@@ -925,7 +920,6 @@ module Files
     #   migrate_remote_server_sync_to_sync - boolean - If true, we will migrate all remote server syncs to the new Sync model.
     #   session_expiry - double - Session expiry in hours
     #   ssl_required - boolean - Is SSL required?  Disabling this is insecure.
-    #   tls_disabled - boolean - This setting enables Legacy Support for Insecure Ciphers across SFTP and FTP.  See our documentation for more information.  Contrary to its name, this setting does not disable TLS (it used to do that a long time ago), but rather enables certain ciphers which are known to be insecure but required for broad MFT compatibility.
     #   sftp_insecure_ciphers - boolean - If true, we will allow weak and known insecure ciphers to be used for SFTP connections.  Enabling this setting severely 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.

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

@@ -14,6 +14,16 @@ module Files
       @attributes[:id]
     end
 
+    # int64 - ID of the user who performed this access
+    def user_id
+      @attributes[:user_id]
+    end
+
+    # string - Username of the user who performed this access
+    def username
+      @attributes[:username]
+    end
+
     # string - The protocol and cipher employed
     def protocol_cipher
       @attributes[:protocol_cipher]
@@ -39,11 +49,6 @@ module Files
       @attributes[:updated_at]
     end
 
-    # int64 - ID of the user who performed this access
-    def user_id
-      @attributes[:user_id]
-    end
-
     # Parameters:
     #   user_id - int64 - User ID. If provided, will return uses for this user.
     #   cursor - string - Used for pagination.  When a list request has more records available, cursors are provided in the response headers `X-Files-Cursor-Next` and `X-Files-Cursor-Prev`.  Send one of those cursor value here to resume an existing list from the next available record.  Note: many of our SDKs have iterator methods that will automatically handle cursor-based pagination.

data/lib/files.com/version.rb

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

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: files.com
 version: !ruby/object:Gem::Version
-  version: 1.1.302
+  version: 1.1.304
 platform: ruby
 authors:
 - files.com
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2025-07-22 00:00:00.000000000 Z
+date: 2025-07-24 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: addressable