« first day (3533 days earlier)      last day (50 days later) » 

12:03 AM
In dark indoor environments, I always preferred to keep the ISO setting as low as possible and let the flash provide most of the light. When bouncing off a high ceiling, getting adequate light on the subject means the flash will need to fire at its maximum output. Repeat this process several hundred times during a typical event, and this kind of cracking becomes inevitable.
Eh, wear and tear.
 
 
2 hours later…
1:41 AM
@Burgi This goes through my mind, every. single. time.
 
 
11 hours later…
12:44 PM
user image
3
 
1:13 PM
:D
 
1:49 PM
I caution relaying entirely on Windows Sandbox to run potentially malicious programs. I watched a YouTube video recently, on a channel that tests security software, against thousands of payloads. In this particular video, Windows Sandbox allowed malicious software, to infect the host OS. However, it's important to point out the the author was running a VM which only had Windows Defender installed. — Ramhound Mar 24 at 16:43
Watched the same video :p pretty neat there is a sandbox available even though it could infect the host OS
 
2:11 PM
@CaldeiraG As of when, and what was the means by which the malware was able to escape the VM? I've used Windows Sandbox for testing purposes, but I'm not confident it could withstand a targeted attack.
Okay, lemme try something.
 
@bwDraco My reading of the comment it that it escaped the sandbox and infected the host OS, which was a VM
as opposed to escaping both the sandbox and the VM
I could be wrong of course
 
Windows Sandbox is a Hyper-V virtual machine which uses containerization technology for efficiency.
 
So you can't nest?
ie run a fully virtualised VM of Windows 10, and enable Windows Sandbox therein?
 
Not entirely sure about that. If the outer hypervisor allows nesting, than Windows Sandbox should be able to run.
 
2:52 PM
Yes, you can
Microsoft supports it
I used Microsoft's sandbox to start Folding@Home, then migrated it to my main machine
You can disable network access, GPU access, and HW access from the sandbox
So I'd like to see if they can escape with all those pieces in place
 
@bertieb yea that's the case
I'm pretty sure the video Ramhound mentions is this one:
basically he runs a VM with Windows and try a bunch of payloads inside it
it's pretty much the same way he tests antivirus on his channel
 
@CaldeiraG Cool
I'd be interested if there were any known exploits that can escape an externally-sandboxed browser
I have a friend who runs that as their protection on Windows 7, and it feels a bit risky
but it might be alright I'm not sure
 
3:09 PM
Teresa Dietrich on April 08, 2020
Back in February, we shared our Q1 Community Roadmap with you. In that post, we described our four roadmap themes which will continue throughout the year. In our commitment to provide transparency, we will continue to share our roadmaps each quarter. So without further ado, here is our Q2 Community Roadmap:  Understand community This month,…
 
3:25 PM
@CaldeiraG What about setting up an actual sandbox, and running the malware in the sandbox directly?
 
@CanadianLuke he is using the VM as a normal computer, then he activated the sandbox there
 
@CaldeiraG But he's not running it in the sandbox, only the Defender part in the sandbox
 
That seems a backwards methodology?
sandbox the AV but not the malware
 
That's how I read the sandbox feature as being useful. It sandboxes a VM of Windows 10, copies the program to it, starts up the desktop environment, then you can run it
 
3:46 PM
@CaldeiraG No, that's Windows Defender, which is the default antivirus. Windows Sandbox is a VM that uses containerization technology for efficiency.
Windows Defender can operate within a sandbox environment to contain malware, but that's not quite the same as the full-fledged VM that Windows Sandbox provides.
The idea behind Windows Sandbox is to allow the end user to test shady applications in a clean, virtualized environment that can be spun up and shut down in a matter of seconds. Exit Windows Sandbox, and poof! everything inside is gone.
 
 
7 hours later…
10:46 PM
 

« first day (3533 days earlier)      last day (50 days later) »