Their is a major flaw in IE8 that may deem safe site unsafe Read More

Microsoft begins paving path for IT, Cloud integration Read More

3 Reason Azzure will Succeed  Read More

The scantily dressed woman has nothing else to show you.

The Facebook staff has been hard at work to squash a new worm propagating on the social networking platform with the help of unwary users. Using the image of a female model in lingerie as lure, the nuisance spread from wall to wall through a Web exploitation technique known as clickjacking.

This most recent attack doesn’t appear to have had a malicious component and was most likely a proof of concept. The rogue Facebook posts featured the picture of an attractive female model looking over her shoulder and an accompanying message reading “Wanna C Somthin’ HOT!?? Click Da’ Button, Baby!” Choosing to comply with the instruction while being logged into Facebook did nothing more than re-post the message without authorization on your own wall, thus propagating it further.

The trick was so well crafted and intriguing that it even managed to trick some security professionals. “The worm’s landing page is brilliant — alluring yet mysterious, and very clean, just like we techies like it. […] As a personal lesson, I have to admit mea culpa. I saw the worm being posted from a friend’s page and didn’t believe it to be dangerous because the lure is pretty cool,” Gadi Evron, a reputed security consultant and former Israeli CERT manager, writes for Dark Reading.

After analyzing the worm, Nick FitzGerald, emerging threats researcher at antivirus vendor AVG, concluded that the attack technique used was cross-site request forgery (CSRF). “A sequence of iframes on the exploit page call a sequence of other pages and scripts, eventually resulting in a form submission to Facebook ‘as if’ the victim had submitted a URL for a wall post and clicked on the ‘Share’ button to confirm the post,” he explains.

However, the Facebook staff disagrees with the CSRF assessment and says that a technique known as clickjacking, or in technical lingo, user interface redressing, is the culprit. Clickjacking is a term referring to an entire class of attacks that affect all browsers and involve overlapping hidden buttons onto visible ones. Therefore, when a user attempts to click the legit button in order to perform an apparently harmless action, their mouse click is hijacked and used to trigger an unintended one.

“This problem isn’t specific to Facebook, but we’re always working to improve our systems and are building additional protections against this type of behavior. We’ve blocked the URL associated with this site, and we’re cleaning up the relatively few cases where it was posted,” a Facebook spokesperson commented for The Register.

Clickjacking is a growing concern amongst the infosec community and browser vendors have yet to completely address it. The technique is actually exploiting an architectural flaw at the core of the Web; therefore, it is difficult to mitigate without breaking other legit functionality.

This doesn’t mean that users are completely exposed. For example, Firefox users can protect themselves against most of these attacks by installing a popular security extension called NoScript.

With Internet Explorer 8, Microsoft also introduced a directive called X-FRAME-OPTIONS that web developers can declare on their websites in order to counter clickjacking abuse. Unfortunately, this means that IE8 users have to rely on website owners to protect them, which is not very practical.

Source: Softpedia.com

The latest version of Microsoft’s Internet Explorer browser contains a bug that can enable serious security attacks against websites that are otherwise safe.

The flaw in IE 8 can be exploited to introduce XSS, or cross-site scripting, errors on webpages that are otherwise safe, according to two Register sources, who discussed the bug on the condition they not be identified. Microsoft was notified of the vulnerability a few months ago, they said.

Ironically, the flaw resides in a protection added by Microsoft developers to IE 8 that’s designed to prevent XSS attacks against sites. The feature works by rewriting vulnerable pages using a technique known as output encoding so that harmful characters and values are replaced with safer ones. A Google spokesman confirmed there is a “significant flaw” in the IE 8 feature but declined to provide specifics.

It’s not clear how the protections can cause XSS vulnerabilities in websites that are otherwise safe. Michael Coates – a senior application security engineer at Aspect Security who has closely studied the feature but was unaware of the vulnerability – speculates it may be possible to cause IE 8 to rewrite pages in such a way that the new values trigger an attack on a clean site.

If the attacker can figure out a flaw in the way IE 8 is actually doing that output encoding and then create a specific string the attacker will know will be transformed into an actual attack, they could use that to input a value … that actually results in an attack firing on the page.
This could be a way to introduce an attack into a page that didn’t have a vulnerability otherwise.

Late on Thursday afternoon, Microsoft told The Register: “Microsoft is investigating new public claims of a vulnerability in Internet Explorer. We’re currently unaware of any attacks trying to use the claimed vulnerability or of customer impact.”

Once its investigation is finished, the company will “take appropriate action,” including issuing a patch or guidance on how users can protect themselves against exploits.

When Microsoft introduced the protections, it also created a way for webmasters to override the feature (by adding the response header “X-XSS-Protection: 0″). A review of the top 50 most visited websites shows that only web properties owned by Google have actually opted to do so. The small number of sites blocking the protection calls into question how widespread the vulnerability is.

Source: Securityfocus.com

This is an angry blog entry. Read no further if that offends you.

"Don't hold my computer hostage, you bitches!"

Internet Explorer 8, or as I call it, “Aiyeeeeeee-Hate,” has completely screwed up my Internet experience, resulting in my messing up Firefox in an attempt to find out what was screwing up IE8.  Now I’m having problems with both browsers.  I am so frustrated!!!  Four days of effort and still no satisfaction!  And everybody keeps giving me the same worthless advice.

“Hey, your wagon isn’t working right?  Let’s try to reinvent the wheel all over again.  Go back to the very beginning — take all the wheels off and start anew.  Then we can put a whole new set of wheels on your wagon and it will go again.”

F**k you, Microsoft, and the horse you rode in on.  The problem lies in IE8 — something you changed!

1) IE8 cannot seem to display web pages I have been going to for the last 4 or 5 years (or more).  WTF!  Why are we having a problem suddenly after updating to IE8?

2) IE8 seems to have been sent out without all the security certificates it should have included, because suddenly since updating to IE8, I cannot log in at my bank (a secure site).  I get a message that roughly indicates that this may not be the site I think it is, and the safest thing to do is just close the web page.  (But it’s my bank, the address is correct, and their VeriSign security certificate seems to be in good order.)  There is another secure site that behaves in the same way, but not all secure sites are warning me off.  [Have you ever locked yourself out of your house or apartment? Doesn't it make you furious?  Doesn't it make you want to scream and dance up and down and wave your arms about!  I'm doing that now!  My husband is busying himself in another room until I cool down.]

3) Trying to publish a blog article has become so excruciating that I just want to throw something, and I’m really not that kind of person.  I love my things way too much to want to break something.  In both IE and Firefox, trying to upload a file to WordPress.com is next to impossible.  You follow the directions and it looks like it might accept the upload after a very long time, but then it throws a blank, white page in your face and you don’t know if the upload was successful or not.  If you try Refreshing the page, it takes you back a page to the beginning of the upload process.  Then you have to start the upload process over again.  [Insert scream here.]

One night this last week, I sat in front of my beloved computer with a stopwatch in one hand, the mouse in the other hand.  I finally got a picture uploaded and in place in the article and pressed the Publish button.  By the stopwatch it was 13 minutes and some odd seconds before WordPress announced success, that it was actually published in the wee hours of the morning.  I had been working on it since about 10:30 in the morning.

What this experience has taught me so far is that I REALLY don’t like Microsoft’s attitude toward the typical user. They seem to say, “You’re too stupid to manage your computer by yourself, so we’re going to do it for you. Just ignore the men behind the curtain. While we help ourselves by gathering information from your machine, we won’t hurt you — MUCH!”

I am not a rank beginner. I am not a child. I am a free woman, old enough to be someone’s grandmother. I will not be folded, spindled, torn, stepped on or shoved into a corner!

I bought the computer.  It belongs to me.  I reserve to myself the right to control what happens to my computer and to veto any suggestions made by a well-meaning advisor if I think that is appropriate.  I will listen to advice.  (May not take it, but I will listen.)  I am open to being taught by a teacher or mentor.  But I will NOT be treated like an errant child.

Time to shop for a new browser! The reviews say Opera is blazing fast….

Hi,

auf Faisal Hussain’s weblog und im TechNet UAG Forum wird nun klargestellt, was mit Forefront IAG & UAG sowie Clients wie Windows 7, IE 8 und 64 Bit Clients  wie supported ist:

As I understand based on information I have about windows 7 support would be fully available for UAG (Unified Application Gateway) only. There are two Win7 clients, 32bits and 64bits and the answers are different per platform:

For 32 bit clients: SSL Network Tunneling (Network Connector) won’t work (Win7 + UAG offers instead SSTP) and Terminal Services (RDP) won’t work (TSG will). Please also note that SSL Application Tunneling will only work in socket forwarding (no port forwarding is supported).

For 64 bit clients: in addition to the above, SSL Application Tunneling and Socket Forwarding won’t work, TSG will only work on 32bit IE that supports ActiveX.

As far as I know for IAG there would only be support for 32 bit clients and is expected with update 3 that will be released end of December. IE 8 is fully supported with IAG 3.7 SP2 Update 2 only.

For more clarification please refer to UAG forum:

http://social.technet.microsoft.com/Forums/en-US/forefrontedgeiag/thread/9a4c45fe-a780-4e07-85a9-93b9aa6cf651

Na dann, Viel Spass beim selber Testen!
CU

There was a period when time spent working online was measured in a similar manner to the way people think of ‘dog years’ (dogs being perceived to age 7 times quicker than humans). A year of digital experience was akin to 7 years working offline. It was an exageration of course, with a kernal of truth. But the pace of digital development has slowed a little (the internet hit 40 years old last week – could this herald middle age spread? Or a looming mid life crisis?).

Netscape Logo 1994 - 2002

In 1994 Netscape made the internet truly accesible for consumers for the first time, slow though it was, through a 14.4k or 28.8k modem and a Netscape browser. After their decline and fall, to Microsoft’s Internet Explorer (which, to be frank, was great in its first few years). The Byzantine code that made up Netscape Communicator remained behind; from the once great Netscape Navigator, that plummeted from controlling over 90% of the browser market, to under a 1% share in the late 1990’s. But after the AOL purchase debacle, the code gained an interesting new life. Under the stewardship of Mozilla (entering into Open Source first in 1998), in 2004 Firefox was born.

So this month marks the 5th birthday of Firefox (or 15th year and a bit for its Netscape parent). And Firefox has finally become a relevant and compelling web browser again. There’s no lag (not in the IE8 sense) and with Xmarks it is easy to flip your favorites list from one PC/Mac to another. So you never need to set up another computer from scratch

So here’s wishing Firefox a happy 5th (15th?) birthday.

There is an understated, but interesting, celebration for Firefox: HERE

Happy birthday to you, happy birthday day to you, happy birthday to Firefoxxxxx. Happyy birthday to you!! Okay, your fifth birthday was actually on Monday; I’m late. Sorry. As a belated gift, I will continue to use you for the foreseeable future as my primary web browser. That is until something better comes out – Google’s Chrome is supposed to come out before Christmas on the Mac.

Can’t believe Firefox is five. Here is my journey. In early 2006 I only knew of Internet Explorer as the main web browser. In Spring 2006, I jumped onto Firefox on the recommendation from a close friend. He was using the fox and was zipping about the web, adding extensions and opening windows in TABS. Firefox was the only browser on the block to have tabbed browsing at the time. It changed the way I browsed. I never looked back. IE was archaic compared to FF.  At the end of August 2007, I bought a MacBook. With OS X 10.4 came Safari. Safa-what? I need my FF was what I thought. FF was slow as hell on my MB. It hoggged RAM like no other, spiked the CPU, heated up the computer…it was nightmare. I eloped with Safari. When Firefox 3.0 was set to go down on June 30, 2008, featuring major RAM reductions and faster page rendering, I joined the millions of people worldwide in downloading it on day one to help set the world record. Indeed, it was much improved. I abandoned Safari and switched back to the fox. I’ve been using FF 3.5 as my main browser ever since.

Whew. That was a mouthful wasn’t it? Even with Safari’s 4.0 being snappy, I can’t live without the plug-ins/extensions that can be installed for FF. Take one plug-in called “Ad-Block Plus.” It blocks advertisements on all web pages. I installed it earlier this year and I haven’t seen an advertisement on the web ever since. No wonder I’ve been so much more productive this past year!

Firefox is an open-source web browser. Because the code is not locked in a closet somewhere sealed beneath 10 layers bullet proof glass, anyone who wants to modify it to their liking can do so. Customization is key for a useful FF experience. No two installations of FF will be the same if each one is customized to the individual.

Here’s to many more years of Firefox! As a bonus, let’s see if the majority of people even know what a browser is.

Google’s Chrome will bring some competition to the web browser arena. It is already my web browser of choice on a Windows machine. The beauty of Chrome lies in the small application size, stripped down interface and FAST FAST page rendering like no other. Chrome is already for Windows and is expected to be released before Christmas on the Mac. Can’t wait!

Had this problem with a site recently. A little reading suggests IE will be forced to document.compatMode= ‘BackCompat’ if there is a comment, PI, XML declaration (prior to IE8) or any non-whitespace textual content before the doctype. If a control character has snuck in that you can’t see in your text editor, that could do it.

Jakarta, dotexe.wordpress.com

Internet Explorer adalah web browser yang menjadi salah satu pilihan bagi sebagian besar pengguna dan vendor. Pengguna PC,utamanya yang menggunakan sistem operasi Windows pasti secara default menggunakan browser ini. Tak salah juga jika para vendor aplikasi berbasis web seperti e-banking dan e-commerce membatasi support mereka pada browser ini.

Bagi pengguna distribusi linux, tentunya merasa ‘teraniaya’ jika sebuah layanan web harus menggunakan IE. Mau tak mau mereka harus beralih sebentar ke PC Windows. Tapi bukan pengguna linux kalau tak kreatif, kita masih bisa menjalankan Internet Explorer dilingkungan Linux.

Yang kita butuhkan cuma installer Internet Explorer 8 dan Wine. Wine atau Wine Is Not Emulator adalah software linux/mac yang menyediakan layer API Windows dilingkungan *nix, sehingga software yang hanya dapat berjalan di Windows dapat dijalankan di Linux dengan baik.

# Untuk mengikuti tutorial ini silakan gunakan distribusi linux apapun selama mudah mendapatkan dan mengkonfigurasikan Wine di sistem anda. Kami sarankan menggunakan Debian atau turunannya (Ubuntu)

1. Instalasi Wine
Untuk Ubuntu, instalasi wine dapat dilakukan dengan mudah via apt-get:

apt-get install wine

2. Konfigurasi lanjut Wine
Jalankan terminal/xterm/konsole dan ketik winecfg untuk menjalankan window konfigurasi Wine.

Tuju ke tab menu Libraries dan tambahkan konfigurasi sebagai berikut dengan tombol Add:

” browseui=”native, builtin”
“crypt32″=”native, builtin”
“gdiplus”=”native”
“hhctrl.ocx”=”native, builtin”
“hlink”=”native, builtin”
“iernonce”=”native, builtin”
“iexplore.exe”=”native, builtin”
“itircl”=”native, builtin”
“itss”=”native, builtin”
“jscript”=”native, builtin”
“mlang”=”native, builtin”
“mshtml”=”native, builtin”
“msimtf”=”native,builtin”
“msxml3″=”native,builtin”
“riched20″=”native,builtin”
“riched32″=”native,builtin”
“secur32″=”native, builtin”
“shdoclc”=”native, builtin”
“shdocvw”=”native, builtin”
“shlwapi”=”native, builtin”
“url”=”native, builtin”
“urlmon”=”native, builtin”
“usp10″=”native, builtin”
“uxtheme”=”native,builtin”
“wininet”=”builtin”
“wintrust”=”native, builtin”
“xmllite”=”native, builtin”

3. Salin library tambahan dari Windows
Untuk trik ini kita harus menggunakan library/pustaka asli dari Windows yaitu:
- msctf.dll
- msimtf.dll
- uxtheme.dll

taruh ketiga pustaka tersebut di /home/user/.wine/dosdevice/windows/system32 (direktori system32 Wine anda)

4. Unduh dan jalankan Winetricks
Kita perlu melakukan konfigurasi advance terhadap Wine, untuk itu kita gunakan script Winetricks dari Kegel.com. unduh dari:
http://www.kegel.com/wine/winetricks

ubah script winetricks menjadi executable dengan:

sudo su chmod +x winetricks

kemudian jalankan winetricks:

./winetricks

5. Unduh dan Install Internet Explorer 8
Unduh terlebih dulu Internet Explorer 8 dari Microsoft.com (via Intipadi.com):
http://dl.intipadi.com/1age

setelah selesai didownload, lewat terminal jalankan instalasi IE8 dengan:

wine IE8-WindowsXP-x86-ENU.exe

*) abaikan permintaan installer untuk melakukan update.

Lihat screenshoot berikut

6. Kesimpulan dan Saran
Walaupun IE8 sudah dapat berjalan dengan baik dilingkungan Linux, tapi dibaliknya masih terdapat ribuan bug dan celah keamanan.Bug terbesar berada pada pustaka comctl32.dll dan comdlg32.dll, Penggunaan IE8 sendiri dilingkungan Linux lebih bersifat experimental dan darurat, jangan memaksa menggunakan IE8 sebagai browser default distribusi linux anda menggantikan browser lain.

Untuk solusi yang lebih professional dan mempunyai support yang baik, silakan beli CrossOver Office atau Bordeaux sehingga anda dapat menjalankan Office 2007, Photoshop CS dan lainnya dengan lancar.

NB. Tutorial ini telah mengalami proses penyuntingan dan praktik real dengan spesifikasi hardware, software tertentu, dan terbukti berhasil. Segala risiko kerusakan hardware, software maupun data akibat tutorial ini bukan tanggungjawab penulis.

Nota: Este artículo habla acerca de cómo guardar fotos utilizando Windows Internet Explorer 7 ó Windows Internet Explorer 8 en Windows 7. Para información acerca de cómo hacerlo utilizando Mozilla Firefox 3.x de click acá.

Copyright (c) 2009 Alvaro O. López

Yo siempre he estado un poco en contra de los metroflogs y una de las opciones que éste ofrece es el bloquear el botón derecho del ratón para no poder descargar las imagenes de un usuario… (si, para poder descargar una imagen generalmente damos click derecho y seleccionamos [Guardar Imagen como...])y nos aparece esta advertencia:

El lamentable error...

Esto se debe a que en la pagina se agrego un script en JavaScript, el cual bloquea el botón derecho y evita que se muestre el menu contextual. Entonces para poder desbloquearlo debemos desactivar JavaScript en las opciones de nuestro navegador web. Les mostraré como hacerlo desde el nuevo Windows Internet Explorer 8 bajo Windows 7: (aclaro, el procedimiento es el mismo bajo Windows XP/2003/Vista/2008 en Windows Internet Explorer 7 ú 8.)

Abrimos las opciones de Internet Explorer, es decir, presionamos <Alt> (para mostrar el menú del navegador, si es que está oculto) y seleccionamos [Herramientas > Opciones de Internet...]. Después seleccionamos la pestaña (tab) llamada [Seguridad]. Veremos esta ventana:

Opciones de Internet

Seleccionamos la opción [Nivel personalizado...]. Veremos ahora esta otra ventana:

En ella buscaremos una opción que dice [Active scripting] y la deshabilitamos con la opción [Deshabilitar]. Procedemos a aceptar nuestros cambios (presionamos [Aceptar]), si nos aparece una advertencia, le decimos [Sí] y regresamos a la pagina web del Metroflog bloqueado. Vean, voila!:

Ya podemos guardar la imagen

Ahora sí ya podremos seleccionar la opción [Guardar imagen como...] y guardarla en algun lugar de nuestro disco duro. Eso sí, cuando terminen, no olviden volver a activar JavaScript, ya que es necesario para algunos sitios (como Hotmail) para funcionar correctamente. Suerte:)!!!

P.D: Este procedimiento también se aplica para otros sitios web con fotos o imagenes protegidas, o que no permitan el uso del botón secundario del mouse.

If you haven’t heard of them ‘Accelerators’ are a new feature in IE8 which are designed to make your browsing tasks quicker and easier.

Accelerators allow you to perform an action by simply highlighting text on a webpage or just right clicking on a page and selecting your chosen accelerator.

Below are my top 5 IE8 accelerators:

1. ‘Google Reader Accelerator’

Simply right click on the RSS feed page and click the accelerator to subscribe to it with your Google reader account.

http://www.ieaddons.com/en/details/bookmarks/Subscribe_with_Google_Reader/

2. ‘WordPress Accelerator’

Select any text on a webpage and select the accelerator to start a new blog post containing the selected text.

http://www.wordpress.com

(Login to your dashboard and you should find it available for download)

3. ‘Twitter Accelerator’

Select some text on a page and select the twitter accelerator to send the text as a tweet from your twitter account.

http://openbrolly.com/2008/08/31/ie8-accelerator-for-twitter/

4. ‘Google Maps Accelerator’

Select any bit of text (Postcode, Address etc) and select the google maps accelerator to open the location in google maps.

http://ie.microsoft.com/activities/en-en/Default.aspx

5. ‘Google Mail Accelerator’

Select some text and select the google mail accelerator to create a new email message containing the selected text.

http://ie.microsoft.com/activities/en-en/Default.aspx

Hope you find these accelerators helpful and as useful as I do!

E aí leitor! Você também é designer de aplicações em .NET? Então isto aqui pode te interessar…

É diante de um problema que a gente aprende coisas novas. Eu estive esta semana “brigando” com a meta tag:

 <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />

no sistema de Extranet da SET.

Pra quem não sabe esta tag serve para fazer o Internet Explorer 8 renderizar uma página como se fosse sua versão 7, isto evita o trabalhão de adaptação ao novo navegador por parte dos desenvolvedores, como já sabemos, existem problemas de estética e Javascript que impedem que a página funcione corretamente dependendo do tipo e do versão de navegador.

O que ocorre é que em aplicações mais robustas e que possuem o arquivo Global.asax, pelo menos no meu caso, aplicar esta tag simplesmente no <header> não adianta. Por alguma razão a qual não era meu foco investigar, o navegador não faz a página ter o mesmo funcionamento do antigo navegador pois esta não é uma solução infalível. Existe também o recurso que o IE8 oferece que é a Solução de Compatibilidade, que tem a mesma função da tal tag mas em alguns casos é possível que esta solução não seja uma solução de fato. A gente tem um CMS da IVIA rodando por lá, o Content, onde há relatos de que fazer com o que o IE8 se comporte como IE7 resultou em alguns problemas.

Aí consultei um ex-colega de trabalho, que jogou no Google, que descobriu um artigo do Vitor Canova, desenvolvedor .NET do Rio Grande do Sul, que é este aqui.

Bom, acontece que esta solução não funcionou porque o .NET é anterior ao que usamos, então, eu como um cara legal que sou , tive a idéia de aumentar as informações sobre o tema, e otimizar a solução já escrita para ajudar colegas que estão precisando de ajuda por aí. Então fizemos uma readaptação do código para uma solução mais pontual em .NET 2.0. Seguem os passos mastigadinhos pra que você possa tentar aí:

1. Primeiro procure a Master Page do seu projeto, e inclua lá, como primeira meta-tag de toda a página, a tag <meta http-equiv=”X-UA-Compatible” content=”IE=EmulateIE7″ /> (no cabeçalho logicamente);

2. Compile e rode no navegador. Teste a aplicação e dá uma boa olhada se está tudo ok. Se estiver você nem precisa pular para o próximo passo, senão, vamos em frente.

3. Procure o GLOBAL.asax da sua aplicação (se não existir, então certamente você não precisará de nada além da meta-tag X-UA-Compatible que falei ali acima);

4. Abra o arquivo e crie as funções:

/// <summary>
    /// Método para preparar a renderização compatível com o IE8 (Emular IE7)
/// </summary>
    protected void Application_PreRequestHandlerExecute(object sender, EventArgs e)
    {
        Page p = this.Context.Handler as Page;
        if (p != null)
        {
            p.PreRenderComplete += new EventHandler(p_PreRenderComplete);
        }
    }
/// <summary>
   /// Método que associa o cabeçalho das páginas à compatibilidade IE8
/// </summary>
    protected void p_PreRenderComplete(object sender, EventArgs e)
    {
        Page page = sender as Page;
        if (page.Header != null)
        {
            HtmlMeta meta = null;
            foreach (Control var in page.Header.Controls)
            {
                HtmlMeta metaAux = var as HtmlMeta;
                if (metaAux != null && metaAux.HttpEquiv == "X-UA-Compatible")
                {
                    meta = metaAux;
                }
            }
            if (meta != null)
            {
                page.Header.Controls.Remove(meta);
                page.Header.Controls.AddAt(0, meta);
            }
        }
    }

5. Agora você precisa recompilar tudo, rodar novamente a aplicação e boa sorte.

Deu tudo certo? Me conta depois.

Mozilla

FireFox  v3.6

Keep your Browser up to date!

La fondation Mozilla à confirmé la mise en ligne de la version 3.6 Beta 1 de son navigateur vedette FireFox :

La v3.6 toujours la plus rapide des Firefox à ce jour !

Avec un tout petit peu de retard sur le calendrier la fondation Mozilla vient de mettre ligne samedi la version beta 1 de Firefox 3.6.

Cette version est disponible pour 50 pays, dont la France..

As of this date (10/22/09) my recommendation is not to install IE8 on XP. I had it installed for over two months after having used v. 7 for about 4 months. IE8 was slow to load, slow to launch tabs, and just slow overall … like a fat hog. Don’t do it to yourself … wait until MS makes a decent update. I reverted back to 6, but missed the tabs, so now I am once again happy with the performance and features in 7.

Good Luck! =)

Cuando estaba prendiendo mi Laptop veo en la Pagina Principal de MSN. Me encuentro con esto:

  Descargar el Nuevo Internet Explorer 8.

Y Nah, Decidí darle una oportunidad, lo descargué  y la gestión de complementos, junto con el manejo de descargas eran los dos principales fallos en las funcionalidades de Internet Explorer 7. Pues en IE8 se ha corregido en parte la primera carencia, agregándose un nuevo administrador de complementos que es un importante avance con respecto a lo que ya se tenía.  Algo así como tratar de Imitar al Firefox.

   Además el gestor de complementos de Firefox sigue siendo muy superior, permitiéndonos buscar y agregar add-ons sin abrir ninguna página, dándonos un control completo sobre ellos, tanto para cambiar sus opciones como para desactivarlos y desinstalarlos, y también incluyendo soporte para temas.

   De todas maneras, se nota que las extensiones y add-ons han sido prioridad en el desarrollo de Internet Explorer 8, ya que aparte de agregarse un gestor decente, también se ha introducido “Activities”, una tecnología exclusiva de IE que permite instalar complementos que potencien la función “Enviar a”, dándonos la posibilidad de acceder directamente a funciones como traductores, mapas o buscadores sin abrir una nueva página. Pero en cosas como está es donde se ven las ventajas de las aplicaciones open source.  ( Lo han liberado un poco )

En mi Opinión :

   IE8 consume más que WinXP
Un análisis de los recursos que necesita Internet Explorer 8 para correr indica que es un VERDADERO TRAGÓN de memoria. Dobla lo necesario en Firefox 3 y otros navegadores, pero es que además consume más memoria que Windows XP.

   No acaban ahí las sorpresas, ya que este estudio demostró que un sistema Windows XP instalado consume menos que este navegador. Nada más iniciarse todas las tareas que corren por defecto en Windows XP hacen que en un sistema con 1 Gbyte de memoria queden libres 800 Mbytes para el resto de aplicaciones que vayamos ejecutando. Sin embargo, al ejecutar IE8  de repente esa memoria disponible pasa a ser menos de la mitad de la que había. ¿Que raro no?

En Conclusión:

   A mi el internet Explorer, que nunca me ha gustado, además de muy aburrido y pesado. Sigo prefiriendo usar Firefox que dobla la Velocidad. Ya hemos de imaginar al IE8 cuanto consumirá de recursos, sobre todo RAM, con un Windows Vista e Reproductor de Audio, faltará que pidan unos 3GB de RAM como requisito mínimo.

Por eso sigue siendo el mejor Firefox. Tu sabes que eres mi Consentido, Firefox. . 

Por si no lo tienes, Descárgalo de Aquí.

See you later