Skip to main content

Home/ Information Security/ Group items tagged engineering

Rss Feed Group items tagged

BluEnt Global

Search Engine Optimization Toronto - 0 views

  •  
    BluEnt helps businesses like yours get found online through search engine optimization. We offer SEO consulting services to small, medium and enterprises in Toronto.
Kiran Kuppa

Google looks to kill the password using tiny cryptographic card | Ars Technica - 0 views

  •  
    "Google engineers are experimenting with new ways to replace user passwords, including a tiny YubiKey cryptographic card that would automatically log people into Gmail, according to a report published Friday. In the future, engineers at the search giant hope to find even easier ways for people to log in not just to Google properties, but to sites across the Web. They envision a single smartphone or smartcard device that would act like a house or car key, allowing people access to all the services they consume online. They see people authenticating with a single device and then using it everywhere."
BluEnt Global

The Truth About Your SEO Contract That Could Save You Big Dollars - 0 views

  •  
    BluEnt reveals the top three factors impacting search engine optimization contract. Achieve the highest possible ROI with the best SEO pricing plan.
Skeptical Debunker

Sea World killer whale attack video leads to malware | Graham Cluley's blog - 0 views

  •  
    Dawn Brancheau, a trainer at Sea World in Orlando, was killed yesterday after being attacked by a killer whale. News of the tragedy sped quickly around the world, and now sick cybercriminals are exploiting the story of 40-year-old Brancheau's death for their own commerical gain. Through SEO (search engine optimisation) techniques, hackers have created webpages stuffed with content which appears to be ghoulish video footage of the animal trainer's death - but are really designed to infect visiting computers.
Kiran Kuppa

Applied Cryptography Engineering - Quarrelsome - 0 views

  •  
    "This article was written with several goals: to hurry along the process of getting Applied Cryptography off the go-to stack of developer references, to point out the right book to replace it with, and to spell out what you else you need to know even after reading that replacement. Finally, I wrote this as a sort of open letter to Schneier and his co-authors."
Seçkin Anıl Ünlü

Plugging the CSS History Leak at Mozilla Security Blog - 0 views

  • History Sniffing
  • Links can look different on web sites based on whether or not you’ve visited the page they reference.
  • The problem is that appearance can be detected by the page showing you links, cluing the page into which of the presented pages you’ve been to. The result: not only can you see where you’ve been, but so can the web site!
  • ...18 more annotations...
  • The most obvious fix is to disable different styles for visited versus unvisted links, but this would be employed at the expense of utility: while sites can no longer figure out which links you’ve clicked, neither can you.
  • David Baron has implemented a way to help keep users’ data private while minimizing the effect on the web, and we are deploying it to protect our users.
  • The biggest threats here are the high-bandwidth techniques, or those that extract lots of information from users’ browsers quickly.
  • The JavaScript function getComputedStyle() and its related functions are fast and can be used to guess visitedness at hundreds of thousands of links per minute.
  • we’re approaching the way we style links in three fairly subtle ways:
  • Change 1: Layout-Based Attacks
  • First of all, we’re limiting what types of styling can be done to visited links to differentiate them from unvisited links.
  • can only be different in color
  • the CSS 2.1 specification takes into consideration how visited links can be abused:
  • implement other measures to preserve the user’s privacy while rendering visited and unvisited links differently
  • Change 2: Some Timing Attacks
  • we are changing some of the guts of our layout engine to provide a fairly uniform flow of execution to minimize differences in layout time for visited and unvisited links.
  • when the link is styled, the appropriate set of styles is chosen making the code paths for visited and unvisited links essentially the same length.
  • Change 3: Computed Style Attacks
  • JavaScript is not going to have access to the same style data it used to.
  • Firefox will give it unvisited style values.
  • it’s the right trade-off to be sure we protect our users’ privacy.
  • fixing CSS history sniffing will not block all of these leaks. But we believe it’s important to stop the scariest, most effective history attacks any way we can since it will be a big win for users’ privacy.
Ace Dee

SEO Services that Exceeds Expectations - 1 views

Oracle Digital impressed me greatly with their content, knowledge and passion for the industry. After following Oracle Digital for three months and liking what I saw, I approached them for an initi...

SEO Perth Brisbane

started by Ace Dee on 22 Feb 11 no follow-up yet
1 - 20 of 20
Showing 20 items per page