files.com 1.1.697 → 1.1.699

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a893aaa8b607be5cdc71b0e9a2d2857cf0ba59b85ac6ae8f7772895169096d61
-  data.tar.gz: 11c31bb97e760ed51071fb8ca96cd93e2fde8e56685ad23e630fe48254564cf4
+  metadata.gz: b1b9be22ebb74b65e03b96b718b6f2e0406f0472e818138613807cd2c8cb9f8b
+  data.tar.gz: 92656a3a1cf3e8ef7ec96124ff045bcfead5e12bf83dcb26a8e935c4741c0eac
 SHA512:
-  metadata.gz: b955a095e6b440763b00bb6edb076058038ebaa10e257e6bed90a88c7eb0ae97687af338af9cfb7cf812a9dead1d84488149dd5f09b6ba5bbf44bf5e466ded95
-  data.tar.gz: 22e68d3c932d53c294dc473ff6c736d9801bf3ff810e40d653e5e216ef5751a3988bffba9e2c24829ca1d9c5e8d71c441f3320c258464ea6c1551fa1afcd03e3
+  metadata.gz: eb2f9eabd5cdcd4e7b0a9399c900728ce0e657729e80dab10ba15bdb40a0efc4d630ae14568fab01762cde531fc450b4d739b3d4edb5be3615179c0fd0716c5a
+  data.tar.gz: b78256c26f8b5213d05c362514b3213fa3a7da4ebcb0f0a9e68dc51c55da3642fac03906891fd38d2c1d351728ae60e2c4f5d44e36eac23481e728ed8c9029af

data/_VERSION

@@ -1 +1 @@
-1.1.697
+1.1.699

data/docs/remote_server.md

@@ -69,6 +69,7 @@
   "files_agent_up_to_date": true,
   "files_agent_latest_version": "example",
   "files_agent_supports_push_updates": true,
+  "direct_transfer_available": true,
   "outbound_agent_id": 1,
   "filebase_bucket": "my-bucket",
   "filebase_access_key": "example",
@@ -149,6 +150,7 @@
 * `files_agent_up_to_date` (boolean): If true, the Files Agent is up to date.
 * `files_agent_latest_version` (string): Latest available Files Agent version
 * `files_agent_supports_push_updates` (boolean): Files Agent supports receiving push updates
+* `direct_transfer_available` (boolean): Whether the Files Agent Proxy recently validated a direct transfer connection. `true` means a direct connection was recently validated (actual availability can vary by client network), `false` means direct transfers are enabled but not currently available, and `null` means direct transfers are disabled or unsupported. Only provided for a connected Files Agent when showing a single Remote Server.
 * `outbound_agent_id` (int64): Route traffic to outbound on a files-agent
 * `filebase_bucket` (string): Filebase: Bucket name
 * `filebase_access_key` (string): Filebase: Access Key.

data/docs/site.md

@@ -94,6 +94,7 @@
   "domain_hsts_header": true,
   "domain_letsencrypt_chain": "example",
   "email": "john.doe@files.com",
+  "fedramp": true,
   "ftp_enabled": true,
   "reply_to_email": "jane.doe@files.com",
   "non_sso_groups_allowed": true,
@@ -434,6 +435,7 @@
 * `domain_hsts_header` (boolean): Send HSTS (HTTP Strict Transport Security) header when visitors access the site via a custom domain?
 * `domain_letsencrypt_chain` (string): Letsencrypt chain to use when registering SSL Certificate for domain. No longer used as of 2026.
 * `email` (email): Main email for this site
+* `fedramp` (boolean): Are FedRAMP security restrictions enabled for this site?
 * `ftp_enabled` (boolean): Is FTP enabled?
 * `reply_to_email` (email): Reply-to email for this site
 * `non_sso_groups_allowed` (boolean): If true, groups can be manually created / modified / deleted by Site Admins. Otherwise, groups can only be managed via your SSO provider.
@@ -631,6 +633,7 @@ Files::Site.update(
   sftp_insecure_ciphers: false, 
   sftp_insecure_diffie_hellman: false, 
   disable_files_certificate_generation: false, 
+  fedramp: false, 
   user_lockout: false, 
   user_lockout_tries: 1, 
   user_lockout_within: 1, 
@@ -812,6 +815,7 @@ Files::Site.update(
 * `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.
+* `fedramp` (boolean): Are FedRAMP security restrictions enabled for this site?
 * `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
 * `user_lockout_within` (int64): Number of hours for user lockout window

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

@@ -594,6 +594,15 @@ module Files
       @attributes[:files_agent_supports_push_updates] = value
     end
 
+    # boolean - Whether the Files Agent Proxy recently validated a direct transfer connection. `true` means a direct connection was recently validated (actual availability can vary by client network), `false` means direct transfers are enabled but not currently available, and `null` means direct transfers are disabled or unsupported. Only provided for a connected Files Agent when showing a single Remote Server.
+    def direct_transfer_available
+      @attributes[:direct_transfer_available]
+    end
+
+    def direct_transfer_available=(value)
+      @attributes[:direct_transfer_available] = value
+    end
+
     # int64 - Route traffic to outbound on a files-agent
     def outbound_agent_id
       @attributes[:outbound_agent_id]

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

@@ -381,6 +381,11 @@ module Files
       @attributes[:email]
     end
 
+    # boolean - Are FedRAMP security restrictions enabled for this site?
+    def fedramp
+      @attributes[:fedramp]
+    end
+
     # boolean - Is FTP enabled?
     def ftp_enabled
       @attributes[:ftp_enabled]
@@ -1039,6 +1044,7 @@ module Files
     #   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.
+    #   fedramp - boolean - Are FedRAMP security restrictions enabled for this site?
     #   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
     #   user_lockout_within - int64 - Number of hours for user lockout window

data/lib/files.com/version.rb

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

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: files.com
 version: !ruby/object:Gem::Version
-  version: 1.1.697
+  version: 1.1.699
 platform: ruby
 authors:
 - files.com
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2026-07-28 00:00:00.000000000 Z
+date: 2026-07-30 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: addressable