@paolafrancesca commented on GitHub:
@roozbehzarei you should address @stefanbenten on this, since this repo is only for the codebase
there is a "Contact us" link in the https://transfer.sh/…
@CodeCubeNeo commented on GitHub:
I guess yes, but you can guess that (although nearly impossible). You can close this and thanks for taking the time to answer my question ;).
@toastie89 commented on GitHub:
The 'password' is part of the URL in form of the random key, isn't it?
@fr34kyn01535 commented on GitHub:
Why? Website works just fine.
@paolafrancesca commented on GitHub:
@gedw99 these are more or less all the REST endpoint relevant for a full…
@CodeCubeNeo commented on GitHub:
So 20 lenght is default for transfer.sh?
@paolafrancesca commented on GitHub:
@CodeCubeNeo
it's one of the example on the frontend:
# Encrypt files with password using gpg
$ cat /tmp/hello.txt
@toastie89 commented on GitHub:
For me the 6 characters also feel a bit short. I run an own instance of transfer.sh and set random-token-length to 20.
@paolafrancesca commented on GitHub:
I will keep this open in case anyone is interested in developing a desktop client (even if you didn't specify what platform for, @CodeCubeNeo )
I'm…
@toastie89 commented on GitHub:
So 20 lenght is default for transfer.sh?
No, this is what I've set for my own installation. The default is 6.
@CodeCubeNeo commented on GitHub:
maybe change deafult to 10 or more? Just an idea.
@paolafrancesca commented on GitHub:
maybe change deafult to 10 or more? Just an idea.
I will do
@CodeCubeNeo commented on GitHub:
Great. always better to change security for the better over 4 characters (possible combos rise from 36^6 to 36^10 (36 is the number of possible characters only…
@brodjieski commented on GitHub:
Changes have been merged into primary branches.
@phaninder-scalefusion commented on GitHub:
This is regarding the rule “system_settings_filevault_enforce”, which checks whether FileVault is enforced. However, it does not validate against…
@brodjieski commented on GitHub:
Ahh, I see. Ok, so we do include the following in the fix of the rule yaml file, however, the guidance does not use this because it also has the mobileconfig_info.…
@brodjieski commented on GitHub:
Hello! Which FileVault subsettings are you seeing this issue with? Are there specific rule files that are affected? I want to be able to accurately reproduce the…