• Joined on 2025-07-20
michael commented on issue dutchcoders/transfer.sh#237 2026-01-19 18:29:33 +00:00
Could not save metadata

@stefanbenten commented on GitHub:

We are in the process of migrating the tool to the Storj network with PR #266 . Waiting for review and test from @aspacca .

michael commented on issue dutchcoders/transfer.sh#237 2026-01-19 18:29:33 +00:00
Could not save metadata

@stefanbenten commented on GitHub:

I just took a look at the host and fixed the issue. Every now and then it rans out of memory.

michael commented on issue dutchcoders/transfer.sh#237 2026-01-19 18:29:33 +00:00
Could not save metadata

@Whoffie commented on GitHub:

It has returned on command line uploads for me

michael commented on issue dutchcoders/transfer.sh#237 2026-01-19 18:29:33 +00:00
Could not save metadata

@blightwing commented on GitHub:

The issue has returned.

michael commented on issue usnistgov/macos_security#182 2026-01-19 18:29:33 +00:00
sshd checks sometimes fail for reasons other than the rule

@georgalis commented on GitHub:

try like this... if sshd -T >/dev/null 2>&1; then echo t ; else echo n ; fi

michael commented on issue usnistgov/macos_security#182 2026-01-19 18:29:33 +00:00
sshd checks sometimes fail for reasons other than the rule

@bernstei commented on GitHub:

Here is the debug output

-----DEBUG-----

###################  COMMANDS START BELOW THIS LINE  ###################

## Must be run as root
if [[ $EUID…
michael commented on issue dutchcoders/transfer.sh#237 2026-01-19 18:29:33 +00:00
Could not save metadata

@2spirit commented on GitHub:

same issue today...

michael commented on issue dutchcoders/transfer.sh#237 2026-01-19 18:29:33 +00:00
Could not save metadata

@stefanbenten commented on GitHub:

I checked the current host and it seems to operate fine, besides being very busy.

michael commented on issue usnistgov/macos_security#182 2026-01-19 18:29:33 +00:00
sshd checks sometimes fail for reasons other than the rule

@bernstei commented on GitHub:

Replacing the &2> with 2&> definitely works. Replacing it with your suggestion, &>, also works.

michael commented on issue usnistgov/macos_security#182 2026-01-19 18:29:33 +00:00
sshd checks sometimes fail for reasons other than the rule

@robertgendler commented on GitHub:

That's weird...try replacing that if statement with if sshd -T &>/dev/null; then

Lets see if that works.

michael commented on issue usnistgov/macos_security#182 2026-01-19 18:29:33 +00:00
sshd checks sometimes fail for reasons other than the rule

@robertgendler commented on GitHub:

Fixed that boo boo.

michael opened issue dutchcoders/transfer.sh#238 2026-01-19 18:29:33 +00:00
Simply not working for me
michael opened issue dutchcoders/transfer.sh#239 2026-01-19 18:29:33 +00:00
docker build error
michael commented on issue usnistgov/macos_security#182 2026-01-19 18:29:33 +00:00
sshd checks sometimes fail for reasons other than the rule

@bernstei commented on GitHub:

I assume that for ventura this is only merged into ventura. What's the best way to deal with that if we want to use Ventura with the STIG, which is in `dev_ventura…

michael closed issue dutchcoders/transfer.sh#238 2026-01-19 18:29:33 +00:00
Simply not working for me
michael commented on issue usnistgov/macos_security#182 2026-01-19 18:29:33 +00:00
sshd checks sometimes fail for reasons other than the rule

@bernstei commented on GitHub:

The actual checks work now, too, so as far as I'm concerned you can close this issue.

michael opened issue dutchcoders/transfer.sh#240 2026-01-19 18:29:33 +00:00
Curl could not save metadata
michael commented on issue usnistgov/macos_security#182 2026-01-19 18:29:33 +00:00
sshd checks sometimes fail for reasons other than the rule

@robertgendler commented on GitHub:

@bernstei just merged it up to dev_ventura_stig

michael commented on issue usnistgov/macos_security#182 2026-01-19 18:29:33 +00:00
sshd checks sometimes fail for reasons other than the rule

@robertgendler commented on GitHub:

All merged into the OS branches.

michael closed issue dutchcoders/transfer.sh#239 2026-01-19 18:29:33 +00:00
docker build error