• Joined on 2025-07-20
michael commented on issue dutchcoders/transfer.sh#133 2026-01-19 18:29:07 +00:00
Error while using Storj as provider

@driftywinds commented on GitHub:

@driftywinds basedir is not used at all for the storj storage provider, only when using local storage. Could you paste your entire docker run command here,…

michael commented on issue dutchcoders/transfer.sh#133 2026-01-19 18:29:07 +00:00
Error while using Storj as provider

@stefanbenten commented on GitHub:

@driftywinds basedir is not used at all for the storj storage provider, only when using local storage. Could you paste your entire docker run command here,…

michael commented on issue dutchcoders/transfer.sh#133 2026-01-19 18:29:07 +00:00
Error while using Storj as provider

@stefanbenten commented on GitHub:

@driftywinds I did not had time to look into this. Will get to it today 🙏

michael commented on issue dutchcoders/transfer.sh#135 2026-01-19 18:29:07 +00:00
Dead v2 onion address

@JacksonChen666 commented on GitHub:

@aspacca you should close this issue by adding the words resolves #446 to the commit message when committing the removal of the onion address

(github…

michael commented on issue dutchcoders/transfer.sh#134 2026-01-19 18:29:07 +00:00
Is there any kind of documentation to set this up with docker other than the README?

@driftywinds commented on GitHub:

@aspacca My bad, here is the command I use to deploy the container -

sudo docker run --publish 8080:8080 dutchcoders/transfer.sh:latest --provider storj…
michael commented on issue dutchcoders/transfer.sh#134 2026-01-19 18:29:07 +00:00
Is there any kind of documentation to set this up with docker other than the README?

@paolafrancesca commented on GitHub:

@driftywinds this doesnàt seem related to docker

also, could please share the params you use to launch transfer.sh and please, do not attacch screenshot…

michael commented on issue dutchcoders/transfer.sh#134 2026-01-19 18:29:07 +00:00
Is there any kind of documentation to set this up with docker other than the README?

@driftywinds commented on GitHub:

@driftywinds do you have any specific issue?

starting from fixing your setup we can come out with better documentation

EDIT: - Forgot to mention I am…

michael commented on issue dutchcoders/transfer.sh#134 2026-01-19 18:29:07 +00:00
Is there any kind of documentation to set this up with docker other than the README?

@driftywinds commented on GitHub:

@driftywinds this doesnàt seem related to docker

also, could please share the params you use to launch transfer.sh and please, do not attacch…

michael closed issue usnistgov/macos_security#69 2026-01-19 18:29:07 +00:00
os_install_log_retention_configure - TTL will be removed after update
michael opened issue dutchcoders/transfer.sh#136 2026-01-19 18:29:07 +00:00
.bashrc transfer command code fails on HTTPS servers
michael opened issue dutchcoders/transfer.sh#137 2026-01-19 18:29:07 +00:00
What all types of "--provider" do we have while launching it with docker
michael opened issue dutchcoders/transfer.sh#138 2026-01-19 18:29:07 +00:00
curl: (92) HTTP/2 stream 0 was not closed cleanly: INTERNAL_ERROR (err 2)
michael closed issue dutchcoders/transfer.sh#136 2026-01-19 18:29:07 +00:00
.bashrc transfer command code fails on HTTPS servers
michael closed issue dutchcoders/transfer.sh#137 2026-01-19 18:29:07 +00:00
What all types of "--provider" do we have while launching it with docker
michael closed issue dutchcoders/transfer.sh#138 2026-01-19 18:29:07 +00:00
curl: (92) HTTP/2 stream 0 was not closed cleanly: INTERNAL_ERROR (err 2)
michael commented on issue usnistgov/macos_security#67 2026-01-19 18:29:07 +00:00
os_sshd_fips_compliant remediation does not gracefully handle previous similar configuration settings

@bernstei commented on GitHub:

Wait, maybe I'm seeing what's happening - I didn't notice that they also appear in /etc/ssh/crypto/fips.conf. Is that how they're being set for sshd?

michael commented on issue usnistgov/macos_security#67 2026-01-19 18:29:07 +00:00
os_sshd_fips_compliant remediation does not gracefully handle previous similar configuration settings

@ChrisButigieg commented on GitHub:

I had the same issue resulted in Integer 3 instead of 7. Ran a -cfc and still failed for the same exact integer as before. Received an odd Token message, so…

michael commented on issue usnistgov/macos_security#67 2026-01-19 18:29:07 +00:00
os_sshd_fips_compliant remediation does not gracefully handle previous similar configuration settings

@golbiga commented on GitHub:

In macOS 15.2 there is a reset option for sshd configurations. See the note in the yaml.

NOTE: On macOS 15.2 and higher the SSH configuration can be reset to…
michael commented on issue usnistgov/macos_security#67 2026-01-19 18:29:07 +00:00
os_sshd_fips_compliant remediation does not gracefully handle previous similar configuration settings

@bernstei commented on GitHub:

So, it's a little weird. It does work in the sense that after I run it, the compliance remediation + check passes with no failures. However, there's one very…

michael commented on issue usnistgov/macos_security#69 2026-01-19 18:29:07 +00:00
os_install_log_retention_configure - TTL will be removed after update

@iamflaurian commented on GitHub:

Hey @robertgendler thank you for your quick response. I think it would be great to see these kind of information as a "note" to get hint about it