Willkommen in dem Jahr, in dem wir Kontakt aufnehmen werden

December 1st, 2009

The date is set for the release of the Boxee Beta.

Image representing Boxee as depicted in CrunchBase
Image via CrunchBase

On December 7th at 7pm we are going to have an unveiling event at the
Music Hall of Williamsburg. If you’re in NYC it would be great if you
could attend (RSVP at http://bit.ly/boxeebetanyc).

In case you can’t make it to the event you’ll be able to tune in to a live stream (provided by LiveStream.com) at http://blog.boxee.tv
or directly on Boxee (we’ve worked with Cliqset to overlay messaging onto the stream so you’ll be able to chat about Boxee
while you’re watching Boxee on Boxee. woah.) We’ll make a recommendation for this App on the day of the event.

At the event we will demo the new Beta, launch new applications and start
a 4-week early-access for users to test the Beta before we Read the rest of this entry »

September 19th, 2009


und alle so: “yeah”

Originally uploaded by spanier

January 11th, 2009


The Web is Agreement

Originally uploaded by psd

January 7th, 2009




saw this on the fnord news at 25C3

Originally uploaded by jmtosses


December 19th, 2008


Lydia Daher aus Augsburg auf dem POETRY SLAM (8. Runde) in der Halleluja Halle on Köln. www.lydiadaher.de

September 7th, 2008

This is not a joke. If you are using Google Chrome then it is very easy for a malicious attacker to get the Remote Access of your Computer.

Less than a week after the release of Google (NSDQ:GOOG)’s new Web browser Chrome, security researchers detected a buffer overflow vulnerability that could enable remote attackers to completely take control of a user’s computer.

The detected buffer overflow vulnerability, deemed critical by security experts, is the result of a boundary error in the handling of the “Save As” function. If a user saves a Web page serving malicious content, the program could cause a stack-based overflow error, which could open the door for remote hackers to unleash malicious code on a user’s machine.

Remote attackers could then exploit the flaw by constructing a specially crafted Web page infused with malicious code. The attacker could then entice a victim to open and then Read the rest of this entry »

September 7th, 2008

Update: 10.09.08: As from today on, due to an update from Chrome the :% issue is no more valid.

Rishi Narang has been the first. A Denial Of Service simple as pie:

Just browse this page and place your mouse over this link (make sure you bookmark this page if you want to read on though):

CRASH ME

Just “evil:%” in the anchor text is capable of crashing all the Chrome tabs (despite all the tabs are separated processes).

Someone has also reported that by entering a very long bookmark may kill the browser. Length has not been given but it’s worth a try.

If your Chrome is still alive you may want to try entering

about@:

in the location bar.

Good thing is that the browser doesn’t need Read the rest of this entry »

September 7th, 2008

Like most other browsers, Google Chrome has some special pages that show information about memory usage, cached files, plug-ins and more. Here’s a list of the most interesting about: pages available in Google Chrome (you can open them by dragging about:name to the address bar).

1. about:version – Google Chrome shows the version number the browser, WebKit and V8 (JavaScript engine). You can also find the user-agent used by Google Chrome:

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/525.19 (KHTML, like Gecko) Version/3.1 Safari/525.19


2. about:plugins – the list of plug-ins that are available in Google Chrome: Shockwave Flash, RealPlayer etc.

3. about:cache – a list of all the web pages cached by Google Chrome. The browser doesn’t have an option to limit the cache’s size, so it’s recommended to regularly empty the cache.

4. about:memory – this pages compares the memory used by all the active browsers and by Google Chrome’s tabs.

Read the rest of this entry »

September 5th, 2008

Shared by natadd

Actually, I would have more liked to give the win to Firefox and develop that to the may, instead of bringing in another rivale.

Google Blogoscoped has published a lengthly cartoon sent to them by Google and drawn by Scott McCloud that provides the first public details about Google Chrome, an open source browser based on WebKit and powered by Google Gears that has been rumored but never before confirmed.

According to the cartoon (which can be seen in its entirely here – thanks Marshall), the Google Chrome project has already undergone a substantial period of development with engineers working to create a product that’s secure, user friendly, fast, stable, safe, and easily testable.

This is a straight shot over the bow of Microsoft, which has tightly integrated its Live Search offering into its dominant Internet Explorer browser (and which, surprise, is also tightly integrated into Read the rest of this entry »

August 30th, 2008
Image representing Gmail as depicted in CrunchBaseImage via CrunchBase, source unknown

Shared by natadd

Very important!! You should always use SSL (https://) for Gmail!

A tool that automatically steals IDs of non-encrypted sessions and breaks into Google Mail accounts has been presented at the Defcon hackers’ conference in Las Vegas.

Last week Google introduced a new feature in Gmail that allows users to permanently switch on SSL and use it for every action involving Gmail, and not only, authentication. Users who did not turn it on now have a serious reason to do so as Mike Perry, the reverse engineer from San Francisco who developed the tool is planning to release it in two weeks.

When you log in to Gmail the website sends a cookie (a text file) containing your session ID to the browser. This file makes it possible for the website to know that you are authenticated and keep you logged in for two weeks, unless you manually hit the sign out button. When you hit sign out this cookie is cleared.

Even though when you log in, Gmail forces the authentication over SSL (Secure Socket Layer), you are not secure because it reverts back to a regular unencrypted connection after the authentication is done. According to Google this behavior was chosen because of Read the rest of this entry »

  • Translator

  • Categories

  • Follow

    Follow Me!

  • Back in the days

  • Listen

  • The usual suspects

  • Tags

  • Questions?

  • Page 1 of 3123»