Files.com 1.4.45__tar.gz → 1.4.47__tar.gz

{Files.com-1.4.45 → Files.com-1.4.47}/Files.com.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 1.2
 Name: Files.com
-Version: 1.4.45
+Version: 1.4.47
 Summary: Python bindings for the Files.com API
 Home-page: UNKNOWN
 License: MIT

{Files.com-1.4.45 → Files.com-1.4.47}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 1.2
 Name: Files.com
-Version: 1.4.45
+Version: 1.4.47
 Summary: Python bindings for the Files.com API
 Home-page: UNKNOWN
 License: MIT

{Files.com-1.4.45 → Files.com-1.4.47}/files_sdk/__init__.py

@@ -193,7 +193,7 @@ the_api_key = ""
 session_id = None
 base_url = "https://app.files.com"
 base_path = "api/rest/v1"
-version = "1.4.45"
+version = "1.4.47"
 
 __version__ = version
 

{Files.com-1.4.45 → Files.com-1.4.47}/files_sdk/models/as2_partner.py

@@ -15,7 +15,7 @@ class As2Partner:
         "name": None,  # string - The partner's formal AS2 name.
         "uri": None,  # string - Public URI for sending AS2 message to.
         "server_certificate": None,  # string - Remote server certificate security setting
-        "mdn_validation_level": None,  # string - MDN Validation Level
+        "mdn_validation_level": None,  # string - MDN Validation Level controls how to evaluate message transfer success based on a partner's MDN response. NOTE: This setting does not affect MDN storage; all MDNs received from a partner are always stored. `none`: MDN is stored for informational purposes only, a successful HTTPS transfer is a successful AS2 transfer. `weak`: Inspect the MDN for MIC and Disposition only. `normal`: `weak` plus validate MDN signature matches body, `strict`: `normal` but do not allow signatures from self-signed or incorrectly purposed certificates.
         "enable_dedicated_ips": None,  # boolean - `true` if remote server only accepts connections from dedicated IPs
         "hex_public_certificate_serial": None,  # string - Serial of public certificate used for message security in hex format.
         "public_certificate_md5": None,  # string - MD5 hash of public certificate used for message security.

{Files.com-1.4.45 → Files.com-1.4.47}/files_sdk/models/site.py

@@ -128,7 +128,8 @@ class Site:
         "sftp_enabled": None,  # boolean - Is SFTP enabled?
         "sftp_host_key_type": None,  # string - Sftp Host Key Type
         "active_sftp_host_key_id": None,  # int64 - Id of the currently selected custom SFTP Host Key
-        "sftp_insecure_ciphers": None,  # 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": None,  # 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": None,  # 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": None,  # boolean - Use user FTP roots also for SFTP?
         "sharing_enabled": None,  # boolean - Allow bundle creation
         "show_request_access_link": None,  # boolean - Show request access link for users without access?  Currently unused.
@@ -144,7 +145,7 @@ class Site:
         "ssl_required": None,  # boolean - Is SSL required?  Disabling this is insecure.
         "subdomain": None,  # string - Site subdomain
         "switch_to_plan_date": None,  # date-time - If switching plans, when does the new plan take effect?
-        "tls_disabled": None,  # boolean - Are Insecure TLS and SFTP Ciphers allowed?  Enabling this is insecure.
+        "tls_disabled": None,  # 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": None,  # int64 - Number of days left in trial
         "trial_until": None,  # date-time - When does this Site trial expire?
         "use_provided_modified_at": None,  # boolean - Allow uploaders to set `provided_modified_at` for uploaded files?
@@ -241,8 +242,9 @@ def get_usage(params=None, options=None):
 #   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