ASP.NET

protected void GridView1_PageIndexChanging(object sender, GridViewPageEventArgs e)
   {
       GridView1.PageIndex = e.NewPageIndex;
   }

   protected void GridView1_PageIndexChanged(object sender, EventArgs e)
   {

       GridView1.DataBind();
   }

goldsoft wrote:

but still i see the same records

<input id="chkGenerateRpt" type="checkbox" name="chkGenerateRpt" onclick="javascript:return ReportConfirmation(); ;setTimeout('__doPostBack(\'chkGenerateRpt\',\'\')', 0)" /><label for="chkGenerateRpt">Generate Reports</label>

<input type="checkbox" id="chkClient"  runat="server" value="..."
name="chkClient" onclick="alert('hello');document.forms[0].submit();"
onserverchange="chkServer_CheckedChanged">

protected void chkServer_CheckedChanged(object sender, System.EventArgs e)
{
    Response.Write("<br>CheckChanged at: " + DateTime.UtcNow.ToString());
}

• Did you change your password when you encrypted it: if not the hacker could still be using your original password.
• You should consider locking down your FTP setup, so that you arrange to have FTP open only when you are uploading. This is most likely how they got in. You could also change your firewall so it only accepts incoming FTP requests from internal/known IPs.
• The presence of files on your site indicates that whoever has hacked you *might* have some level of user access to you machine (ftp is more likely, but there are tools to bootstrap yourself an account using known vulnerabilities) : Check for new users (especially with administrative rights) and strap your server down.


• If the hacker has their own login account, they might no longer need the password, their kerberos identity could be enough if authentication is in mixed mode. Check the SQL logs to see who has been in on your system, again strap down who can log in to your SQL server, but they sound clever enough to cover their own tracks. If your SQL server isn't on a different machine, move it. Only allow specific windows accounts to login (say the DB admin's and yours), or none at all (SQL only mode).
• Put some code security in place so that only code signed by yourselves can be actually executed.
• Change your SQL password again: they may already have a new one.