Slavok wrote:

Agree with you. It will be implemented in the next version of pun_quote.
What method do you suggest to determine whether client's JavaScript is enabled at server?

Cheers. smile

As Rich mentioned, javascript itself should enable the links being displayed. A display: none in the CSS for the id of the div, (or whichever parent tag they're enclosed in), containing the links and then set to display via javascript. If javascript isn't enabled, they can't ever become visible.

Might one suggest that the bbcode tools, i.e: the smiley bar and editor tool blocks, are only visible when javascript is enabled. They are totally useless without. smile

Plus, it isn't necessary to load all of the quickquote/multiquote information for guests. The page size is being bloated unnecessarily for no reason whatsoever.

153

(25 replies, posted in Programming)

njwoods wrote:

When you filter input never try to worry about what characters to block, only worry about what characters you should let in.  Use functions like preg_match or similar functions to specify rules where if the input is not between 0-9 and a-z or A-Z - strip it out silently or report an error to the user.

To clarify what that means specifically, is that you start off with a blacklist which blocks everything and then you only specifically allow the characters or other info you require.


njwoods wrote:

If you're using php be sure to use mysql_real_escape_string before your database queries (all of them).  That alone should prevent most if not all sql injection attacks.

Not if you're running PostgreSQL it won't. big_smile Use the specific *sql escape function fr your DB if creating your own code from scratch. The likes of PunBB have database layers so that the DB specific query is unnecessary. It uses one common name for all DB types.

154

(11 replies, posted in PunBB 1.2 troubleshooting)

You had made no alterations to the code whatsoever? Post your viewtopic up here, (within code tags). Everything else appears to be functioning fine.

155

(11 replies, posted in PunBB 1.2 troubleshooting)

kierownik wrote:

When people have to login or register to help you, you will proberbly will not get any help.
People do not like to register to help people.

Make your board public availible so we can have a look or have a demo acount so people can have a look.

You've done the same trick as I did the other week. big_smile big_smile

Log in with

user: reiner
password: 650099

156

(11 replies, posted in PunBB 1.2 troubleshooting)

There is no problem that I can see. Everything displays just fine.

157

(19 replies, posted in News)

Best of wishes in your new venture, Anatoly. smile

158

(17 replies, posted in PunBB 1.3 troubleshooting)

I was actually going to write an indepth reply to your post above, but realised I might as well try to plait snuff. Hence this shortened version.

You are perfectly entitled to your opinion. PunBB, however, shoud be sanitising, (which is perfectly relevant, might I add), and validating all input where possible. Simple fact. Crap in, crap out.

That is personally my last post on this subject. I can bang my head against a wall here if I'm feeling the urge, rather than responding further to your posts.

159

(2 replies, posted in General discussion)

If 1.3 still uses a header and footer include, then just creating another index file and just including the header and footer alone in it should give you practically what you want.

160

(2 replies, posted in PunBB 1.2 discussion)

I believe smarty's posted a mod over on Punres awhile ago for adding the feature to 1.2.

161

(2 replies, posted in PunBB 1.3 troubleshooting)

You can alter it via the stylesheet.

162

(17 replies, posted in PunBB 1.3 troubleshooting)

pepak wrote:
SiCo wrote:

It's always possible to miss escaping sql input,

Actually, if developers (in general, not specifically of PunBB) finally started to use prepared statements, the whole problem of SQL injection would go away.

I believe you'll find that statement is incorrect, if I remember correctly. Prepared statements are, (from memory), an extra layer of protection but not a foolproof one. Besides, there is still no excuse for not parsing, sanitising and validating wherever humanly possible. Any other approach is plain old sloppiness where security is concerned, no matter how you phrase it. You cannot make a silk purse out of a sows ear. Period.


pepak wrote:

I see it as a line in the defences, backed up by escaping the sql and the output etc. It should be standard coding practice to check all input is at least within reasonable bounds.

I agree generally, but I do think that there are cases where rigorous validation isn't worth it. E-mail-like logins for various IM services are one such case.

Rigourous validation and sanitisation is *always* worth it. Any other approach is, inevitably, at some point in time, just putting up a big sign asking for problems.

If you wish to take the haphazard approach personally, then by all means do so. A project such as this should have no coding practices such as those inplace, however. Security is paramount.

163

(17 replies, posted in PunBB 1.3 troubleshooting)

Parpalak wrote:

But I have an objection about the 'website' field. Forum can be installed for users of a LAN. Users may write there simply their computer names. A computer name doesn't have a form like '<something>.com' and will fail a validation.

If an internal zone is set up incorrectly, that is not for PunBB to decide. A domain should be in the form of *.*. Only localhost is exempt from that rule.


Btw, in reference to your earlier post, sloppy, (or none, in this case, it seems), input validation is *never* a feature request. It is a bug.

164

(17 replies, posted in PunBB 1.3 troubleshooting)

pepak wrote:

Validating e-mail isn't exactly easy to do.

The old devs managed it perfectly well where 1.2 was concerned, so I see no reason why 1.3 should be any different.


pepak wrote:

With most of these values, I pretty much fail to see their importance. So someone enters a wrong homepage or wrong AIM - where's the harm? It only hurts him, nobody else.

The point is? The input is invalid. Pure and simple. Consequence is irrelevant.

I believe the function to run on the string is now called forum_htmlencode().

166

(17 replies, posted in PunBB 1.3 troubleshooting)

Slavok wrote:

I don't think that it is a bug, but if you want you can create an extension to validate this information. I think, real members of forum are interested in stating the real and correct contact information about themselves in their profiles. Fake users will enter something useless in these fields, and you will notice this.

That is just pure poppycock. The first, most simple rule of security, is to validate all user input, where humanly possible. It should *never* be an extension or afterthought. When that input can be guaranteed to be of a predefined format, there is no excuse whatsoever for not validating it.

Unless you'd prefer that forum admins turn around and tell the scripters and spammers to stop being cocks and behave themselves? I'm sure they'd feel awfully ashamed at being berated and behave in a civilised manner.

Honestly Slavok, that response you posted belies belief.

Check in the 1.3* sections and the wiki. They may already have a version for 1.3. If not, regrading from 1.3 is going to be a feature of FluxBB when they bring 1.4 out. I don't think PunBB have anything which does it.

You're trying to install 1.2* mods on 1.3*? You'll have a fun time getting nowhere with that. Mods and extensions are vastly different things and not cross version compatible.

I doubt anyone could be "desperate" for chatbox or reputation mods, especially less than one hour after your initial post.

Check your logs for errors. Pyschic abilities have never been my strongpoint personally, I must admit.

Edit: However, if you're on 1.2, one does wonder why you're trying to run anything from the admin directory?

170

(12 replies, posted in PunBB 1.2 troubleshooting)

esupergood wrote:

p.s. how can a punbb support manager be unaware of the latest extensions? Sorry if that is a bad question but it seems like you should be on top of latest releases smile

User extensions aren't official code.

171

(5 replies, posted in PunBB 1.3 additions)

esupergood wrote:

what's that matt?

An online style generator for 1.3.

172

(5 replies, posted in PunBB 1.3 additions)

http://spinkbb.jsand.net/punbb/index.php

If you have access to the mysql command, then you should also have the mysqldump command available. There is no more portable and cross-platform a method than MySQL's own utilities.

mysqldump [database_name] > [output_filename]

Just do a db dump via your normal SQL admin utility.

175

(5 replies, posted in PunBB 1.2 troubleshooting)

You mean you only want the code to execute on one specific page? If so, which page?