http://arduino.cc/blog/2011/10/04/arduino-1-0/
- various changes related to this port:
* adjust sketch extensions from .pde to .ino
* deal better with different arduino variants
* adjust template to get it compiling/linking again
tested by various
* A permission escalation vulnerability in Asterisk Manager Interface. This
would potentially allow remote authenticated users the ability to execute
commands on the system shell with the privileges of the user running the
Asterisk application.
* A heap overflow vulnerability in the Skinny Channel driver. The keypad
button message event failed to check the length of a fixed length buffer
before appending a received digit to the end of that buffer. A remote
authenticated user could send sufficient keypad button message events that
the buffer would be overrun.
* A remote crash vulnerability in the SIP channel driver when processing UPDATE
requests. If a SIP UPDATE request was received indicating a connected line
update after a channel was terminated but before the final destruction of the
associated SIP dialog, Asterisk would attempt a connected line update on a
non-existing channel, causing a crash.
* Fixed assertion failure if Chunked encoding along with
Content-Length is used.
* Fixed clang and gcc-4.7 warning and errors.
* Fixed the bug that aria2 cannot read line longer than 4096 bytes
from the file specified by --input-file option.
While here USE_GROFF is not needed.
OK rpointel@ (maintainer), aja@
- enable thread model posix; bump estdc++ major
- fix manpages: install cpp.1 and gcov.1 with an 'e' prefix, and install
another copy of gcc.1 as eg++.1 instead of an effectively empty page.
feedback and ok kurt@
DBIx::Class::TimeStamp automatically sets and updates time based columns
in a table. The module effectively emulates triggers to get consistent
behavior across databases that either implement them poorly or not at
all.
DBICx::TestDatabase creates a temporary SQLite database, deploys your
DBIC schema, and then connects to it. This lets you easily test your
schema. Since you have a fresh database for every test, you don't have
to worry about cleaning up after your tests, ordering of tests affecting
failure, etc.
