files-com 1.6.38__py3-none-any.whl → 1.6.39__py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Potentially problematic release.

This version of files-com might be problematic. Click here for more details.

Files changed (8) hide show
  1. _VERSION +1 -1
  2. {files_com-1.6.38.dist-info → files_com-1.6.39.dist-info}/METADATA +1 -1
  3. {files_com-1.6.38.dist-info → files_com-1.6.39.dist-info}/RECORD +8 -8
  4. files_sdk/__init__.py +1 -1
  5. files_sdk/models/site.py +2 -2
  6. {files_com-1.6.38.dist-info → files_com-1.6.39.dist-info}/WHEEL +0 -0
  7. {files_com-1.6.38.dist-info → files_com-1.6.39.dist-info}/licenses/LICENSE +0 -0
  8. {files_com-1.6.38.dist-info → files_com-1.6.39.dist-info}/top_level.txt +0 -0
_VERSION CHANGED
@@ -1 +1 @@
1
- 1.6.38
1
+ 1.6.39
{files_com-1.6.38.dist-info → files_com-1.6.39.dist-info}/METADATA RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: files_com
3
- Version: 1.6.38
3
+ Version: 1.6.39
4
4
  Summary: Python bindings for the Files.com API
5
5
  License: MIT
6
6
  Requires-Python: >=3.5
{files_com-1.6.38.dist-info → files_com-1.6.39.dist-info}/RECORD RENAMED
@@ -1,7 +1,7 @@
1
1
  README.md,sha256=dJpTjuJA-JJIQ4CKgQhlbqyxanVatHk0RXgCD6KFl3A,28758
2
- _VERSION,sha256=2RtflCTAZElLJ5GC7rH9_xVHRFFuhvhHU6hd-34U1jc,7
3
- files_com-1.6.38.dist-info/licenses/LICENSE,sha256=ziANl9OTD-5-iE8XYIZNm6IYBDxOCHwQ-mdhci7lNew,1102
4
- files_sdk/__init__.py,sha256=zIBvgNC0ap6BWX6wkPUPj0qn7j8QCf68fUi3_iEv1rM,12884
2
+ _VERSION,sha256=hrDbMEYAx762iSyEdwBQQE_oh3CBwcpEmd1WBSJtkQg,7
3
+ files_com-1.6.39.dist-info/licenses/LICENSE,sha256=ziANl9OTD-5-iE8XYIZNm6IYBDxOCHwQ-mdhci7lNew,1102
4
+ files_sdk/__init__.py,sha256=S8Df5yppJydRMo51_yIlAG6BCjjf89OWMK-YwTEN91w,12884
5
5
  files_sdk/api.py,sha256=HOLk50HLQCbnHwnAr9OElQEWvdA_BABBSEvvFSt1S4A,1846
6
6
  files_sdk/api_client.py,sha256=cfFvm-o4Ao8SWADiJv7t7qnJfG_LJmWV3l6ALTC-Opo,11264
7
7
  files_sdk/error.py,sha256=lZKht6lYj9i99CzRbHschmdSs6T2Y51-YrZX_5Y_o7A,64945
@@ -94,7 +94,7 @@ files_sdk/models/sftp_host_key.py,sha256=3r5noHhRg-Hn3TLGBUDQYayKIw_Dn5waB9YmGSf
94
94
  files_sdk/models/share_group.py,sha256=rw-W2x5XFBPc48rvazaro28HfjOli885417i702Mowc,9066
95
95
  files_sdk/models/share_group_member.py,sha256=m0BUE4AhClJIoaV-_kU0yryCOwQ5EloZlyHQ4WaCVdU,1248
96
96
  files_sdk/models/siem_http_destination.py,sha256=BDExKltNMH8q3ZoKJO_fBRtjVliqzjnj1KHEKycXiCw,49945
97
- files_sdk/models/site.py,sha256=XqYd3bFupgLejXchndaz4WicIq41E_xBkZUmd0RArPw,69364
97
+ files_sdk/models/site.py,sha256=VqYKbKsWa6S9yg7R-NQClWbStBXodH9FEL8jxEbiOFI,69580
98
98
  files_sdk/models/snapshot.py,sha256=zmdQWKR8EhUkF1mFQHFzWfreaEVXG1p_jEtmY4j3cKA,9840
99
99
  files_sdk/models/sso_strategy.py,sha256=vWNCPfot8z15xUhAoFsS52W-1vg8IpKIqAALZ6pBwd0,9112
100
100
  files_sdk/models/status.py,sha256=IIY3RiJ2RZ2yPByAAh8eIq_cgZFTj13eR4UpqHTANQI,1363
@@ -112,7 +112,7 @@ files_sdk/models/user_request.py,sha256=ykA5Lq0MYB7qTDOMMFBuyKa_R_LgQwGVorC-q-6q
112
112
  files_sdk/models/user_sftp_client_use.py,sha256=VnOo3ll6fwSc8grG5ZqGK8o3grYKg5P9b5B_hGS4vCs,2827
113
113
  files_sdk/models/web_dav_action_log.py,sha256=uMTIkTgSpW5mgKAEWnCmI4U5eqcAL2g8OHqB-lBir3A,76424
114
114
  files_sdk/models/webhook_test.py,sha256=AWGH8ULsgltBJL2YtTYGnAJ80cCVekrjZ2sUP0UlWgc,5018
115
- files_com-1.6.38.dist-info/METADATA,sha256=51gZygSRt4p9pmy94osHflRx4zcGZSvvbUU80GP3MKU,29050
116
- files_com-1.6.38.dist-info/WHEEL,sha256=_zCd3N1l69ArxyTb8rzEoP9TpbYXkqRFSNOD5OuxnTs,91
117
- files_com-1.6.38.dist-info/top_level.txt,sha256=p_2P-gluT_8boeXQNixTP3x-tFd1-la2NedKOiln21I,10
118
- files_com-1.6.38.dist-info/RECORD,,
115
+ files_com-1.6.39.dist-info/METADATA,sha256=ZevGNUhFbZSZLYVd8L9PsY1QKNDZRb-7sia_oXAxWc4,29050
116
+ files_com-1.6.39.dist-info/WHEEL,sha256=_zCd3N1l69ArxyTb8rzEoP9TpbYXkqRFSNOD5OuxnTs,91
117
+ files_com-1.6.39.dist-info/top_level.txt,sha256=p_2P-gluT_8boeXQNixTP3x-tFd1-la2NedKOiln21I,10
118
+ files_com-1.6.39.dist-info/RECORD,,
files_sdk/__init__.py CHANGED
@@ -223,7 +223,7 @@ session_id = None
223
223
  source_ip = None
224
224
  base_url = "https://app.files.com"
225
225
  base_path = "api/rest/v1"
226
- version = "1.6.38"
226
+ version = "1.6.39"
227
227
 
228
228
  __version__ = version
229
229
 
files_sdk/models/site.py CHANGED
@@ -159,7 +159,7 @@ class Site:
159
159
  "ssl_required": None, # boolean - Is SSL required? Disabling this is insecure.
160
160
  "subdomain": None, # string - Site subdomain
161
161
  "switch_to_plan_date": None, # date-time - If switching plans, when does the new plan take effect?
162
- "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.
162
+ "tls_disabled": None, # 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.
163
163
  "trial_days_left": None, # int64 - Number of days left in trial
164
164
  "trial_until": None, # date-time - When does this Site trial expire?
165
165
  "use_dedicated_ips_for_smtp": None, # boolean - If using custom SMTP, should we use dedicated IPs to deliver emails?
@@ -266,7 +266,7 @@ def get_usage(params=None, options=None):
266
266
  # migrate_remote_server_sync_to_sync - boolean - If true, we will migrate all remote server syncs to the new Sync model.
267
267
  # session_expiry - double - Session expiry in hours
268
268
  # ssl_required - boolean - Is SSL required? Disabling this is insecure.
269
- # 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.
269
+ # 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.
270
270
  # 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.
271
271
  # 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.
272
272
  # disable_files_certificate_generation - boolean - If set, Files.com will not set the CAA records required to generate future SSL certificates for this domain.