files.com 1.2.41 → 1.2.43

Sign up to get free protection for your applications and to get access to all the features.
package/_VERSION CHANGED
@@ -1 +1 @@
1
- 1.2.41
1
+ 1.2.43
package/docs/Errors.md CHANGED
@@ -149,6 +149,7 @@ These errors are derived from the error groups listed above.
149
149
  ### NotFound_PlanNotFoundError
150
150
  ### NotFound_SiteNotFoundError
151
151
  ### NotFound_UserNotFoundError
152
+ ### ProcessingFailure_AlreadyCompletedError
152
153
  ### ProcessingFailure_AutomationCannotBeRunManuallyError
153
154
  ### ProcessingFailure_BundleOnlyAllowsPreviewsError
154
155
  ### ProcessingFailure_BundleOperationRequiresSubfolderError
@@ -169,6 +169,7 @@
169
169
  "sftp_host_key_type": "default",
170
170
  "active_sftp_host_key_id": 1,
171
171
  "sftp_insecure_ciphers": true,
172
+ "sftp_insecure_diffie_hellman": true,
172
173
  "sftp_user_root_enabled": true,
173
174
  "sharing_enabled": true,
174
175
  "show_request_access_link": true,
@@ -391,7 +392,8 @@
391
392
  * `sftp_enabled` (boolean): Is SFTP enabled?
392
393
  * `sftp_host_key_type` (string): Sftp Host Key Type
393
394
  * `active_sftp_host_key_id` (int64): Id of the currently selected custom SFTP Host Key
394
- * `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.
395
+ * `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.
396
+ * `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.
395
397
  * `sftp_user_root_enabled` (boolean): Use user FTP roots also for SFTP?
396
398
  * `sharing_enabled` (boolean): Allow bundle creation
397
399
  * `show_request_access_link` (boolean): Show request access link for users without access? Currently unused.
@@ -407,7 +409,7 @@
407
409
  * `ssl_required` (boolean): Is SSL required? Disabling this is insecure.
408
410
  * `subdomain` (string): Site subdomain
409
411
  * `switch_to_plan_date` (date-time): If switching plans, when does the new plan take effect?
410
- * `tls_disabled` (boolean): Are Insecure TLS and SFTP Ciphers allowed? Enabling this is insecure.
412
+ * `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.
411
413
  * `trial_days_left` (int64): Number of days left in trial
412
414
  * `trial_until` (date-time): When does this Site trial expire?
413
415
  * `use_provided_modified_at` (boolean): Allow uploaders to set `provided_modified_at` for uploaded files?
@@ -489,6 +491,7 @@ await Site.update({
489
491
  'ssl_required': true,
490
492
  'tls_disabled': true,
491
493
  'sftp_insecure_ciphers': true,
494
+ 'sftp_insecure_diffie_hellman': true,
492
495
  'disable_files_certificate_generation': true,
493
496
  'user_lockout': true,
494
497
  'user_lockout_tries': 1,
@@ -633,8 +636,9 @@ await Site.update({
633
636
  * `left_navigation_visibility` (object): Visibility settings for account navigation
634
637
  * `session_expiry` (double): Session expiry in hours
635
638
  * `ssl_required` (boolean): Is SSL required? Disabling this is insecure.
636
- * `tls_disabled` (boolean): Are Insecure TLS and SFTP Ciphers allowed? Enabling this is insecure.
637
- * `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.
639
+ * `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.
640
+ * `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.
641
+ * `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.
638
642
  * `disable_files_certificate_generation` (boolean): If set, Files.com will not set the CAA records required to generate future SSL certificates for this domain.
639
643
  * `user_lockout` (boolean): Will users be locked out after incorrect login attempts?
640
644
  * `user_lockout_tries` (int64): Number of login tries within `user_lockout_within` hours before users are locked out
@@ -68,6 +68,21 @@ await Snapshot.create({
68
68
  * `name` (string): A name for the snapshot.
69
69
  * `paths` (array(string)): An array of paths to add to the snapshot.
70
70
 
71
+ ---
72
+
73
+ ## Finalize Snapshot
74
+
75
+ ```
76
+ const [snapshot] = await Snapshot.list()
77
+
78
+ await snapshot.finalize()
79
+ ```
80
+
81
+ ### Parameters
82
+
83
+ * `id` (int64): Required - Snapshot ID.
84
+
85
+
71
86
  ---
72
87
 
73
88
  ## Update Snapshot