Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ Simple answer: because there are other ways than HTTP requests to exploit
SQLi vulnerabilities ! Most of the available tools only rely on HTTP GET/POST
methods, and sometimes provide other methods.

PySQLi is thought to be easily modified and extended through derivated classes
PySQLi is thought to be easily modified and extended through derived classes
and to be able to inject into various ways such as command line, custom network
protocols and even in anti-CSRF HTTP forms.

Expand Down
4 changes: 2 additions & 2 deletions pysqli/core/context.py
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ def get_field_type(self):
"""
return self.__field_type

## Enable SQL string encvoding
## Enable SQL string encoding
# Enable SQL string encoding to evade anti-quote functions or WAF

def enable_string_encoding(self, enabled):
Expand Down Expand Up @@ -284,7 +284,7 @@ def set_inband_fields(self, fields):
Set inband fields

Inband fields are quite special: they are described with a single string
with these possible caracters:
with these possible characters:
- s: specify a string field
- i: specify an integer field

Expand Down