Security Vulnerabilities
- Vuln: Pligg CMS 'status' Parameter SQL Injection Vulnerability December 29, 2012Pligg CMS 'status' Parameter SQL Injection Vulnerability […]
- Vuln: Joomla! Multiple Information Disclosure Vulnerabilities February 3, 2012Joomla! Multiple Information Disclosure Vulnerabilities […]
- Vuln: QEMU KVM CVE-2012-0029 Local Privilege Escalation Vulnerability February 3, 2012QEMU KVM CVE-2012-0029 Local Privilege Escalation Vulnerability […]
- Vuln: Mozilla Firefox/SeaMonkey/Thunderbird XPConnect Security Check Cross Domain Scripting Vulnerability February 3, 2012Mozilla Firefox/SeaMonkey/Thunderbird XPConnect Security Check Cross Domain Scripting Vulnerability […]
- Bugtraq: [ MDVSA-2012:013 ] mozilla[ MDVSA-2012:013 ] mozilla […]
- Bugtraq: ESA-2012-010: EMC Documentum xPlore information disclosure vulnerabilityESA-2012-010: EMC Documentum xPlore information disclosure vulnerability […]
- Bugtraq: RFC 6528 on Defending against Sequence Number AttacksRFC 6528 on Defending against Sequence Number Attacks […]
- Bugtraq: [SECURITY] [DSA 2403-1] php5 security update[SECURITY] [DSA 2403-1] php5 security update […]
- More rss feeds from SecurityFocusNews, Infocus, Columns, Vulnerabilities, Bugtraq ... […]
Full Error: Warning: #1264 Out of range value adjusted for column ‘id’ at row 1
We have a database that was used to store some valuable data. The Id column was set to auto increment when a new record was inserted. After about 127 records we started to get the above error message. come to find out we designed the column to use tinyint instead of INT. TinyINT has a max value of 127 , while the record will insert into the table. The id value remained at 127 for all records after. This could have been a huge problem with a larger and high volume application. We ignored the error for about 30 days as it was a warning and not a true error.
Despite what This blog says to issue the following SET GLOBAL SQL_MODE=”; . I would recommend exploring all options before changing the value of the sql mode.
Please check the following resource links to help you make a decision
Numeric Types
MySQL Modes
Nov 11
11
Vi: Found a swap file by the name
If you encounter the message
(1) Another program may be editing the same file.
If this is the case, be careful not to end up with two
different instances of the same file when making changes.
Quit, or continue with caution.
(2) An edit session for this file crashed.
If this is the case, use “:recover” or “vim -r file name”
This means the terminal crashed while you were editing the file. This can also mean someone else is modifying the file.
You can remove the message by deleting the swap file. You will notice a file name in the same directory ending with .swp
While OKB fully supports the Open source community. We enjoyed our time testing out a new Office application called LibreOffoce . This project is backed by The Document Foundation . We found the application to be comparable with Microsoft Office suit 2000 up to version 2010. You can save in docx, xlsx, doc and xls. If you travel without the laptop upload the odp file to Google Docs.
This is a cost effective solution for any user that needs a office suit. Please donate what you can to support this application. They are not asking for the 300. you pay M$ .
Fully supported by OpenKB. Thank you Document Foundation cheers
Available for Mac OS, Windows and Linux
Full error: [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
Server: Windows 2k8 64bit
SQL Server : SQL 2k8 R2
Summary: This is occurring because you are trying to connect to a 64bit system. Notice that PHP runs in 32bit mode so you will need to set a 32bit DSN
run the following command to setup a 32bit DSN
C:\Windows\SysWOW64\odbcad32.exe
Nov 11
6
Crond: enable logging
Depending on your distro , you will need to locate the syslog file. This file is normally found under /etc/syslog.conf
open this file and uncomment the line starting with cron.*
Restart syslog and cron
/etc/init.d/syslog or sysklogd restart
/etc/init.d/crond restart
The logs are normally stored under /var/log/cron