Isn’t this the most worthless result from a vulnerability scan:
PHP Unspecified Vulnerability (Protocol: tcp Port: 80)
DESCRIPTION An unspecified vulnerability has been discovered in PHP with Unknown impact and attack vectors. All versions before 5.2.11, and 5.3.x before 5.3.1 are affected
SOLUTION Upgrade to the latest version of PHP, available at http://www.php.net/downloads.php
Go Nessus.
Sebastian Bergmann, lead developer of the PHPUnit testing framework, has decided to switch PHPUnit from subversion to Git. I wouldn’t normally have a problem with this, especially if he were to follow all of the other mainstream projects that choose to keep backwards-compatibility with Subversion by keeping Subversion and Git in sync. However, he’s chosen to go strictly the route of Git and not bother keeping a subversion repository in sync.
Why do I have such a significant problem with this? I don’t do anything in Git right now. Everything of mine is still in Subversion, and quite frankly, I intend to continue using Subversion for quite some time as it works well for my group and I’m too overwhelmed with learning other technologies to learn yet another source code control system.
So, please Sebastian, at least keep subversion around and sync it with Git. All of us Subversion developers that use your repository to fetch PHPUnit from there (instead of using the PHP un-best practices way of installing through PEAR) would greatly appreciate it.
[root@sheerjira ~]# rpm -i rpmforge-release-0.5.1-1.el5.rf.i386.rpm
package rpmforge-release-0.5.1-1.el5.rf.i386 is already installed
[root@sheerjira ~]# rpm -e rpmforge-release-0.5.1-1.el5.rf.i386.rpm
error: package rpmforge-release-0.5.1-1.el5.rf.i386.rpm is not installed
‘Nuff said.
I cannot believe i’ve never seen the first Star Trek: The Next Generation episode. Then again, it first aired in 1987, which would have made me about 3. I have to say, the later years were so much better!! the camera angles, acting, and music were quite campy in the first episodes. Oh, and Riker is really boy-ish. It’s weird.
As one of the first few languages I learned, PHP has a special place in my heart. I am able to do a lot with the language. But sometimes, I wish that the core development team would actually make it into a full object-oriented language. See more of the story for the exact reason.
Read more…
I’ve been moving the databases at work from one Microsoft SQL 2005 server to another SQL 2005 Server. When the databases grant security to non-domain users, they have a tendency to not be attached / accessible on the new server. What you have to do is reattach / rejoin the orphaned security authorization to the credential that you reestablish on the new SQL Server. This is done with the following pl_Sql command:
sp_change_users_login 'Auto_Fix' sp_change_users_login 'Update_One', 'old_username', 'new_username'
Auto_Fix can only be used if the old_username and the new_username are the same.
The last year or so I have dabbled in C# .Net development, which was quite a bit different from PHP development. The .Net Framework is absolutely huge, the capabilities are endless, and the tools to help me develop faster far outnumber those of PHP. Furthermore, there are many within the community that work like true pragmatic developers (J.P. Boodhoo is one). These developers think about how best to organize your application and help to bring true automation to a project. Further, they work to eliminate conflict from workstation to workstation. In short, I’m talking about organization and management of code for rapid and agile development no matter who is on the team or how those team member’s workstations are setup. When moving back from .Net development to PHP, though, this type of mentality hasn’t quite made it.
For those Eclipse users who are PHP developers, getting the PDT Eclipse modules to install in a non-PDT distribution of Eclipse is extremely painstaking. This is compounded by the fact that x86_64 users don’t get a PDT distrib from http://www.zend.com/pdt/. As a result, we have to fend on our own…
Howdy all,
I made a post below relating to PHP, and the caching engine is not deleting the cache, so the post is showing up with < and > characters as literals, thus showing text boxes and other things that’s supposed to be straight code. Give it about 24 hours, and if it isn’t fixed, I’ll look into what’s causing the problems.
Update (3/28/2008): I thought it was a problem with wpsupercache, but in fact it wasn’t. It was a problem with the Wordpress plugin Google Code Prettify and/or something internal to Wordpress. I say this because my code snippets, which originally had < and > characters inline were rendering the HTML as literal HTML - not what I wanted. But when I figured that I’d change the snippets to use < and > instead, it _still_ got rendered as literal < and > characters. Weird - no? Well, check out the most previous post prior to this, and I’ll (hopefully) update my archives with the syntax used in the wp-syntax plugin.
Recent Comments