Jump to content

mark1million

Moderators
  • Posts

    2283
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by mark1million

  1. Its in the core>common>PIREPData.class,php

    Its about line 756 in my file, it looks like this, thats not the whole section.

    if (Config::Get('EMAIL_SEND_PIREP') === true) {
    
               # Send an email to the admin that a PIREP was submitted
               $sub = "A PIREP has been submitted by {$pilotcode} ({$pirepdata['depicao']} - {$pirepdata['arricao']})";
               $message = "A PIREP has been submitted by {$pilotcode} "
                   ."({$pilotinfo->firstname} {$pilotinfo->lastname})\n\n"
    
    

  2. The url for the pilots to download the config file should be, http://eravirtualairways.com/en/action.php/acars/xacarsconfig

    I have my link in the profile_main.tpl

    <a href="<?php echo actionurl('/acars/xacarsconfig');?>">X-ACARS Config File</a>

  3. Maybe a "VA Licence" would be more suitable, i have to agree with Tom about forcing users to have their own personal account.

    Vroute used this same kind of thing where you can call the parameters off their api and you get a return xml string of route data and such, the VA only had to pay for the current araic and this was all a backend function invisible to the user except from a logo at the bottom with "route provided by vroute".

  4. Hi

    i got to the install process and i went to create the database info adn clicked next step to create tables and got

    Fatal error: Uncaught <blockquote><font face=arial size=2 color=000099><b>Last Error --</b> [<font color=000000><b>Access denied for user 'joinbbva_phpvms'@'localhost' to database 'joinbbva_phpvms' (1044)</b></font>]<br />[<font color=000000></font>]</font><p> </blockquote><hr noshade color=dddddd size=1> thrown in /home/joinbbva/public_html/core/classes/ezdb/ezdb_mysql.class.php on line 140

    How can i fix this

    Your password is not correct for the user specified. Check the password or username or create a new password and try again.

  5. Sava, a good addition to this would be to approve the request and once approved they get added to a defined group ie leave, i have different groups and would need to add them to the group once approved.

    Hope you understand what im trying to say :)

  6. The file you need to modify is Core>Common>PilotData.class.php

    In my file its around line 513 but yours may be different,

    /**
    * Completely delete a pilot
    *
    * @param int $pilotid Pilot ID
    * @return mixed This is the return value description
    *
    */
    public static function deletePilot($pilotid) {
    
    $sql = array();
    unset(self::$pilot_data[$pilotid]);
    
    $tables = array(
    'acarsdata', 'bids', 'pirepcomments', 'pireps',
    'fieldvalues', 'groupmembers', 'pilots'
    );
    
    foreach ($tables as $table) {
    $sql = 'DELETE FROM '.TABLE_PREFIX.$table.' WHERE `pilotid`='.$pilotid;
    $res = DB::query($sql);
    }
    
    return true;
    }
    
    

    Thats the code so just take the pireps and pirepcomments out of the array.

    NOT TESTED please use at your peril.

  7. Just add a new field to the database this will not get undone on any update then just modify the stock file and create a back up of it which sits on the server, on any update all you have to do is then compare the differences from your modified backed up file against the new one.

  8. By looking at that list your skins folder is untouched, download a complete copy of your site to your desktop then delete everything from your home folder on the server, thats providing you have phpvms only in there.

    Download a new version of phpvms and upload to your server.

    Now go to your desktop where your old site is and check all the files in your active skin folder that they are clean, once satisfied upload them to your site, check also the local.config.php file and when your in there change your database password and save, then upload that to your core and you should be back to normal.

    If you have modified the other scripts you will need to re modify them again to your needs but basically thats the easiest thing to do.

  9. Well, if you have any files that you need that were edited after that date then that was a bit silly. Anyway, why Sept 10th? All of mine were later on, find out when your site was compromised, not when everyone else's was.

    We all know this exploit has been about since 2009 so dating your files is useless. You need to examine everything unless you know exactly.

    Most of the default phpvms files are 2011 depending what version your running so you can easily check that way.

  10. Our site was compromised, so I read the forum and looked for all the suspicious files. Found one, deleted it. Problem persisted. So I did what most people suggested- I went through every file and deleted everything dated after Sept 10. Now the entire website is down. WTF?

    If you have a backup i could have a look at the files in there for you, you know what should be there not not really but also if your on the same server check other directories.

  11. Sadly, when there is a vulnurability, you find out when it's too late. As I mentioned earlier a checksum would at least give us early indication that some files have been tampered with. Maybe it would be possible to automate site backups/restores based on that information.

    By the way, before this happened, I got bots trying to get through the login system at phpVMS and phpBB for months. They finally managed to break into phpBB a few months ago. Afterwards I was able to reduce bot attcks by blocking a LOT of ip ranges, and reduce it further by implementing a "human check" on the register page, which by the way I think should be standard since some of their attempts have managed to overcome captcha.

    I found adding an extra page which requires a tick box to be checked before registration completely eliminated spam or bot registrations.to date so far.

×
×
  • Create New...