Noam Rathaus

@initstring - it seems to be a rolling change - it now doesn't work when you try `/foobar`, it worked an hour ago I don't know what is going on......

I think there is some sort of rate limit / blocking - I have switch on and off the VPN and now it seems that S3 detection with the `/foobar`...

@Zoudo The fix isn't 100% accurate, it works sometimes - as there is some sort of rate limit - once you hit it, everything will return `NoBucket` - even valid...

I did some investigation with my AWS setup, from what I see, when `public` access has been completely blocked - `NoSuchBucket` will always return

I think current design implementation of S3, prevent detection of unknown S3 via keywords - at least this what I think

At the moment even valid s3 return as non existing when you hit the rate - which appears to me to happen within 2-3 requests to none existing buckets with...

The error you are seeing seems related to you not doing things as expected, see this old issue: https://github.com/rapid7/metasploit-framework/issues/7336 It specifically talks about your gpg key issue (missing key)

Can you verify that this: `/usr/share/keyrings/metasploit-framework.gpg` Exists? This is where the key is stored - it seems this step failed

We can close this one - there is no response from @edrapac

Easiest way to get a splunk copy running: `docker run -d -p 8000:8000 -e "SPLUNK_START_ARGS=--accept-license" -e "SPLUNK_PASSWORD=splunk" --name splunk splunk/splunk:7.1.0` Change 7.1.0 to older/newer versions depending on your needs NOTE:...