Gapski

The malicious actors behind the MuddyWater campaign have given the malware a facelift changing the way the malicious files are executed and altering the social engineering used to entice its victims to open the infected Word document. Read More

I’m thinking of writing some complex macros that I plan to sell as a bundle. What’s the best way for a tool geek like me, who is not a trained programmer, to produce code that can run against ER/Studio Data Architect, that cannot be easily copied and shared with friends? Can basic macros be ‚compiled’? Is that even a word these days?

If you’re working across countries and time zones, you may want to use universal time instead of local time. And to ensure that the time format is culture neutral, using the ISO format is recommended. Here is how:

$date = Get-Date
$date.ToUniversalTime().ToString('yyyy-MM-dd HH:mm:ss')

ReTweet this Tip!

While Cortana would function as intended should you want to check your calendar or get an update on the weather, an attacker could issue a voice command and start typing. This would trigger a popup allowing access to features typically only available to a user on an unlocked device. By typing in the popup, anyone could access the application index and filesystem, and start searching the computer for system files (or file paths) where a password might be stored. Read More

We provide the system requirements for each free tool on the respective „Tech Specs” webpage. For example, here is the link for SQL Check: ” https://www.idera.com/productssolutions/freetools/sqlcheck/systemrequirements „. That pages states that SQL Check supports Microsoft Windows: Server 2008 SP3, 7 post-SP1 with .NET 4.0, Server 2008 R2, 8, Server 2012, 8.1, Server 2012 R2, 10 (provisional). Windows 2003 Server is not listed. etc. Please note that the system requirements refer to systems that we support because they were applied to the test program of each free tool during software development. It is well possible that other versions of Windows may also work. We just did not test that extensively, and we are not able to support that. So, for example, it is well possible that SQL Check works with Windows 2003 Server. But it may not, or at least not all functionality may work properly. And we cannot support Windows 2003 Server.