VMware Player 4.0.4 Build 744019

VMware Player 4.0.4 Build 744019 es la forma más sencilla de ejecutar múltiples sistemas operativos al mismo tiempo en su PC. Con su interfaz fácil de usar, VMware Player hace sin esfuerzo para cualquiera de probar Windows 7 o ejecutar la última versión de Linux.

  • VMware Player pueden ejecutar Windows XP, Windows 7, Ubuntu 9.10 y RHEL 5, al mismo tiempo en ventanas separadas!
  • Instalación sencilla hace que la creación de máquinas virtuales con la última de 32-bit y Windows 64-bit y el sistema operativo Linux más fácil que instalar directamente en su PC.
  • Ejecutar las empresas de máquinas virtuales, test de nuevos sistemas operativos y tratar con seguridad el nuevo software en un entorno aislado en su PC.
  • Construida sobre más de 10 años de excelencia de virtualización, la plataforma de virtualización avanzada de VMware puede manejar las aplicaciones más exigentes.

Desarrollador:vmware.com

Descargar:VMware Player 4.0.4 Build 744019

General Issues

  • Linux guests running the Linux kernel version 2.6.34 or later could not be pinged from the host via an IPv6 address.
  • On rare occasions, Linux guests would suddenly fail to Autofit or enter Unity.
  • Unity mode would exit if the title bar of an application contained certain non UTF-8 encoded extended ASCII characters.
  • On Windows hosts, the VMware Player user interface sometimes became unresponsive when minimized from full-screen mode if the suggestion balloon was being displayed.
  • On Windows hosts, the user interface sometimes became unresponsive if the application was rendered on an extended display that was abruptly disconnected.

Security Issues

  • VMware host Checkpoint file memory corruption
    Input data was not properly validated when loading Checkpoint files. This issue could have allowed an attacker with the ability to load a specially crafted Checkpoint file to execute arbitrary code on the host.
    The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-3288 to this issue.
  • VMware virtual machine remote device denial of service
    A device (such as CD-ROM or keyboard) that is available to a virtual machine while physically connected to a system that does not run the virtual machine is referred to as a remote device. Traffic coming from remote virtual devices was incorrectly handled. This issue could have allowed an attacker who was capable of manipulating the traffic from a remote virtual device to crash the virtual machine.
    The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-3289 to this issue.

 

Google Chrome 19.0.1084.52

Google Chrome 19.0.1084.52.Este navegador web tiene una interfaz sencilla y funcional. Para la mayoría de los usuarios el navegador no es lo más importante en su experiencia en la Red: sólo es una herramienta donde visualizar y ejecutar los sitios, páginas web y las aplicaciones que la conforman. Al igual que la página de inicio de nuestro buscador, Google Chrome es rápido y fácil de utilizar. Su objetivo es que los usuarios obtengan la información que buscan y accedan a los sitios web con la mayor rapidez posible.

 

google-chrome-gratis-gratis-net

  • Busca desde la barra de direcciones
    Escribe en la barra de direcciones y obtén sugerencias para búsquedas y para páginas web.
  • Miniaturas de las páginas más visitadas
    Accede a tus páginas favoritas a gran velocidad desde una pestaña nueva.
  • Navegación privada
    Abre una ventana de incógnito cuando no quieras guardar el historial de navegación.

Descargar:Google Chrome 19.0.1084.52 portable

Descargar:Google Chrome 19.0.1084.52

Cambios y modificaciones en esta versión Google Chrome 19.0.1084.52

The Chrome Stable channel has been updated to 19.0.1084.52 on Windows, Mac, Linux and Chrome Frame.  

Security fixes and rewards:

Please see the Chromium security page for more detail. Note that the referenced bugs may be kept private until a majority of our users are up to date with the fix.

  • [117409] High CVE-2011-3103: Crashes in v8 garbage collection. Credit to the Chromium development community (Brett Wilson).
  • [118018] Medium CVE-2011-3104: Out-of-bounds read in Skia. Credit to Google Chrome Security Team (Inferno).
  • [$1000] [120912] High CVE-2011-3105: Use-after-free in first-letter handling. Credit to miaubiz.
  • [122654] Critical CVE-2011-3106: Browser memory corruption with websockets over SSL. Credit to the Chromium development community (Dharani Govindan).
  • [124625] High CVE-2011-3107: Crashes in the plug-in JavaScript bindings. Credit to the Chromium development community (Dharani Govindan).
  • [$1337] [125159] Critical CVE-2011-3108: Use-after-free in browser cache. Credit to “efbiaiinzinz”.
  • [Linux only] [$1000] [126296] High CVE-2011-3109: Bad cast in GTK UI. Credit to Micha Bartholomé.
  • [126337] [126343] [126378] [127349] [127819] [127868] High CVE-2011-3110: Out of bounds writes in PDF. Credit to Mateusz Jurczyk of the Google Security Team, with contributions by Gynvael Coldwind of the Google Security Team.
  • [$500] [126414] Medium CVE-2011-3111: Invalid read in v8. Credit to Christian Holler.
  • [127331] High CVE-2011-3112: Use-after-free with invalid encrypted PDF. Credit to Mateusz Jurczyk of the Google Security Team, with contributions by Gynvael Coldwind of the Google Security Team.
  • [127883] High CVE-2011-3113: Invalid cast with colorspace handling in PDF. Credit to Mateusz Jurczyk of the Google Security Team, with contributions by Gynvael Coldwind of the Google Security Team.
  • [128014] High CVE-2011-3114: Buffer overflows with PDF functions. Credit to Google Chrome Security Team (scarybeasts).
  • [$1000] [128018] High CVE-2011-3115: Type corruption in v8. Credit to Christian Holler.

FileZilla 3.3.5 Final

FileZilla 3.3.5 Final es un cliente FTP para Windows, Linux, FreeBSD y MacOS gratis, libre y de código abierto. Soporta FTP, SFTP y FTP sobre SSL.
Las principales características son el Site Manager (Administrador de sitios), Message Log (Registro de mensajes), y Transfer Queue (Cola de transferencia).El administrador de sitios permite a un usuario crear una lista de sitios FTP con sus datos de conexión, como el número de puerto a usar, o si se utiliza inicio de sesión normal o anónima. Para el inicio normal, se guarda el usuario y opcionalmente la contraseña.

filiezilla-gratis.gif

Desarrollador:filezilla.sourceforge.net

Descargar:FileZilla 3.3.5 Final

Lista de Cambios FileZilla Portable 3.2.3
2010-11-14 – FileZilla Client 3.3.5 releasedBugfixes and minor changes:
Updated language files, otherwise identical with rc1

2010-11-07 – FileZilla Client 3.3.5-rc1 releasedNew features:
FTP over TLS certificate store is now host-specific
MSW: Large-DPI awareness
Improved SFTP transfer speeds
FTP over TLS should prefer ciphers with longer key sizes, updated contained GnuTLS library in precompiled binaries
Add context menu entry to re-queue all files on the successful and failed queue tabs
MSW: Native file list sort indicator on Windows Vista and 7
Bugfixes and minor changes:
Resuming of uploads was not working correctly in all cases
Correct remaining time calculation in queue
Do not show welcome dialog in kiosk mode 2
Do not offer option to permanently accept certificate in kiosk mode 2
Fix sorting by size in filelists with directory sort behavior set to inline
MSW: Fix memory corruption when changing language
OS X: Include license and documentation files in application bundle
Directly save settings after importing from file

PHP 5.3.3 Released!

PHP 5.3.3 Released! El equipo de desarrollo de PHP se complace en anunciar la inmediata disponibilidad de PHP 5.3.3 . Este lanzamiento se centra en la mejora de la estabilidad y la seguridad de la rama 5.3.x de PHP con más de 100 correcciones de errores, algunos de los cuales están relacionados con la seguridad . Todos los usuarios son alentados a actualizar a esta versión.

Desarrollador:php.net

Descargar:PHP 5.3.3 (tar.bz2)

Cambios y modificaciones en esta versión PHP 5.3.3

Security Enhancements and Fixes in PHP 5.3.3:

  • Rewrote var_export() to use smart_str rather than output buffering, prevents data disclosure if a fatal error occurs (CVE-2010-2531).
  • Fixed a possible resource destruction issues in shm_put_var().
  • Fixed a possible information leak because of interruption of XOR operator.
  • Fixed a possible memory corruption because of unexpected call-time pass by refernce and following memory clobbering through callbacks.
  • Fixed a possible memory corruption in ArrayObject::uasort().
  • Fixed a possible memory corruption in parse_str().
  • Fixed a possible memory corruption in pack().
  • Fixed a possible memory corruption in substr_replace().
  • Fixed a possible memory corruption in addcslashes().
  • Fixed a possible stack exhaustion inside fnmatch().
  • Fixed a possible dechunking filter buffer overflow.
  • Fixed a possible arbitrary memory access inside sqlite extension.
  • Fixed string format validation inside phar extension.
  • Fixed handling of session variable serialization on certain prefix characters.
  • Fixed a NULL pointer dereference when processing invalid XML-RPC requests (Fixes CVE-2010-0397, bug #51288).
  • Fixed SplObjectStorage unserialization problems (CVE-2010-2225).
  • Fixed possible buffer overflows in mysqlnd_list_fields, mysqlnd_change_user.
  • Fixed possible buffer overflows when handling error packets in mysqlnd.

Key enhancements in PHP 5.3.3 include:

  • Upgraded bundled sqlite to version 3.6.23.1.
  • Upgraded bundled PCRE to version 8.02.
  • Added FastCGI Process Manager (FPM) SAPI.
  • Added stream filter support to mcrypt extension.
  • Added full_special_chars filter to ext/filter.
  • Fixed a possible crash because of recursive GC invocation.
  • Fixed bug #52238 (Crash when an Exception occured in iterator_to_array).
  • Fixed bug #52041 (Memory leak when writing on uninitialized variable returned from function).
  • Fixed bug #52060 (Memory leak when passing a closure to method_exists()).
  • Fixed bug #52001 (Memory allocation problems after using variable variables).
  • Fixed bug #51723 (Content-length header is limited to 32bit integer with Apache2 on Windows).
  • Fixed bug #48930 (__COMPILER_HALT_OFFSET__ incorrect in PHP >= 5.3).

Google Chrome 5.0.375.70 Final

Google Chrome 5.0.375.70 Final es un navegador que combina diseño minimalista con una tecnología sofisticada para hacer la web más rápido, más seguro y más fácil. Tiene un cuadro para todo: Escribe en la barra de direcciones y obtén sugerencias para búsquedas y páginas web. Le dará las miniaturas de tus sitios preferidos; Accede a tus páginas favoritas a gran velocidad de la luz desde una pestaña nueva. Google Chrome es un navegador web de código abierto desarrollado por Google. Su arquitectura de software fue diseñado desde cero (con componentes de otros programas de código abierto como WebKit y Mozilla Firefox) para atender a las necesidades cambiantes de los usuarios y reconociendo que hoy la mayoría de los sitios web no son páginas web, sino aplicaciones web. Los objetivos de diseño incluyen la estabilidad, velocidad, seguridad y una interfaz limpia, de uso sencillo y eficaz.

google-chrome-gratis-gratis-net

Desarrollador:www.google.com/chrome

Descargar:Google Chrome 5.0.375.70 Final

Cambios y modificaciones en esta versión Google Chrome 5.0.375.70 Final

his release fixes the following security issues:

  • [15766] Medium Cross-origin keystroke redirection. Credit to Michal Zalewski of Google Security Team.
  • [$2000] [39985] High Cross-origin bypass in DOM methods. Credit to Sergey Glazunov.
  • [$500] [42723] High Memory error in table layout. Credit to wushi of team509.
  • [Linux only] [43304] High Linux sandbox escape. Credit to Mark Dowd under contract to Google Chrome Security Team.
  • [43307] High Bitmap stale pointer. Credit to Mark Dowd under contract to Google Chrome Security Team.
  • [43315] High Memory corruption in DOM node normalization. Credit to Mark Dowd under contract to Google Chrome Security Team.
  • [43487] High Memory corruption in text transforms. Credit to wushi of team509.
  • [43902] Medium XSS in innerHTML property of textarea. Credit to sirdarckcat of Google Security Team.
  • [44740] High Memory corruption in font handling. Credit: Apple.
  • [44868] High Geolocation events fire after document deletion. Credit to Google Chrome Security Team (Justin Schuh).
  • [44955] High Memory corruption in rendering of list markers. Credit: Apple.

Google Chrome 4.1.249.1064 Final

Google Chrome 4.1.249.1064 Final -Bug and Security Fixes-.Este navegador web tiene una interfaz sencilla y funcional. Para la mayoría de los usuarios el navegador no es lo más importante en su experiencia en la Red: sólo es una herramienta donde visualizar y ejecutar los sitios, páginas web y las aplicaciones que la conforman. Al igual que la página de inicio de nuestro buscador, Google Chrome es rápido y fácil de utilizar. Su objetivo es que los usuarios obtengan la información que buscan y accedan a los sitios web con la mayor rapidez posible.

google-chrome-gratis-gratis-net

  • Busca desde la barra de direcciones
    Escribe en la barra de direcciones y obtén sugerencias para búsquedas y para páginas web.
  • Miniaturas de las páginas más visitadas
    Accede a tus páginas favoritas a gran velocidad desde una pestaña nueva.
  • Navegación privada
    Abre una ventana de incógnito cuando no quieras guardar el historial de navegación.

Descargar:Google Chrome 4.1.249.1064 Final

Cambios y modificaciones en esta versión Google Chrome 4.1.249.1064 Final
Google Chrome 4.1.249.1064 has been released to the Stable channel on Windows.

This release fixes the following issues:
Google Chrome was not using the correct path for the Java plugin for Java Version 6 Update 20.
4.1.249.1059 was much slower on JavaScript benchmarks than 4.1.249.1045. (Issue 42158)

This release also fixes the following security issues:
Please see the Chromium security page for more detail. Note that the referenced bugs may be kept private until a majority of our users are up to date with the fix.

[$1000] [40445] High Cross-origin bypass in Google URL (GURL). Credit: Jordi Chancel.
[40487] High Memory corruption in HTML5 Media handling. Credit: David Bloom of Google Security Team.
[$500] [42294] High Memory corruption in font handling. Credit: wushi of team509.

MySQL 5.1.43

MySQL 5.1.43 es un sistema de gestión de base de datos relacional, multihilo y multiusuario.

MySQL is the world’s most popular open source database software, with over 100 million copies of its software downloaded or distributed throughout its history. With superior speed, reliability, and ease of use, MySQL has become the preferred choice of corporate IT Managers because it eliminates the major problems associated with downtime, maintenance, administration and support.

MySQL es muy utilizado en aplicaciones web como MediaWiki o Drupal, en plataformas (Linux/Windows-Apache-MySQL-PHP/Perl/Python), y por herramientas de seguimiento de errores como Bugzilla.

MySQL es una base de datos muy rápida en la lectura cuando utiliza el motor no transaccional MyISAM, pero puede provocar problemas de integridad en entornos de alta concurrencia en la modificación.

Desarrollador:mysql.com

Descargar:MySQL 5.1.43 Windows

Descargar:MySQL 5.1.43  Windows x64

Cambios y modificaciones en esta versión MySQL 5.1.43

  • This release includes InnoDB Plugin 1.0.6. This version is considered of Release Candidate (RC) quality.

Functionality added or changed:

  • Partitioning: The UNIX_TIMESTAMP() function is now supported in partitioning expressions using TIMESTAMP columns. For example, it now possible to create a partitioned table such as this one:
    CREATE TABLE t (c TIMESTAMP) 
    PARTITION BY RANGE ( UNIX_TIMESTAMP(c) ) (
        PARTITION p0 VALUES LESS THAN (631148400),
        PARTITION p1 VALUES LESS THAN (946681200),
        PARTITION p2 VALUES LESS THAN (MAXVALUE)
    );
    

    All other expressions involving TIMESTAMP values are now rejected with an error when attempting to create a new partitioned table or to alter an existing partitioned table.

    When accessing an existing partitioned table having a timezone-dependent partitioning function (where the table was using a previous version of MySQL), a warning rather than an error is issued. In such cases, you should fix the table. One way of doing this is to alter the table’s partitioning expression so that it uses UNIX_TIMESTAMP(). (Bug#42849)

Bugs fixed:

  • Security Fix: For servers built with yaSSL, a preauthorization buffer overflow could cause memory corruption or a server crash. We thank Evgeny Legerov from Intevydis for providing us with a proof-of-concept script that allowed us to reproduce this bug. (Bug#50227, CVE-2009-4484)
  • Important Change: Replication: The RAND() function is now marked as unsafe for statement-based replication. Using this function now generates a warning when binlog_format=STATEMENT and causes the the format to switch to row-based logging when binlog_format=MIXED.

    This change is being introduced because, when RAND() was logged in statement mode, the seed was also written to the binary log, so the replication slave generated the same sequence of random numbers as was generated on the master. While this could make replication work in some cases, the order of affected rows was still not guaranteed when this function was used in statements that could update multiple rows, such as UPDATE or INSERT ... SELECT; if the master and the slave retrieved rows in different order, they began to diverge. (Bug#49222)

  • Partitioning: When used on partitioned tables, the records_in_range handler call checked all partitions, rather than the unpruned partitions only. (Bug#48846)

    See also Bug#37252, Bug#47261.

  • Partitioning: A query that searched on a ucs2 column failed if the table was partitioned. (Bug#48737)
  • Replication: A LOAD DATA INFILE statement that loaded data into a table having a column name that must be escaped (such as `key` INT), caused replication to fail when logging in mixed or statement mode. In such cases, the master wrote the LOAD DATA event to the binary log without escaping the field names. (Bug#49473)

    See also Bug#47927.

  • Replication: Spatial data types cause row-based replication to crash. (Bug#48776)
  • Replication: A flaw in the implementation of the purging of binary logs could result in orphaned files being left behind in the following circumstances:
    • If the server failed or was killed while purging binary logs.

      If the server failed or was killed after creating of a new binary log when the new log file was opened for the first time.

    In addition, if the slave was not connected during the purge operation, it was possible for a log file that was in use to be removed; this could lead data loss and possible inconsistencies between the master and slave. (Bug#45292)

  • Replication: When using the STATEMENT or MIXED logging format, the statements LOAD DATA CONCURRENT LOCAL INFILE and LOAD DATA CONCURRENT INFILE were logged as LOAD DATA LOCAL INFILE and LOAD DATA LOCAL INFILE, respectively (in other words, the CONCURRENT keyword was omitted). As a result, when using replication with either of these logging modes, queries on the slaves were blocked by the replication SQL thread while trying to execute the affected statements. (Bug#34628)
  • Replication: Manually removing entries from the binary log index file on a replication master could cause the server to repeatedly send the same binary log file to slaves. (Bug#28421)
  • Cluster Replication: When expire_logs_days was set, the thread performing the purge of the log files could deadlock, causing all binary log operations to stop. (Bug#49536)
  • Within a stored routine, selecting the result of CONCAT_WS() with a routine parameter argument into a user variable could return incorrect results. (Bug#50096)
  • The IBMDB2I storage engine was missing from the i5os 64-bit distribution of MySQL 5.1.42. It is now included again. (Bug#50059)
  • EXPLAIN EXTENDED UNION ... ORDER BY caused a crash when the ORDER BY referred to a nonconstant or full-text function or a subquery. (Bug#49734)
  • The push_warning_printf() function was being called with an invalid error level MYSQL_ERROR::WARN_LEVEL_ERROR, causing an assertion failure. To fix the problem, MYSQL_ERROR::WARN_LEVEL_ERROR has been replaced by MYSQL_ERROR::WARN_LEVEL_WARN. (Bug#49638)
  • Some prepared statements could raise an assertion when re-executed. (Bug#49570)
  • A Valgrind error in make_cond_for_table_from_pred() was corrected. Thanks to Sergey Petrunya for the patch to fix this bug. (Bug#49506)
  • When compiling on Windows, an error in the CMake definitions for InnoDB would cause the engine to be built incorrectly. (Bug#49502)
  • Valgrind warnings for CHECKSUM TABLE were corrected. (Bug#49465)
  • Specifying an index algorithm (such as BTREE) for SPATIAL or FULLTEXT indexes caused a server crash. These index types do not support algorithm specification, and it is now disallowed to do so. (Bug#49250)
  • The optimizer sometimes incorrectly handled conditions of the form WHERE col_name='const1' AND col_name='const2'. (Bug#49199)
  • Execution of DECODE() and ENCODE() could be inefficient because multiple executions within a single statement reinitialized the random generator multiple times even with constant parameters. (Bug#49141)
  • MySQL 5.1 does not support 2-byte collation numbers, but did not check the number and crashed for out-of-range values. (Bug#49134)
  • With binary logging enabled, REVOKE ... ON {PROCEDURE|FUNCTION} FROM ... could cause a crash. (Bug#49119)
  • The LIKE operator did not work correctly when using an index for a ucs2 column. (Bug#49028)
  • check_key_in_view() was missing a DBUG_RETURN in one code branch, causing a crash in debug builds. (Bug#48995)
  • Several strmake() calls had an incorrect length argument (too large by one). (Bug#48983)
  • On Fedora 12, strmov() did not guarantee correct operation for overlapping source and destination buffer. Calls were fixed to use an overlap-safe version instead. (Bug#48866)
  • Incomplete reset of internal TABLE structures could cause a crash with eq_ref table access in subqueries. (Bug#48709)
  • Re-execution of a prepared statement could cause a server crash. (Bug#48508)
  • The error message for ER_UPDATE_INFO was subject to buffer overflow or truncation. (Bug#48500)
  • SHOW BINLOG EVENTS could fail with a error: Wrong offset or I/O error. (Bug#48357)
  • Valgrind warnings related to binary logging of LOAD DATA INFILE statements were corrected. (Bug#48340)
  • An aliasing violation in the C API could lead to a crash. (Bug#48284)
  • With one thread waiting for a lock on a table, if another thread dropped the table and created a new table with the same name and structure, the first thread would not notice that the table had been re-created and would try to used cached metadata that belonged to the old table but had been freed. (Bug#48157)
  • The InnoDB Monitor could fail to print diagnostic information after a long lock wait. (Bug#47814)
  • Queries containing GROUP BY ... WITH ROLLUP that did not use indexes could return incorrect results. (Bug#47650)
  • If an invocation of a stored procedure failed in the table-open stage, subsequent invocations that did not fail in that stage could cause a crash. (Bug#47649)
  • On Solaris, no stack trace was printed to the error log after a crash. (Bug#47391)
  • The first execution of STOP SLAVE UNTIL stopped too early. (Bug#47210)
  • When the mysql client was invoked with the --vertical option, it ignored the --skip-column-names option. (Bug#47147)
  • It was possible for init_available_charsets() not to initialize correctly. (Bug#45058)
  • Comparison with NULL values sometimes did not produce a correct result. (Bug#42760)
  • Crash recovery did not work for InnoDB temporary tables. (Bug#41609)
  • The mysql_upgrade command would create three additional fields to the mysql.proc table (character_set_client, collation_connection, and db_collation), but did not populate the fields with correct values. This would lead to error messages reported during stored procedure execution. (Bug#41569)
  • When compressed MyISAM files were opened, they were always memory mapped, sometimes causing memory-swapping problems. To deal with this, a new system variable, myisam_mmap_size, was added to limit the amount of memory used for memory mapping of MyISAM files. (Bug#37408)
  • A race condition on the privilege hash tables allowed one thread to try to delete elements that had already been deleted by another thread. A consequence was that SET PASSWORD or FLUSH PRIVILEGES could cause a crash. (Bug#35589, Bug#35591)
  • ALTER TABLE with both DROP COLUMN and ADD COLUMN clauses could crash or lock up the server. (Bug#31145)

Google Chrome 2.0.172.31

Google Chrome 2.0.172.31 .Este navegador web tiene una interfaz sencilla y funcional. Para la mayoría de los usuarios el navegador no es lo más importante en su experiencia en la Red: sólo es una herramienta donde visualizar y ejecutar los sitios, páginas web y las aplicaciones que la conforman. Al igual que la página de inicio de nuestro buscador, Google Chrome es rápido y fácil de utilizar. Su objetivo es que los usuarios obtengan la información que buscan y accedan a los sitios web con la mayor rapidez posible.

 

   google-chrome-gratis-gratis-net

  • Busca desde la barra de direcciones
    Escribe en la barra de direcciones y obtén sugerencias para búsquedas y para páginas web.
  • Miniaturas de las páginas más visitadas
    Accede a tus páginas favoritas a gran velocidad desde una pestaña nueva.
  • Navegación privada
    Abre una ventana de incógnito cuando no quieras guardar el historial de navegación.

 

Descargar:Google Chrome 2.0.172.31

Cambios y modificaciones en esta versión Google Chrome 2.0.172.31

Google Chrome’s Stable channel has been updated to version 2.0.172.31 to fix two security issues in WebKit.CVE-2009-1690 Memory corruption
A memory corruption issue exists in WebKit’s handling of recursion in certain DOM event handlers. Visiting a maliciously crafted website may lead to a tab crash or arbitrary code execution in the Google Chrome sandbox. This update addresses the issue through improved memory management.

Severity: High. An attacker might be able to run arbitrary code within the Google Chrome sandbox.

Mitigations:
A victim would need to visit a page under an attacker’s control.
Any code that an attacker might be able to run inside the renderer process would be inside the sandbox. 
CVE-2009-1718 Drag and drop information leak
An issue exists in WebKit’s handling of drag events. This may lead to the disclosure of sensitive information when content is dragged over a maliciously crafted web page. This update addresses the issue through improved handling of drag events.

Severity: Medium. An attacker might be able to read data belonging to another web site, if a user can be convinced to select and drag data on an attacker-controlled site.

AbiWord 2.7.2

AbiWord 2.7.2 es un procesador de texto. La sencillez de su interfaz y los bajos requerimientos técnicos que permiten usarlo en equipos considerados ya obsoletos.

AbiWord tiene filtros de importación/exportación de documentos desde su formato nativo a XML, a RTF, HTML, Microsoft Word, LaTeX y OpenDocument.

abiword-gratis-net

Lamentablemente para los usuarios de Windows 95, 98 y ME  AbiWord 2.6 no está disponible actualmente para su sistema operativo.

 

Desarrollador:abisource.com

Descargar:abiword-setup-2.7.2.exe

Descargar:AbiWord 2.7.2 Linux

Cambios y modificaciones en esta versión AbiWord 2.7.2

•Bug 12102: AbiWord crashes after print previewing (Martin Sevior)
•Add support for uppercase, lowercase, and capitalized character styles [text transforms] (Dominic Lachowicz)
GUI
General
•Bug 7453: Provide a keyboard shortcut for inserting bullets [Ctrl + Shift + L] (sum1)
•Bug 12089: AbiWord aborts when using the font dialog (sum1)
•Make sure selection handles are drawn in the correct color (Marc Maurer)
GTK+
•Bug 8636: Add superscript and subscript options to the font dialog (Urmas, Marc Maurer)
•Bug 12084: New windows cause memory corruption (Hubert Figuiere)
•Bug 12093: AbiWord displays corrupted font lists (Hubert Figuiere)
•Add a default file name when printing to file (Martin Sevior)
•Fix a g_signal_handler warning on exit (Hubert Figuiere)
•Fix the loading of the options dialog (Hubert Figuiere)
Windows
•Bug 6498: Hebrew menu text does not display the last character (Dominic Lachowicz)
•Bug 9961: Find dialog does not work with Russian text (Urmas)
•Bug 11346: Toolbar icons are corrupted at less than 32-bit color (Marc Maurer)
•Bug 12086: Window title has extraneous character appended (Dominic Lachowicz, Urmas)
•Disable the “Change Language when changing keyboard” setting by default (Marc Maurer)
•Fix print preview crashes (Marc Maurer)
Import/Export
OpenDocument
•Bug 11921: Import overline formatting (sum1)
•Import and export text transforms (sum1)
XHTML
•Export text transforms (Dominic Lachowicz)
•Import text transforms (sum1)
•Import margin-top and margin-bottom properties from inline paragraph styles (Urmas)
XSL-FO
•Import and export text transforms (sum1)
Installer
•Install to Program Files\AbiWord instead of Program Files\AbiSuite2 by default (Marc Maurer)
•Use one Windows installer instead of three separate ones (Marc Maurer)
Internationalization
•Update the Russian (ru-RU) translation (Urmas)
Plug-ins
Collaboration
•Add a button to the account dialog for registering AbiCollab.net accounts (Marc Maurer)
•Allow long email addresses and passwords to be entered in the new account dialog on Windows (Marc Maurer)
Grammar
•Update the dictionary-loading code to work with newer versions of link-grammar (Marc Maurer)
Development
General
•Add –enable-clipart and –enable-templates build options (Robert Staudinger)
•Fix a number of compiler warnings (Hubert Figuiere)
•Fix format string errors throughout the code base (Hubert Figuiere)
•Maintain and release 2.7.2 (Marc Maurer)
•Move templates and clipart to abiword/ to get rid of abiword-extras/ (Marc Maurer)
•Remove the non-functional nroff plug-in (Marc Maurer)
•Use g_convert() instead of custom code (Dominic Lachowicz)
Linux
•Replace GList with std::list in some spots (Hubert Figuiere)
•Update the libgoffice requirement for the GOffice plug-in to 0.7.7 and fix the build (Jean Brefort)
Windows •Add the Applix, BabelFish, ClarisWorks, Collaboration, DocBook, Email, FreeTranslation, Google, Grammar, HRText, ISCII, LaTeX, Office OpenXML, OpenDocument, OPML, StarOffice, T602, URLDict, Wikipedia, Windows Graphics, WML, WordPerfect, and XSL-FO plug-ins to the VC++ build (Marc Maurer)
•Enable printing and spelling support with VC++ (Marc Maurer)
•Fix a bunch of warnings in the VC++ build (Marc Maurer)
•Fix a compiler error when cross-building (Dominic Lachowicz)
•Improve the VC++ build system to handle official Windows releases (Marc Maurer, Marc Oude Kotte)
•Make numerous changes to the collaboration plug-in to get it to build with VC++ (Marc Maurer)
•Modify the NSIS install script to handle packaging from VC++ (Marc Maurer)
•Remove template exports to quiet VC++ (Marc Maurer)
•Use pre-built peer libraries for the VC++ build (Fridrich Strba, Marc Maurer)
•Include the MSVC2008 runtime in the installer (Marc Maurer)

FileZilla Portable 3.2.3

FileZilla Portable 3.2.3  es un cliente FTP para Windows, Linux, FreeBSD y MacOS gratis, libre y de código abierto. Soporta FTP, SFTP y FTP sobre SSL.
Las principales características son el Site Manager (Administrador de sitios), Message Log (Registro de mensajes), y Transfer Queue (Cola de transferencia).El administrador de sitios permite a un usuario crear una lista de sitios FTP con sus datos de conexión, como el número de puerto a usar, o si se utiliza inicio de sesión normal o anónima. Para el inicio normal, se guarda el usuario y opcionalmente la contraseña.

filiezilla-gratis.gif

 

Desarrollador:filezilla.sourceforge.net

Descargar:FileZilla Portable 3.2.3

Lista de Cambios FileZilla Portable 3.2.3

New features:

  • made OpenCrystal the default theme on new installations
  • setting kiosk mode to 2 in fzdefaults.xml prevents FileZilla from writing to any settings files. Useful if executed from read-only media.

Bugfixes and minor changes:

  • Fix crashes and memory corruption if resizing columns in queue if message log is positioned as queue tab