Showing posts with label free. Show all posts
Showing posts with label free. Show all posts

Friday, 2 May 2014

How to Test Website across Multiple Browsers and Devices Synchronously


Welcome back!  I, Anubhav Sachan, am here again with another guide “How to Test Website across Multiple Browsers and Devices Synchronously”.


Responsive Web Design (RWD) is now a common approach in building a mobile friendly website. But building a responsive website can be quite irritating when you have to test the website in multiple devices and screen-sizes.

Say you have three devices to run the test on, you may end up having to constantly refresh each browser in every of those devices, which is cumbersome, to say the least.

So the idea of “synchronized testing” has emerged to address this situation and make the workflow more streamlined. There is a Grunt plugin called Browser Sync  to perform this, and Iam going to show you how to deploy it in your project, in this post.


 Why use Browser Sync?
First off, I’m not saying that Browser Sync is the perfect tool. There are also a number of GUI Applications such as Adobe Edge Inspect and Ghostlab which are great tools as well. They both have a nice GUI, but here’s why I think Browser Sync is better than these Applications:

1) Browser Sync (as well as Grunt) is free which helps if you have little to no budget to work with.

2) It is open-source. Depending on your JavaScript and Node.js proficiency you can extend it to cater to your own specific requirements.

3) It is cross-platform. You can use it in Windows, OS X and Linux. Ghostlab, on the other hand, is only available in OS X and Windows.


Installation
 To start off, you would install the Grunt plugin called Browser Sync. I’m sure the name says it all; this plugin syncs a number of interactions that occur on the website including page scrolling, populating form fields, and clicking on links.

All these actions will be reflected in the other browsers and devices as they are happening. Type the following command to install Browser Sync in your working directory:


npm install grunt --save-dev
npm install grunt-browser-sync --save-dev



Configuration

Once installed, Browser Sync can be loaded within the Gruntfile.js, this way.





  module.exports = function(grunt) {  
     grunt.initConfig({  
         browser_sync: {  
             dev: {  
                 bsFiles: {  
                     src : 'navbar-fixed-top.css',  
                 },  
                 ghostMode: {  
                    clicks: true,  
                    scroll: true,  
                    links: true,  
                    forms: true,  
                 },  
             },  
         },  
     });  
     grunt.loadNpmTasks('grunt-browser-sync');  
 }; 



This configuration will monitor the navbar-fixed-top.css file and automatically refresh the browser when it’s changed. We should also enable ghostMode to keep track of interactions on the website.

Note: Browser Sync also provides a number of other configurations, you can check them out in detail on this page. For the time being, the above configuration should suffice for the project example in this article.

Once the configuration is set, go to Terminal (or Command Prompt) and run the task using the following command:

grunt browser_sync

After running the command, you will be prompted to add three line of scripts within the <head> tag.

Also, when you view your website in multiple browsers, it also records those browsers, and notifies you in Terminal. In this case, I opened the website in Chrome, Safari, and Mobile Safari (through iPhone Simulator).


Check It Out

Now, as you can see from the following animated GIF, all updates, changes, and interactions are synced in real time in all the browsers.

I would be happy to hear from you. You may send your Suggestions,Advices etc. on contac ifo at Developers page.
Thank You !

Sunday, 20 April 2014

Cloud security challenges go all the way to the board



Short Description: "Less hardware, scalable infrastructure, falling prices and maturing services all make cloud computing very difficult to ignore. Organisations must ensure they don't also ignore the security challenges of cloud models."




 In the rush to take advantage of cloud's benefits, businesses must properly manage the risks of handing over data, systems, and infrastructure to a third-party.  As with any risk management process this is a challenge for the board as much as for the technical security team. 

Security keeps cropping up as a (if not the) major obstacle to cloud adoption — whether it’s applications or infrastructure that is hosted in a private, hybrid or public cloud environment.
But are concerns about security in the cloud misplaced? Evidence in the 2013 Data Breach Incident Report from Verizon (which also owns cloud provider Terramark) suggests it is. Based on 47,000 breach investigations in 2012, Verizon notes that "attacks against virtualisation were not present, but attacks against weakly configured devices that happened to be hosted in an external location were common — but not more common than among internally hosted ones."

Do CIO's agree with these facts? Yes and no. For every CIO who believes cloud security concerns are overrated, there's another who believes cloud security issues are very real.

However, whether security concerns about the cloud are exaggerated or not isn't the question under discussion here. The key issue for businesses considering moving a workload to the cloud is to quantify and address risks; from assessing which applications or infrastructure can be moved to the cloud with an acceptable level of risk, to how they will be protected once moved. 


Cloud security: Same concept, different implementation

While the same concepts behind on-premise security management apply in the cloud, there are nuances in their implementation that may escape the board-level view, but could nonetheless be vital.
For example, customers may find security tools they're familiar with on-premise are stripped back in the cloud. Network access controls are just one example. 

"Network access controls are typically far more basic in the cloud compared to physical architectures, and the tools used to manage the access controls are also more basic. This can lead to poorly implemented network access controls that lead to unnecessary access to systems and services," said Ty Miller, founder of security firm Threat Intelligence. 

"Physical security appliances ensure high performance and can be made highly scalable with low level networking to load balance packets across multiple security devices. Cloud environments are designed to be scalable, but some virtual security devices don't have the same performance as their hardware equivalent."

So how should businesses go about security risk management when considering cloud service providers?  Those considering the cloud can be confronted by providers that only offer opaque visibility into how they manage security and data. But isn't that scenario also true when assessing a provider of closed-source software or an outsourcer that offers assurances based on service level agreements? 

The customer needs to build a framework to assess a provider and compare them with rivals but not overburden the provider with assurance requirements. In the end, the rigour of the risk assessment process comes down to the depth of research a buyer is willing to go into ahead of making a commitment. 

"The first thing we're talking to clients about is that not all clouds are equal," said Intelligent Business Research Services security analyst James Turner. 

"A prospective buyer should research what the cloud vendor is prepared to commit to. Most cloud vendors have realised that committing to SLAs has to be a token gesture that immature buyers will pay attention to."

Different maturity levels on the buyer-side explain why, in a recent survey (pdf) by cloud-management vendor RightScale, a third of 'cloud beginners' saw security as the major obstacle to moving to the cloud, but only 13 percent of 'cloud focused' organisations (those that make "heavy use' of cloud) shared that view. 

"Mature buyers will know that no amount of service credits can ever replace the business impact of a cloud failure. Cloud vendors are in the unenviable position of offering to provide outstanding business service and at the same time, putting themselves on the hook for protecting their customer's information assets," said Turner.

The mega-bug outlier and the perennial question of data sovereignty
Last week's discovery of a security hole, dubbed Heartbleed, in OpenSSL should give pause for thought to anyone weighing up risks in the cloud. Implementing OpenSSL on a web server should have provided encrypted communications over the internet, but instead, could be abused to leak user passwords, private keys and session tokens. 

The flaw affected components of on-premise systems, private clouds and public cloud providers. But it has different ramifications for the buyer, signs that a service provider supports good security practices turned out to be a major vulnerability. How does a buyer asses that?
Before Amazon Web Service applied the Heartbleed patch, its elastic load balancers were vulnerable to the bug. 

Microsoft's popular web server IIS is immune to the bug, but it's not uncommon today to rely on a cloud provider for backup services, such as Amazon Web Service's (AWS) Elastic Load Balancer. 
"There are definitely lessons that have been learnt via the Heartbleed vulnerability in relation to risks introduced by cloud providers," Ty Miller, CEO of Threat Intelligence told ZDNet.

"The AWS load balancer could still be exploited to capture your private SSL certificates, and potentially usernames, passwords and session cookies."

Fortunately, bugs like Heartbleed don't come along every day. A more persistent issue has been data sovereignty and the fuzzy legal risks that come with shifting data to a different jurisdiction. It's a deal-breaker for many government agencies and some regulated industries, particularly for those outside the US.

Sweden's Data Inspection Board last year undertook legal action against one municipality and several schools that migrated from on-premise systems to Google Apps. In addition to data sovereignty concerns, Google's standard contract, in the Board's view, gave too much leeway for it to do as it saw fit, which conflicted with the organisations' duties as a "data controller".
The Swedish cloud cases occurred against the backdrop of a much bigger shift within the European Union, which updated its Data Protection Directive amidst calls by some Members of European Parliament to cancel the US-Europe Safe Harbour Act that had allowed some US firms to process data about EU citizens outside the continent.  

"As part of any migration to the cloud, enterprises need to ensure they are aware of and comfortable with the locations where the data will be stored and the legal implications associated with those locations," said Craig Searle, head of cyber for BAE Systems' Applied Intelligence in the Asia Pacific region.  

These are weighty issues that go past the technical and into the legal and management sphere, and demonstrate why it's so important board level executives are on top of cloud security challenges and exposures.


Friday, 21 March 2014

How QR Code Scanner does works?



Hey! Readers 

Now days a craze for QR Code has begun. Every advertisement has a QR Code embedded in it which usually takes you to the link of the product’s demonstration movie on YouTube®. During this thinking and research I got a program ( A basic HTML one) which could generate the QR Code for your  Website , Facebook Fan page , Google+ Profile  or any link you want. You can even make it for a text, address or number.
 
If you want one contact me on details at the end of post.

Beginning with a Bar Code Reader I’ll be telling the basic funda how it works then we’ll move on to QR Code Reader.

A barcode scanner is composed of three parts: the illuminator, the decoder, and the sensor/convertor. The barcode scanner illuminates the barcode with red light using the illuminator system. The sensor/convertor part of the scanner then detects the reflected light. Once the light is detected, an analog signal is generated. This signal contains varying voltage based on the intensities of the light reflection. The analog signal is converted by the sensor into a digital signal. The digital signal is then interpreted by the decoder. The decoder then sends the information to the computer attached to the scanner.

In the case of QR code scanner, the decoder sends the information to your mobile phone instead of a computer. The app you download for your phone that is a QR code scanner contains the illuminator, which is the red light that runs across the screen when you open the app. The sensor and decoder then work to decode the QR code. Then the decoder sends the information to your phone, and you will be able to see where the QR code was supposed to take you.

The way the scanner reads the reflected light it actually a lot more complicated than the way that I simply described it, but I think it's fascinating that all you have to do is download a free app and all of a sudden your phone is a barcode scanner. The barcode was first patented in 1952, and now almost every person with a smart phone carries around their own barcode scanner with them every day. Since this scanning technology is so easily accessible with most phones, QR codes as a marketing tool seem like they will be around for a while.

Thank You!

Contact Me (Anubhav Sachan)
Via-  anubhavsachan@outlook.com
         anubhavsachan4shree@gmail.com