Custom Query (8169 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (310 - 312 of 8169)

Ticket Resolution Summary Owner Reporter
#12351 worksforme S3 on Pro: Allow entry of bucket name Hilton Goldstein
Description

Without entering a bucket name, the Client must do a ListBuckets but that might not be permitted. Also, I might only care about one bucket. I consider this a bug since it prevents me connecting to a bucket without ListBuckets permission.

#12350 rejected Debug level selector in Settings is broken php4fan
Description

Steps to reproduce:

  1. Go to Edit / Settings
  2. Go to Debug
  3. Change the value of "Debug Information in message log" to something other than "warning": e.g., "Debug"
  4. Save and exit Settings
  5. OPTIONALLY restart FileZilla (will reproduce either way)
  6. Go to Settings again and again to Debug

Expected: the selector for "Debug Information in message log" should show the current level. Saving without touching it should not change the setting

Observed: regardless of what the current level is (that is, if you followed the steps above, regardless of the level you configured at step 3), the selector shows "1. Warning". If you now save the settings without having touched the debug level setting, it will be actually changed to Warning.

This is broken in two ways: 1) it doesn't show the actual current level; 2) it causes you to unintentionally change a setting without having touched it (by only changing other unrelated settings and saving) if you don't notice.

#12347 invalid Update failures - filezilla-project.org is using a local CA, so no path to verification m27GUmtEKeVEla
Description

When checking for updates in the client, I saw the update failing to connect. I grabbed the connection string from the "Show details" link and pasted it into a browser (Chrome for example). The link for me was https://update.filezilla-project.org/update.php?cpuid=sse%2Csse2%2Csse3%2Cssse3%2Csse4.1%2Csse4.2%2Cavx%2Cavx2%2Caes%2Cpclmulqdq%2Crdrnd%2Cbmi%2Cbmi2%2Cadx%2Clm&initial=1&manual=1&osarch=64&osversion=10.0&package=1&platform=x86_64-w64-mingw32&updated=0&version=3.51.0

This should generate a standard warning that pops up whenever certificates can't be validated. Looking at the certificate, the cert specified for update.filezilla-project.org seems good; however, it was issued by a private ca for filezilla-project.org with a private IP address of 10.6.92.6. This needs to be issued as a resolvable host (also: use FQDN, not IP).

New cert looks to have been applied around Dec 14.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.