Showing posts with label Forced. Show all posts
Showing posts with label Forced. Show all posts

Sunday, March 25, 2012

Use an Analog Alarm Clock to Disable Forced Screensavers [Clever Uses]

Some employers have security policies that require mandatory password-protected screensavers after a minute or two of idle time. This can be extremely annoying since every time you take a phone call or jot down notes you have to login again. For a low-tech solution to this problem keep an analog alarm clock on hand.


Any time you need to take your hands off your keyboard and/or mouse, Reddit user acntech recommends placing your mouse on an analog alarm clock—the ticking will register as movement and keep the screensaver from engaging. This tip also works when watching longer videos on any computer.

How to use an analog alarm clock to disable forced corporate screensavers on your PC or laptop | Reddit

Thursday, March 22, 2012

Create a Hidden Encrypted Volume on Your Computer to Hide Sensitive Data When You're Forced to Decrypt Your Machine [Security]

Using full-disk encryption (FDE) is a great first step if you want to protect your data, but sometimes it isn't enough. The U.S. Government can force you to decrypt your data, so if you truly want to stay protected you need to hide your sensitive files elsewhere and use your primary disk as a decoy. Security expert Brandon Gregg explains:



FDE drives still leave your data and personal information vulnerable in at least two scenarios: 1) You are forced to turn over your password (as in Judge Blackburn's District Court ruling), or 2) Someone has hacked into your live machine and remotely recording your keystrokes/data while you work. To address these issues, we are also going to put our personal/business files in an encrypted directory-but not using just any encryption scheme. Encryption with hidden volumes is the key to really protecting your information and rights. With a correctly implemented hidden volume on your encrypted hard drive, you don't have to worry when someone cracks (or coerces you into giving up) the password. When they use it to open the door, they will only see the closet.


Brandon suggests using a bad password for the "closet" (your encrypted hard drive—not the sensitive data), such as password. It'll get cracked easily, which will encourage the person looking at your data to believe that you're not smart enough to hide and encrypt your truly sensitive data elsewhere. Keeping that data in a secret volume is a very clever trick and requires hardly more work than encrypting your disk in the first place. If you're looking to keep your files secure, this is a great way to do it.

Three steps to properly protect your personal data | CSO Online via Quora

Monday, March 5, 2012

Forced Browsing Attack


Forced browsing is XSRF attack in which a user is forced to browse a content without his/her knowledge. For example on this blog you can see several advertisements, all of them are real time examples of forceful browsing because you can't control their existence while browsing to this blog. A site is called vulnerable to forced browsing XSRF attack if it processes a request directly without notifying a user. For example consider a website http://www.victimsite.com/ is vulnerable to forced browsing XSRF attack. Now suppose you want to buy Bit Defender anti-virus from http://www.victimsite.com/ so when you click add to cart button on website, it will process your request by URL which might appears something like this,

www.victimsite.com/software/antivirus.php?product_id=123456 without notifying user about his/her request is processed, then that site can be surely attacked using forced browsing attack. Please note that above is just an example in real world stuff may vary according to the website. Now suppose an attacker want to take advantage of above vulnerability for his/her advantage then he/she will place an advertisement or review about product on his/her website and rather than putting a direct link in ADD TO CART button he will place a script in which he/she will add two or more products to get processed. Suppose the attacker adds link to a PHP script in which he/she also specifies visitor to buy one more product then most likely the script will appear as follows,/**** Some Lines of Code *****/header ('Location: www.victimsite.com/software/antivirus.php?product_id=123456 ');/**** Some Lines of Code *****/header ('Location: www.victimsite.com/software/antivirus.php?product_id=654321 ');/**** Some Lines of Code *****/in fact even following code in script will work,header ('Location: www.victimsite.com/software/antivirus.php?product_id=123456 ');header ('Location: www.victimsite.com/software/antivirus.php?product_id=654321 ');but attacker will not take any chances so he/she will surely craft code more carefully. Now when the victim will be checking out, his/her cart will be having two products instead of one and he/she will be fooled to buy an extra product. Again a site which does not create a random cookies for registering product to cart is also vulnerable forced browsing attack. If cookies remain static for some product then surely an attacker will pick up the product cookie value and craft his/her script to intentionally add that cookie to browser on which victim user is browsing so that when he/she will check out he/she will have to pay for more than one product. Please note that such sites are more dangerous than sites which can be attacked using URLs. Now the final words for the day. At practical level there's no way you can ever understand a site is vulnerable to these kind of attacks unless you have experience with web development tools and web application development. Everything explained above are nothing but basic examples specialty crafted so that even a nerd can understand forced browsing XSRF attacks but reality is that when an experienced web developer or web application developer will read this he/she will surely find out several variations can be made to above method to put on a real attack. In other words a person with no knowledge of web development or web application development can hardly figure out whether a site is vulnerable to attack or not and even if he/she figures out he/she may hardly have any idea about how to exploit it.