13 May, 2008

Summary:

• These vulnerabilities affect: Windows 2000, XP, and Server 2003
• How an attacker exploits them: By enticing one of your users into opening a maliciously crafted Word (.doc) or .mdb file
• Impact: An attacker can execute code, potentially gaining complete control of your user's computer
• What to do: Install the appropriate Microsoft Jet 4.0 Database Engine update immediately

Exposure:

In a security bulletin released today as part of its monthly patch update, Microsoft describes a security vulnerability in the Joint Engine Technology (JET) database engine -- a database handling component that ships with Windows. The JET engine component suffers from a buffer overflow vulnerability involving the way it processes .mdb files. Although the flaw specifically lies in how Jet engine handles .mdb files, an attacker could easily embed an .mdb file into a Word document as well. So, potentially, attackers could leverage this vulnerability using booby-trapped Word documents. By enticing one of your users into downloading and opening such a document, an attacker could exploit this flaw to execute code on that user's machine, with that user's privileges. If the user has local administrator rights, the attacker would gain full control of the user's machine.

You probably remember this flaw from a Wire post we published back in March. In that post, we warned you that malicious attackers were exploiting this previously unpatched vulnerability in the wild, in what Microsoft called, "limited, targeted attacks." Now that Microsoft has finally fixed this vulnerability, we highly recommend you download, test, and deploy its patch immediately, before one of your users succumbs to this serious attack vector.

Solution Path:

The Microsoft Jet 4.0 Database Engine update fixes a significant issue which attackers are exploiting in the wild. You should download, test, and deploy the appropriate Microsoft Jet 4.0 Database Engine update immediately.

• Microsoft Jet 4.0 Database Engine update:
  •  
    • For Windows 2000
    • For Windows XP SP2
    • For Windows XP x64
    • For Windows Server 2003
    • For Windows Server 2003 Itanium
    • For Windows Server 2003 x64

Microsoft Vista and Server 2008 are not affected.

For All WatchGuard Users:

While you can configure some of WatchGuard's Firebox models to block all Word (.doc) and .mdb documents, most organizations need to allow Office documents in order to conduct business. Blocking them could bring your business to a halt. Therefore, the patches are your best recourse. Nevertheless, if you do wish to block any Office documents, follow the links below for our instructional videos on using your Firebox proxy's content blocking features:

• Firebox X Edge running 10.x
  • How do I block files with the FTP proxy? (Video, 2:30)
    Windows Media, 17.4MB   /    QuickTime, 11.8MB
  • How do I block files with the HTTP proxy? (Video, 2:52)
    Windows Media, 32MB   /    QuickTime, 28.6MB
  • How do I block files with the POP3 proxy? (Video, 2:35)
    Windows Media, 17.6MB   /    QuickTime, 16.5MB
  • How do I block files with the SMTP proxy? (Video, 2:18)
    Windows Media, 12.2MB   /    QuickTime, 9.1MB
  •  
• Firebox X Core and X Peak running Fireware 10.x
  • How do I block files with the FTP proxy? (Video, 2:30)
    Windows Media, 25.2MB   /    QuickTime, 9.1MB
  • How do I block files with the HTTP proxy? (Video, 2:52)
    Windows Media, 38.2MB   /    QuickTime, 10.7MB
  • How do I block files with the POP3 proxy? (Video, 2:35)
    Windows Media, 23.2MB   /    QuickTime, 10.1MB
  • How do I block files with the SMTP proxy? (Video, 2:18)
    Windows Media, 25.6MB   /    QuickTime, 9.0MB

Status:

Microsoft has released Microsoft Jet 4.0 Database engine to fix this vulnerability.

References:

• MS Security Bulletin MS08-028

13 May, 2008

Summary:

• These vulnerabilities affect: Many current versions of Microsoft Office for Windows and Mac (also affects Word Viewer and Office Compatibility Pack)
• How an attacker exploits them: By enticing you to open maliciously crafted Office documents
• Impact: An attacker can execute code, potentially gaining complete control of your computer
• What to do: Install the appropriate Office patches immediately

Exposure:

Today, Microsoft released two security bulletins describing three vulnerabilities found in components or programs that ship with Microsoft Office for Windows (and in one case, Office for Mac). Some of the vulnerabilities also affect Microsoft Word Viewer and the Office Compatibility Pack. Each vulnerability affects different versions of Office to a different extent. The three flaws affect different components and applications within Office, but the end result is always the same: By enticing one of your users into downloading and opening a maliciously crafted Office document, an attacker can exploit any of these vulnerabilities to execute code on a victim's computer, usually inheriting that user's level of privileges and permissions. If your user has local administrative privileges, the attacker gains full control of the user's machine.

According to Microsoft's bulletins, an attacker can exploit these flaws using three types of Office documents: Word (.doc), Publisher (.pub), and Rich Text Format (.rtf). So beware of all unexpected documents you receive with these file extensions.

If you'd like to learn more about each individual flaw, drill into the "Vulnerability Details" section of the security bulletins listed below:

• MS08-026: Two Word Vulnerabilities, rated Critical
• MS08-027: Publisher Code Execution Vulnerability, rated Critical

Solution Path

Microsoft has released patches for Office to correct all of these vulnerabilities. You should download, test, and deploy the appropriate patches throughout your network immediately.

MS08-026:

Word update for:

• Office 2000 w/SP3
• Office XP w/SP3
• Office 2003 w/SP3
  • Word Viewer 2003
• 2007 Microsoft Office System w/SP1
• Office 2004 for Mac
• Office 2008 for Mac
• Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats

MS08-027:

Publisher update for:

• Office 2000 w/SP3
• Office XP w/SP3
• Office 2003 w/SP3
• 2007 Microsoft Office System w/SP1

For All WatchGuard Users:

While you can configure certain WatchGuard Firebox models to block Word, Publisher, and Rich Text Format documents, some organizations need to allow them in order to conduct business. Therefore, these patches are your best recourse. Temporarily though, you may still want to block these Office documents until you are able to install Microsoft's patches.

If you want to block Word, Publisher, and Rich Text Format documents, follow the links below for video instructions on using your Firebox proxy's content blocking features to block .doc, .pub, and .rtf files by their file extensions:

• Firebox X Edge running 10.x
  • How do I block files with the FTP proxy? (Video, 2:30)
    Windows Media, 17.4MB   /    QuickTime, 11.8MB
  • How do I block files with the HTTP proxy? (Video, 2:52)
    Windows Media, 32MB   /    QuickTime, 28.6MB
  • How do I block files with the POP3 proxy? (Video, 2:35)
    Windows Media, 17.6MB   /    QuickTime, 16.5MB
  • How do I block files with the SMTP proxy? (Video, 2:18)
    Windows Media, 12.2MB   /    QuickTime, 9.1MB
  •  
• Firebox X Core and X Peak running Fireware 10.x
  • How do I block files with the FTP proxy? (Video, 2:30)
    Windows Media, 25.2MB   /    QuickTime, 9.1MB
  • How do I block files with the HTTP proxy? (Video, 2:52)
    Windows Media, 38.2MB   /    QuickTime, 10.7MB
  • How do I block files with the POP3 proxy? (Video, 2:35)
    Windows Media, 23.2MB   /    QuickTime, 10.1MB
  • How do I block files with the SMTP proxy? (Video, 2:18)
    Windows Media, 25.6MB   /    QuickTime, 9.0MB

Status:

Microsoft has released Office updates to fix these vulnerabilities.

References:

• MS Security Bulletin MS08-026
• MS Security Bulletin MS08-027

Para Inscribirte, puedes hacer click Aqui
 

Registration Options

Event ID: 1032376194

 

Para transformar suas pastas em menus, siga os próximos passos:
1. Após fazer o download do arquivo, descompacte-o em um novo diretório (por exemplo, C:\standalonestack)

2. Neste diretório, crie um atalho do arquivo StandaloneStack. Para isso, basta clicar com o botão direito do mouse sobre o arquivo e selecionar a opção “Criar Atalho”.

3. Agora, clique com o botão direito no atalho, selecione a opção “Propriedades” e no final do campo “Destino” digite o nome do menu pilha que será criado, por exemplo “arquivos” (sem aspas) e clique em OK. Lembre-se que cada menu deverá ter um nome diferente.

4. O campo destino deverá conter “C:\standalonestack\StandaloneStack.exe arquivos”.

5. Depois disso, dê um duplo clique no atalho e o menu do programa deverá aparecer. Você escolhe a pasta que deseja transformar em menu pilha e clica em OK.

Fonte: Baixaki

Description:
File size uncompressed is 769 MB.

Requirements:

* 1 GHz 32-bit (x86) or 64-bit (x64) processor
* 1 GB of system memory
* 40 GB hard drive with at least 15 GB of available space

Support for DirectX 9 graphics with:

* WDDM Driver
* 128 MB of graphics memory (minimum)
* Pixel Shader 2.0 in hardware
* 32 bits per pixel
* DVD-ROM drive
* Audio Output

DESCARGAR

http://rapidshare.com/files/114474106/Windows_Vista.zip

• Sistemas Operacionais com Suporte: Windows Vista; Windows Vista x64; Windows Vista SP1; Windows Vista x64 SP1

Download: Update (KB905866) x86

Download: Update (KB905866) x64

Fonte: Baboo

The Windows Installer (msiexec.exe) can be ran at the command line to extract files directly using an administrative install.

How?

msiexec /a “YourMSIPackage.msi” /qb TARGETDIR=”DRIVE:\YourTargetPath”

Switches used:

/a – Administrative installation
/qb – Basic UI (simple GUI progress bar)

This is a lot easier than hacking it using WinRAR. :)

Ahora es General Motors quien renuncia a utilizar el sistema operativo de Microsoft porque no es compatible con parte de su software. Prefieren esperar a la llegada, que se producirá en los próximos años, de un nuevo Windows 7 -esperemos que mucho más pulido que el Vista-. Mientras tanto, la ofensiva de Microsoft pasa por retirar del mercado en junio la versión XP.

Ordenador portatil de Steve Ballmer, CEO de Microsoft

Y es que tienen toda la razón, Windows Vista ha sido una equivocación en toda regla tanto para empresas como para usuarios particulares. La escasa combatibilidad con determinado sofware y la incomodidad que produce tener que estar cerrando unas y otras ventanas de emergencia hacen de este producto una herramienta mala para el trabajo diario.

Echemos un ojo a las estadísticas: El 60% de los usuarios particulares y un 70% de empresas nos mantenemos fieles a Windows XP, un 94% de ordenadores nuevos viene con Vista preinstalado pero para las empresas el dato es menor, un 25% de ellas utilizan todavía XP aun teniendo ordenadores nuevos.

La diferencia entre particulares y empresas deriva de la posibilidad que ofrece Microsoft para poder encargar sus ordenadores con XP a las compañías, todo un lujo al que los particulares no podemos acceder y más sabiendo que en 2009 se retirará el servicio técnico para XP, una putada -hablando en plata- para muchos.

Não é difícil entender o que acontece. No passado, era natural desenvolver um sistema operacional ou aplicativo pensando no hardware que estava por vir. Mesmo que o software não rodasse bem nos micros existentes, funcionaria nos novos computadores que chegassem às lojas. Isso ainda acontece em vários segmentos do mercado. Mas há certas categorias de computador que evoluem em outras direções. É o caso dos ultraportáteis de baixo custo, que vêm ganhando espaço com o sucesso do EeePC, da Asus. Com capacidade insuficiente para rodar o Windows Vista, eles acabariam adotando o Linux (o Eee PC começou rodando Linux, mas agora tem também o XP com opção).

Para manter sua presença nesses computadores fraquinhos, a Microsoft tinha basicamente três opções. Poderia lançar alguma variante do Windows Mobile para eles. A empresa já tentou isso no passado com o Windows CE, mas não deu muito certo. Os usuários queriam os aplicativos que rodam no Windows XP (que não rodam no CE). Outra opção era enxugar o Vista para ele rodar nesses dispositivos. Há gente trabalhando nisso na Microsoft. Mas esse é um projeto demorado e de resultados incertos. A terceira opção era prolongar a vida do Windows XP. Considerando a boa aceitação do XP no mercado, essa alternativa faz sentido.

O visual da versão para XP está mais 'Vistalizado' e sem dúvida, bonito

Ampliar

Fonte: BlogWindows

PDC Longhorn Logon Vista

Para instalar essa logon, será necessário o programa LogonStudio Vista.

deviantART

Longhorn Fusion Public Beta II

deviantART

PARA INSTALARLO

The CLR profiler is great; it’s sweet to be able to see where memory is allocated and how well objects are disposed of (and whether or not I missed something that GC just isn’t catching). 

The form is pretty easy to use, but there’s a bit of a trick for VS 2008 web application profiling when using the built-in Web Development Server.

NOTE:  This isn’t anything like the ANTS Profiler (which I wish I had a license for, but don’t).  ANTS will tell you where code slowdowns are and more, this simply returns back histographs of object usage, memory, and the stack/heap.  Still very useful none the less.

Here’s how to get started:

1. Download the CLR profiler (see the link at the beginning of this article or click here).

2. Extract the profiler into a directory (it defaults to C:\CLRProfiler); it will extract two directory structures (binaries, source) and a readme document.

3. To start using the application immediately, browse into the Binaries directory and execute the CLRProfiler. 

Use the x86 version. I haven’t been able to get the x64 version to work correctly (even though I’m on a x64 machine) when profiling .NET web applications ala the built-in web development server.

4. Under File > Set Parameters, modify the “Command Line” to reflect the parameters required to start the built-in web development server.  After the parameters have been set, click OK.

Usually, you have a Port parameter and a Path parameter.  Here’s an example:

/port:1234 /path:“J:\Projects\Work\Current\ERC\web\”

5. Click ‘Start Application’.  A browse window will open.  Visual Studio 2008’s web development server is located in the Common Files directory.

%CommonProgramFiles%
    \Microsoft Shared\DevServer\9.0
or
%CommonProgramFiles(x86)
    \Microsoft Shared\DevServer\9.0

6. After selecting the WebDev.WebServer.Exe application file, your server will kick off with the parameters you set.

Now you’re ready to open up a web browser, begin browsing around, and evaluate your application.  When finished, click the ‘Kill Application’ button on the Profiler or simply close the WebServer application.

In my opinion, this isn’t a service pack—this is a new version!

There are quite a few bug fixes (what you normally associate with a service pack), but also a huge list of new additions and improvements.

From Somasegar:

Traditionally our service packs address a range of issues found both through customer and partner feedback as well as our own internal testing.  While this service pack holds true to that theme and delivers updates for these types of issues, it also builds on the tremendous value that Visual Studio 2008 and .NET Framework 3.5 deliver today and enables an improved developer experience by adding a number of additional components that cover a range of highly requested customer features. For example, the service pack is the first release for Visual Studio 2008 that delivers full support for SQL Server 2008 and the ADO.NET Entity Framework.

I’ve posted a few links at the end of the post to the more extensive sources right now, take a look and get ready for the plunge.

So, what am I most excited about?

• ADO.NET Entity Framework – I’m hoping that the “real” release motivates Oracle to develop provides for the entity framework and my dream of LINQ-esque connections to Oracle will be realized.
• ASP.NET Routing Engine – As the MVC framework gets closer to a production reality, it’s very motivating to see the underpinnings already in place.
• VS2008 Performance Improvements – Anything has to be an improvement. :(
• JavaScript Code Formatting – Sweet, now if I can only get JavaScript intellisense to work. :(
• LINQ Debug Support – Very nice, love seeing the generated SQL right there at debug time.

There are also lots of updates to WCF and WPF.  Hopefully this summer I’ll have more time to use these .NET 3.0 technologies and maybe be a bit more excited. ;)

Visual Studio 2008 GUI/Tools

The Web Developer Tools team has released a comprehensive list of designer bug fixes, IIS templates and modules, formatting changes, intellisense upgrades, and more on their blog.

MVC and URL Routing

Phil Haack details the effects of the URL routing changes on the MVC Preview releases as well as how it affects the upcoming Preview 3.

Everything

ScottGu, as always does an excellent job tying everything up together—designer, framework, and tooling.

Now, if ReSharper 4.0 would EVER get to RTW before we’re ready to VS2009, it’d be super!

Die Zahlen lassen sich allerdings nicht einfach miteinander vergleichen. Auch die Verbreitung des jeweiligen Betriebssystems spielt eine entscheidende Rolle. Bei der Auswertung der Testergebnisse hat sich gezeigt, dass unter Windows Vista zwar pro Rechner derzeit seltener Malware auftritt als bei XP. Dennoch gehen die Sicherheitsexperten davon aus, dass die Infektionsrate künftig erheblich steigen könnte, da Vista bisher weniger verbreitet ist als die Vorgängerversion. Angriffe sind daher bislang noch weitgehend uninteressant für Hacker. Mit steigendem Verbreitungsgrad des Betriebssystems dürfte Windows Vista verstärkt in den Fokus der Cyber-Kriminellen geraten, weil es dann ein lohnenderes Ziel für Online-Attacken darstellt.

Quelle: Global Press

Pesquisa revela que para cada mil máquinas rodando Vista a empresa detectou 639 ameaças, em um período de 6 meses e rodando XP foram encontrados 1021 ameaças no mesmo período.

Esse fato reforça a investida da Microsoft, que levantou a bandeira em defesa do seu mais novo sistema operacional, claro, e divulgou que seu novo produto seria 60% mais seguro que seu antecessor, o que não é totalmente verdade.

Especialistas afirmam que a plataforma é realmente mais segura, mas por si só, e usando suas ferramentas padrões, não tem o poder de fogo ideal que é necessário hoje para se manter seguro na rede, é necessário apelar para softwares de terceiros e ferramentas mais poderosas.

Fica aí a dica!!!

So how did Vista come to be the target of so much derision? To understand that you need to see Vista not from the perspective of someone buying a typical Vista PC of today, but of someone transitioning from XP a year ago.

Vista introduced new and very resource hungry user interface technology. In truth, quite a hike was needed in computing power to run Vista properly. However, PC vendors were selling a lot of PCs that were "Vista capable" but only just, in order to keep prices down. The result was that buyers would spend good money on a machine that looked good on paper but performed like a pig.

Then factor in that the only significant new selling point was the 3D graphical interface technology, but it wasn't used all that impressively and the novelty soon wore off.

Then factor in that early on Vista was plagued by incompatibilities, specific performance issues and bugs. No worse than XP had been in its day, but that was a long time ago and people forget.

Then factor in the long gestation, the sense of anticipation, the completely over the top hype from Microsoft set against the actual experience: a slow, buggy OS (when compared with a by now very mature XP) and just a bit of not very exciting eye candy to show for it.

Then factor in some general drift in public sentiment away from Microsoft for a variety of reasons.

Then factor in the age of the blog. Blogs like this one, started by real Vista early adopters who experienced all the things described above and now had the perfect medium to share their opinions with the world. Not that I'm claiming credit for denting Vista's reputation single handedly. But all the blogs and negative press in general have, collectively, taken their toll.

So the Vista of today is pretty much alright, but the reputational damage is done. Microsoft will want to usher in Vista 7 (AKA Vista SP2) as soon as they can in the hope of leaving their Vista woes behind them. I'm not confident about their chances.

En mai 2008, les données vont encore en ce sens.

L'action de Microsoft est à 29,99$ toujours plus basse que le 30,49$ le jour du lancement de Windows Vista le 30 janvier 2007.  Donc rendement négatif de l'action depuis 1 ans et 4 mois.

Windows Vista ressemble de plus en plus à Windows ME vous vous rappelez, ce flop de Microsoft?

Microsoft avait promis une campagne publicitaire hors du commun pour le lancement de Vista... j'ai encore pas vu grand chose à la télé.

Moi je continue de voguer sur Windows XP et avec joie.

Tiens un blogue pour ceux et celles qui veulent sauver XP.
http://weblog.infoworld.com/save-xp/ 

Oui je sais vous allez me dire que vous avez investi dans Google à la place.  Croyez vous vraiment que Google sortiront un système d'exploitation capable de rivaliser Microsoft?  Bien sûr que non.  Leurs crénaux se sont de vendre de la publicité et des logiciels gratuits.

J'ai rarement vu un empire se bâtir en distribuant du gratuit.