Search options (Page 8 of 16)

i think thats only for text fields

mmm so...

piece2='date "+%Y-%m-%d"'
piece1='mydb'
filename="${piece1}${piece2}"
cp mydb filename

i am a still a bit confusing with the way the string variables are handled ( noob )

would that do it?

I wouldn't like to make changes in the code because of the updates. I've highly modify the code of a forum that i set up and i keep wondering if i will remember all changes i made when it comes to update.

About you solution... i am dummy, it's the second time i need to do such a change ( the other was allowing html in some specific posts ) and both times the solution was the same and it was in front of my nose without me seeing it, lol.

Elbekko, thank you, you are becoming my official troubleshooter

I will check anyway if i can manualy insert more than 64kb of text in the post body field.

Try it.
You mean you want to evaluate the echo execution?

You can assign whatever you want to echo into a variable through a function call like this

if($foo = function_call_to_evaluate($foo2)){
     echo $foo;
}

nice integration

I agree with bot of those. This discussion was not refering to punbb in particular. That's why i said i don't think this new hashing is useless.
The blog entry just made me think about all this existencial security doubts i had. Thank you three for the answers

Comment #6 focus what i just posted here and comment #7 gives the explanation there is to give.

Mmmm there is some improvement in security, an attacker would have to build a rainbow-table for each salt. So it would have to focus on one ( or more ) specific user rather then trying to find colisions in whatever data he/she hijacked.

We all should keep in mind that this wont stop a brute force attack if the attacker intends so ( and can perform it of course )

That's actually the article i was reading when my doubts came up. I interrupted then the reading to, once and for all, understand the salt thing.

Now i red the whole article anyway and got to understand how the punbb password hashing system works. But i am still wondering about my biggest doubt:

Every single article i read about this ( including that blog entry ) points the big danger: database leaking.
If password leaking is the "attack"  one should be protected of, in case it happens, i can't see how storing a hash in the very same database improves security.

I take the chance to drop another related question:
The hashed ( with salt ) passwords in a *nix system are stored in a passwd file. Where is the location where the salt is typicaly kept?

I have set up my script and fetch about 100 posts a day running it once through a crontab.
This script, as it is posts only in a category, but you can simply solve that.

Put an array into $newsforum_id rather than an intiger.
use a two dimension array in $feed_array being the first coordinate the forum_id of the feed.

wrap the code into one more foreach cicle to loop through the forums and replace $feed_array by $feed_array[$forum_id]

If all this sounds tricky or complicated i suggest you run multiple instances of ths script with different settings.

I could go into the code and change it a bit but i am currently out of time to test it.
If you go on and hack the code feel free to drop questions