Stories
Slash Boxes
Comments

Slash Open Source Project

Slash: Temporary Workaround For CVS Vulnerability

posted by jamiemccarthy on 03:05 PM December 16th, 2004   Printer-friendly   Email story
We've gotten a couple of questions about whether there will be a workaround for site admins who don't want to upgrade into x_2_5_* CVS but who don't want to just wait until the patch comes out next week.

For security reasons, we don't want to reveal too much of what's going on until everyone has had a chance to upgrade, but we will say that you can temporarily make your site immune to the vulnerability by removing the symlinks to search.pl and submit.pl.

Slash: Security Advisory for CVS Slash

posted by jamiemccarthy on 10:42 AM December 15th, 2004   Printer-friendly   Email story
There has been a security issue in CVS Slash code for the last couple of years which was found recently. This is something that site administrators should be concerned about.

We are urging all sites which are using a version of the code from CVS to upgrade now to the CVS tag R_2_5_0_41. Sites which are using the 2.2.6 tarball, the latest official release, do not need to upgrade (the issue is not present there).

Slash: Brace For Impact

posted by jamiemccarthy on 07:40 AM June 11th, 2004   Printer-friendly   Email story
Those of you following CVS closely: don't do incautious updates in the near future. We're going to be committing a large chunk of code all at once, very soon now, and we guarantee it will break your site if you install it. Bear with us while we get everything up to speed. In a couple of weeks everything will be humming along smoothly.

(We're overhauling the section and topic system, replacing it with something more flexible.)

New R_ tag: 151

posted by jamiemccarthy on 10:43 AM May 12th, 2004   Printer-friendly   Email story
Last night we sprinkled a trace amount of holy penguin pee on the CVS tag T_2_3_0_151 and pronounced it to also be our latest R_ tag, R_2_3_0_151. This is the latest R_ tag since _113, which was many weeks ago. (If you missed the memo, "T" is for testing and "R" is for releases. We still haven't dubbed anything "Slash 2.3.0" yet, but that's mostly because we're lazy.)

We feel pretty good about the stability of _151, it's been running on Slashdot for a couple of weeks and there are no real problems.

The big change, committed shortly after _151, is the switch from users.pl to login.pl for authentication and related operations. That seems to be working but it hasn't been tested enough to merit an R_ yet. In fact, this may be the last R_ tag that we do for a while, since there are big changes that will be committed in the weeks to come which will put the damper on R'ing.

Here's the CVS tree if you want to browse, and here are the instructions to download:


$ cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/  slashcode login
CVS password: (hit return, there is no password)
$ cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/  slashcode co slash
(much activity)
$ cd slash
$ cvs update -r R_2_3_0_151 -dP

Ask SlashCode: Making Slash Install Friendly?

posted by Cliff on 09:50 PM March 23rd, 2004   Printer-friendly   Email story
Recently I was asked by a heavily trafficed website to investigate migrating their site to Slash. After downloading the latest codebase I'm reliving a lot of the installation frustrations experienced when I messed around with Slash over a year ago. I've installed lots of portals before like PhpBB, Nuke, MX-System etc. All of those installs were pain free. I'm writing to request that you guys simply the install process. How about some straight forward docs? I would suggest a list of required packages and then simple instructions how to get Slash working with Apache etc that comes with most distros.
Today's News | December 18 | December 16  >