vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   News and Announcements (https://vborg.vbsupport.ru/forumdisplay.php?f=2)
-   -   Important: It is all about trust (https://vborg.vbsupport.ru/showthread.php?t=115640)

peterska2 05-16-2006 11:09 PM

Quote:

Originally Posted by JD45
Obviously the coder(s) put that line of code in for a reason. To generate an 'installed' click instead of counting on the user to manually do it.

Why not consider this:

Take away the ability for users to manually hit the install/uninstall button. Have every hack that is created contain two lines of additional code. One to add to the install count when the hack is installed by the user and another to uninstall, when it is removed by the user.

Obviously this would have to be disclosed somewhere on VB.org like in a sticky or the FAQ so everyone is aware of it.

This would in fact IMO, help the coders by giving them a truer account of how many people in fact installed their hack as well as helping the installer with receiving the 'hack updated' emails.

Could be a win/win situation if handled properly. :cool:

Why? Because a number of users do not wish to have the install button forced upon them. I always click install if I am using something, but as I have previously mentioned, I don't just install on my site and yet all the installations go onto my account here.

Also, the method does not always work. There are certain requirements that must be achieved in order for it do so. Therefore, it would be just as inaccurate, if not worse, than the install button we currently have.

JD45 05-16-2006 11:25 PM

Quote:

Originally Posted by peterska2
Why? Because a number of users do not wish to have the install button forced upon them. I always click install if I am using something, but as I have previously mentioned, I don't just install on my site and yet all the installations go onto my account here.

Also, the method does not always work. There are certain requirements that must be achieved in order for it do so. Therefore, it would be just as inaccurate, if not worse, than the install button we currently have.

  • It would no longer be forced..
  • If you always click install, then you wouldn't need to anymore
  • What requirements???
  • If the script worked, it would be HIGHLY accurate

If you created something, wouldn't you want an accurate measure of how many people were using it or how popular it was?

Paul M 05-16-2006 11:36 PM

Quote:

Originally Posted by amykhar
Paul, I disagree on the gloom and doom thing.

You are, of course, free to disagree - but I'm still right :p

It's all old news now, so I'll just agree to disagree with you. :)

GaryP 05-17-2006 12:45 AM

I just wanted to say that I've uninstalled every hack on my site and won't be installing anything else until it is known that no hack will have any code in that may harm my site, transmit any form of information about me, or do anything other than the function that I install it to achieve.

I might be relatively new here, but I still support the people who make the hacks by clicking install.

Darat 05-17-2006 08:25 AM

Quote:

Originally Posted by GaryP
I just wanted to say that I've uninstalled every hack on my site and won't be installing anything else until it is known that no hack will have any code in that may harm my site, transmit any form of information about me, or do anything other than the function that I install it to achieve.

I might be relatively new here, but I still support the people who make the hacks by clicking install.

Don't forget just because there is a rule against something doesn't mean that something won't still happen! I don't think this site or any other site will ever be able to give you an absolute assurance that a hack won't have some code that may harm your site and/or Members.

If you are very concerned I would suggest you PM the Members whose hacks you used to have installed and ask them directly if they have any hidden functionality.

But don't forget one of the very good things about hacks from here is that they are in a way "open source" in the sense that anyone can review the hack's code. And it's obvious many of the coders take an active interest in the code of other coders so I think it's quite unlikely that any hack that has malicious hidden functionality will go unspotted for any length of time.

Boofo 05-17-2006 08:31 AM

Quote:

Originally Posted by GaryP
I just wanted to say that I've uninstalled every hack on my site and won't be installing anything else until it is known that no hack will have any code in that may harm my site, transmit any form of information about me, or do anything other than the function that I install it to achieve.

I might be relatively new here, but I still support the people who make the hacks by clicking install.

The few I have done are safe as well as most others on here now. If you have any concerns or questions regarding the hacks you would like to install, please feel free to PM me with your concerns and I will check to make sure there is nothing there that will affect what you want from the hack. ;)

GaryP 05-17-2006 08:53 AM

That will be very helpful. Thank you for offering to do that.

I will send you a PM with a list on shortly.

I'm sure that you can understand my concerns.

Maybe not saying what hacks are affected by this problem is a mistake, but even if there are reasons for not saying so at present, perhaps an email to people who have installed those hacks would just be common courtesy.

lebanon 05-17-2006 12:32 PM

Quote:

Originally Posted by sabret00the
Cause (going off of what Princton said) this is way bigger than we think, however cross referencing that information with Marco's post, i'm inclined to think that people are actually requesting usage statistics, i also wouldn't rule out the vBsoccer hack.

Hi, i noticed the two comments on my vbsoccer, and due to the thread title, i just want to clear that i am not monitoring the stats neither my stats would be harmfull anyway, but rather all i wanted was not to disclose my feeds.
Now to be honest, i dont even know why i have shared this , all i get now is either trust questioning or suspecion of my intentions here and there.
My suggestion regards my vbsoccer is a moderator to delete the whole thread since i cannot do it myself, regards

SaN-DeeP 05-17-2006 06:16 PM

Quote:

The reason for this thread is that, to our own shame, we received recently reports that there are coders who do incorporate hidden functionalities in their modifications. Lucky the type of hidden functions could be considered as relative harmless, but we will nevertheless not tolerate this. I would like to emphasize that this did not sent any security or privacy related information, nor did it in anyway brake the security of your site
never noticed this with hacks I have been using on my boards or tested, but thanks for clarifications..

akanevsky 05-18-2006 01:54 AM

Quote:

Originally Posted by SaN-DeeP
never noticed this with hacks I have been using on my boards or tested, but thanks for clarifications..

haven't noticed that either, maybe cause I'm not using many of 3rd party hacks lately.. but thanks for heads up anyway.

AWS 05-18-2006 03:16 AM

When I read the first post my first thought was someone put a backdoor in a hack. The post reads like a virus warning. The first post does indeed scream "doom and gloom"
Having said that no person should install any hack without first looking through the code. You want to do this to make sure the code is secure and doesn't contain any backdoors. In all honesty you shouldn't be installing hacks if you have no knowledge of php. While I have trust in the authors of the hacks here it would be very easy for one of them to put in a backdoor that would give them control of your forum or your whole server.

Chroder 05-18-2006 03:21 AM

Quote:

Originally Posted by AWS
While I have trust in the authors of the hacks here it would be very easy for one of them to put in a backdoor that would give them control of your forum or your whole server.

This is true. I think maybe we should create some sort of "verified" system. When we upload attachments, they are marked as unverified (but still downloadable). Then maybe have a team that goes around and checks newly uploaded or updated attachments for unsafe code. Once it's passed the check, display a "verified" badge on the attachment.

Evil X 05-18-2006 03:41 AM

why was my post deleted? was it too real for you

IceBurn3000 05-18-2006 03:42 AM

Quote:

Originally Posted by Chroder
This is true. I think maybe we should create some sort of "verified" system. When we upload attachments, they are marked as unverified (but still downloadable). Then maybe have a team that goes around and checks newly uploaded or updated attachments for unsafe code. Once it's passed the check, display a "verified" badge on the attachment.

That sounds like an excellent idea!

akanevsky 05-18-2006 09:27 AM

Quote:

Originally Posted by Chroder
This is true. I think maybe we should create some sort of "verified" system. When we upload attachments, they are marked as unverified (but still downloadable). Then maybe have a team that goes around and checks newly uploaded or updated attachments for unsafe code. Once it's passed the check, display a "verified" badge on the attachment.

Ironically, this is the idea I put forth quite some time ago... Unfortunately, it was not accepted. :( Maybe now is the time to rethink.

Marco van Herwaarden 05-18-2006 09:35 AM

It is a very good idea.

But it also has been suggested (members and within Staff) many times before, and it was in some way even implemented once (not as far as really putting verified or not).

It always failed because there are no volunteers that want to go through all the submitted code (and every time an update is done). This is not only a huge task, but what if you verify a source, and later to find out you missed some nasty code somewhere, are you/we liable?

There are many aspects to this, but maybe it is the right time now to give it another try.

Smiry Kin's 05-19-2006 04:20 PM

Quote:

Originally Posted by MarcoH64
At this time Staff has not decided yet if we will name the Hacks/Authors involved in public. Like mentioned before the found issues don't cause any real harm to the users, if it would have harmed users, we would already have disclosed it probably.

Coders are always free to inform the users in their hack threads, but then it wouldn't be hidden functionality anymore ;)

i think we have a right to know.. for our own security..

noppid 05-19-2006 04:46 PM

Quote:

Originally Posted by amykhar
Paul, I disagree on the gloom and doom thing. The user that ticked me off the most in this whole issue is just the type to use that 'harmless' little link to do some more nefarious things. The policy had to be broad enough to stop these kinds of things in their tracks.

I still think this was handled very politely by staff. No fingers were pointed, no names were named. The new rule was spelled out and time was given to comply.

So is that to say if there is a bug in the vBulletin software the public announcement should be, there is a bug or backdoor in the software. We are not going to say which verision, but don't worry, we are counting on hackers to be good?

Not agreeing with Paul on this one is absurd. The hacks in question should have been used to mass notifiy the hack users. That cloak and dagger announcement was completely irresponsible. That's why it's imperitive to click install. The staff should be using these resources. This could have been handled much better with tools that already exist.

Ohiosweetheart 05-19-2006 05:06 PM

Quote:

Originally Posted by Chroder
This is true. I think maybe we should create some sort of "verified" system. When we upload attachments, they are marked as unverified (but still downloadable). Then maybe have a team that goes around and checks newly uploaded or updated attachments for unsafe code. Once it's passed the check, display a "verified" badge on the attachment.

that's what they do at phpbb.com. They, of course, also have the hacks database. Sad to say they are way ahead of vB.

Quote:

Originally Posted by Psionic Vision
Ironically, this is the idea I put forth quite some time ago... Unfortunately, it was not accepted. :( Maybe now is the time to rethink.

if you suggested this and it was denied, then they need to look again. As I said, phpbb.com has had this system implemented for quite some time now, as well as a hack database. Being a free software, it's a shame that they are so far ahead of vB in that regard.

amykhar 05-19-2006 05:27 PM

Quote:

Originally Posted by noppid
So is that to say if there is a bug in the vBulletin software the public announcement should be, there is a bug or backdoor in the software. We are not going to say which verision, but don't worry, we are counting on hackers to be good?

Not agreeing with Paul on this one is absurd. The hacks in question should have been used to mass notifiy the hack users. That cloak and dagger announcement was completely irresponsible. That's why it's imperitive to click install. The staff should be using these resources. This could have been handled much better with tools that already exist.

Noppid, there is a procedure in place to deal with security problems in a mod. So, the existing system would be used in that case.

This was a case of some mod authors using code that is in poor taste but was not technically against the rules. The rules have now been updated and I'm sure the mods will follow through and update users and remove the offending code after the deadline.

akanevsky 05-19-2006 05:42 PM

Quote:

Originally Posted by Smiry Kin's
i think we have a right to know.. for our own security..

I totally agree.

Evil X 05-19-2006 10:35 PM

will you post a list of all the infected hacks? I never hit install (mybad) so im gonna need a list

kall 05-19-2006 10:41 PM

IMO, if you lack the respect to Install, you lack the deservingness to be given a list.

But thats just MO.

Paul M 05-19-2006 10:59 PM

I very much doubt a list will be given to anyone - and I would imagine that most of the mods being discussed were updated to reflect the new policy anyway.

Evil X 05-19-2006 11:00 PM

Quote:

Originally Posted by kall
IMO, if you lack the respect to Install, you lack the deservingness to be given a list.

But thats just MO.


I just recently learned of the install button :confused:

kall 05-19-2006 11:43 PM

My apologies. You said 'I never hit Install'.

That means .. well, never. :)

Salazar 05-21-2006 09:29 AM

Wow, this sucks donkeycocks! :confused:

Please hire someone who looks through the code of released hacks.

:tired:

kall 05-21-2006 06:05 PM

*edit*

Whoops, wrong thread. :o

amykhar 05-21-2006 06:45 PM

Uh, GamePusha, let's go through some logic here :D
1. You never use the install button.
2. The affected code clicked the install button without the user's permission.
3. In your usercp, there is a list of all the mods you have clicked the install button for.

So, logically if there are any mods showing up in that list for you, they were ones that used the code. Click uninstall on them if you are really cheesed off. Problem solved ;)

Xenon 05-21-2006 07:02 PM

Quote:

Originally Posted by Salazar
Please hire someone who looks through the code of released hacks.

well, we are currently hiring a lot of new staff members :)

FASherman 05-22-2006 12:04 AM

What the bloody hell is going on around here?

1. Why would any programmer give a damned about getting credit for the install? Two reasons come to mind. The first is ego and there is no accounting for that. The second is the ridiculous method used to choose Hack of the Month nominees. Get rid of that. Nominate hacks based on merit, not clicks. Oh yeah, and subject every nominee to a code review. Kind of like the way NASCAR does vehicle inspections.

2. I'm sick of the way VB.Org either is or isn't independent of Jelsoft, depending on what they need at the moment. Pick one. Either admit to being a momma's boy or cut the freaking apron strings, but don't play it both ways.

3. Coders are the life's blood of this place. Every user needs to appreciate the hell out of them. They develop code because THEY need it and happen, out of the kindness of their hearts, to make it available to us too. Bee damned greatful. When you have a problem, make an effort to fix it yourself, if you can and post the fix - if you are able. If not, don't PM them. Post in the release thread so that the 100 other people that have the same problem can get the fix. AND BE PATIENT. None of them are full time professional VB developers and celebate PHP monks. They have lives, jobs and families that need the occasional care and feeding.

4. Somebody better get a handle on this site pronto. The snail pace of development of VB and the inability to deliver the years-ago promised vbCMS isn't why VB is the best damned message board for the money. VB.Org and the ability to customize my site to what I need is the real reason. But I see that reason slipping away. Not just this thread but several others show this place in near shambles. The Bush administration is run better with less controversy. This is a site that CANNOT exist without coders. When you run them off hiding behind rules and make mountains out off molehills, then YOU are doing something wrong, rules be damned.

I'll get off my soapbox now. Talk among yourselves.

Ramsesx 05-22-2006 12:59 AM

Quote:

Originally Posted by FASherman
What the bloody hell is going on around here?

1. Why would any programmer give a damned about getting credit for the install? Two reasons come to mind. The first is ego and there is no accounting for that. The second is the ridiculous method used to choose Hack of the Month nominees. Get rid of that. Nominate hacks based on merit, not clicks. Oh yeah, and subject every nominee to a code review. Kind of like the way NASCAR does vehicle inspections.

2. I'm sick of the way VB.Org either is or isn't independent of Jelsoft, depending on what they need at the moment. Pick one. Either admit to being a momma's boy or cut the freaking apron strings, but don't play it both ways.

3. Coders are the life's blood of this place. Every user needs to appreciate the hell out of them. They develop code because THEY need it and happen, out of the kindness of their hearts, to make it available to us too. Bee damned greatful. When you have a problem, make an effort to fix it yourself, if you can and post the fix - if you are able. If not, don't PM them. Post in the release thread so that the 100 other people that have the same problem can get the fix. AND BE PATIENT. None of them are full time professional VB developers and celebate PHP monks. They have lives, jobs and families that need the occasional care and feeding.

4. Somebody better get a handle on this site pronto. The snail pace of development of VB and the inability to deliver the years-ago promised vbCMS isn't why VB is the best damned message board for the money. VB.Org and the ability to customize my site to what I need is the real reason. But I see that reason slipping away. Not just this thread but several others show this place in near shambles. The Bush administration is run better with less controversy. This is a site that CANNOT exist without coders. When you run them off hiding behind rules and make mountains out off molehills, then YOU are doing something wrong, rules be damned.

I'll get off my soapbox now. Talk among yourselves.

I fully agree to that. To point 1 maybe it would be a good idea to make it if somebody is downloading a hack it will be counted automatically as a install.
Also give every coder the title "super master of the universe coder" :)

Shaliza 05-22-2006 01:57 AM

Quote:

Originally Posted by Paul M
Nope, I think it's about the code that tries to call the vb.org "install" link when a product is first installed.

What if someone didn't click "install" because they simply forgot to & not because they were trying to be slick or something?

Quote:

Originally Posted by Mark.B
This is, as you say, about trust, therefore the list of known affected hacks MUST be disclosed, without question.

Absolutely. I bet some people are holding off installing hacks until they know.

I guess the thing I don't understand is why some coders didn't mention that they did this in the readme files? Doesn't the person installing the hack have the right to know what exactly they're uploading onto their site? Why be sneaky about it if it's just "nothing"?

I didn't know about this "install" issue until I read this post. I haven't installed any hacks yet & it looks like I won't be until this list is finally let out in the open.

Quote:

Originally Posted by Chroder
This is true. I think maybe we should create some sort of "verified" system. When we upload attachments, they are marked as unverified (but still downloadable). Then maybe have a team that goes around and checks newly uploaded or updated attachments for unsafe code. Once it's passed the check, display a "verified" badge on the attachment.

That sounds like a fantastic idea.

I also agree with some of what FASherman.

libertate 05-22-2006 02:04 AM

VBulletin.org is Jelsoft.

JohnBee 05-22-2006 02:11 AM

If vb.org doesn't release the hack names to protect the users who failed to press [install] then you are not doing your job. I'm not sure it was said officially but if my board is compromised because some debilated coder thought he had the right to slip some backdoor code past my security then watch out.

Some people who come here are not simple Joe Blows with a forum full of jibber jabbers some people actually have serious data to protect. If you are telling me that I have no right to know what code was compromised then I will take the initiative to show vb.org how serious things can get.

simple said, don't mess with peoples companies and money by playing the blame game. There is no way some coders integrity will come before the information on my site.

I will contact the individual who posted this thread the fuse short and my associates will not mess around with this situation at all.

Shaliza 05-22-2006 02:13 AM

Well said.

FASherman 05-22-2006 02:18 AM

Quote:

Originally Posted by JohnBee
If vb.org doesn't release the hack names to protect the users who failed to press [install] then you are not doing your job. I'm not sure it was said officially but if my board is compromised because some debilated coder thought he had the right to slip some backdoor code past my security then watch out.

Some people who come here are not simple Joe Blows with a forum full of jibber jabbers some people actually have serious data to protect. If you are telling me that I have no right to know what code was compromised then I will take the initiative to show vb.org how serious things can get.

simple said, don't mess with peoples companies and money by playing the blame game. There is no way some coders integrity will come before the information on my site.

I will contact the individual who posted this thread the fuse short and my associates will not mess around with this situation at all.

Can you say "class action"?

The IBM pSeries Users Groups forums run vBulletin with some modifications from this site. Be ready for an excrement storm when I inform their sysadmin that they have potential backdoors but have no right to know.

Code Monkey 05-22-2006 02:31 AM

Way OTT

Boofo 05-22-2006 02:32 AM

Exactly! ;)

Paul M 05-22-2006 02:44 AM

There are/were no "backdoors", perhaps you should re-read the original message.


All times are GMT. The time now is 02:41 AM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01703 seconds
  • Memory Usage 1,869KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (24)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (4)pagenav_pagelink
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (40)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete