C#

SELECT * FROM MyTable WHERE StreetAddress = 'Baker's Wood'

SELECT * FROM MyTable WHERE StreetAddress = 'x';DROP TABLE MyTable;--'

SELECT * FROM MyTable WHERE StreetAddress = 'x';

DROP TABLE MyTable;

--'

Eddy Vluggen wrote:

When you have a button on a WinForm, you can inspect its properties. So, if I see a disabled button, I'll simply toggle the "enabled" property to gain access. If there's no button visible, I'll look at the form and check if there's an invisible button as a child. That means hiding/disabling buttons is not secure.

Eddy Vluggen wrote:

I dislike the idea of asking the user for a password in WinForms; if need be, all assemblies can be decompiled, adapted, and recompiled. For ASP that's less of an issue - but then I'd assume an AD that does the authentication, which means you don't need to provide yet another login.

BillWoodruff wrote:

If you believe the OP is a "beginner," do you think they will understand this ?

BillWoodruff wrote:

If the app stores no passwords, how can any form of hacking the app discover them ...

BillWoodruff wrote:

for that matter, lots of Winform apps consume the plain-text user-entered password, hash it, salt it, and use that to query the DB for a check.

Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.

Eddy Vluggen wrote:

When you have a button on a WinForm, you can inspect its properties.

MS wrote:

When you select a control, the PropertyGrid shows properties on that control. You can examine or change property values here. You should note that custom types are supported as long as they are binary serializable (see Basic Serialization).

Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.

BillWoodruff wrote:

he issue here is not what you can do by hacking, but how to securely

BillWoodruff wrote:

The link you posted was to the expensive MicroFocus tool

Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.

Member 2458467 wrote:

backgroundWorker1 is difficult to use and the computer freezes

bool _isStopped = true;
public Form1()
   {
       InitializeComponent();
       backgroundWorker1.WorkerReportsProgress = true;
       backgroundWorker1.WorkerSupportsCancellation = true;

       lblStatusPlaySound.ForeColor = Color.Violet;
       lblStatusPlaySound.Text = "Status: PLAY/STOP";
   }
private void btnPlaySound_Click(object sender, EventArgs e)
  {
      // Start the asynchronous operation.
      backgroundWorker1.RunWorkerAsync();

      using (SoundPlayer player = new SoundPlayer(Properties.Resources.ring))
      {
          player.Play();
      }

      while (_isStopped == true)
      {      
         if (backgroundWorker1.IsBusy != true)
         { _isStopped = true; }
         else //
         { _isStopped = false; }

         lblStatusPlaySound.ForeColor = Color.Green;
         lblStatusPlaySound.Text = "Status: PLAY";
         lblStatusPlaySound.Refresh(); //                
         Debug.Print("Status: PLAY");
     }

     lblStatusPlaySound.ForeColor = Color.Red;
     lblStatusPlaySound.Text = "Status: STOP";
     lblStatusPlaySound.Refresh();             
     Debug.Print("Status: STOP");

  }