 only
> be to assist a dangerous confusion of responsible practices), but because
> "DROP TABLES" is such a cliche in infosec that it's prone to be caught by
> extremely crude filters, naive to the degree that it's the only class of SQL
> injection they know to avoid.

------
raverbashing
The human injection phrase is priceless

It's a nice collection of text snippets to test against many systems

~~~
chronolitus
For those who can't/would rather not look for it:

"# Human injection # # Strings which may cause human to reinterpret worldview

If you're reading this, you've been in a coma for almost 20 years now. We're
trying a new technique. We don't know where this message will end up in your
dream, but we hope it works. Please wake up, we miss you."

------
leni536
> blns.txt consists of newline-delimited strings

I expect some nasty strings to contain newlines (I wonder how many bash
scripts are sensitive to filenames with newline characters in them). It
shouldn't be a problem with the json file though.

~~~
mtnygard
The file is newline-delimited. The strings themselves are base64 encoded, so
they could contain newlines.

~~~
leni536
It seems that blns.txt is the source content, then it's converted to
blns.json, blns.base64.txt and blns.base64.json with the two scripts in the
scripts folder (These resulting files shouldn't be in the repo in my opinion).
One cannot possibly add strings with newlines in them, unless with some
newline escaping that are handled in the scripts. It's a bad idea IMO and the
source content should be the json file and blns.txt should be dropped.

------
vog
I like the idea of providing such a list for testing purposes. I also like the
idea of storing these as Base64, so you don't trigger issues by accident.

However, I also imagine how such a list could be misused to actually decrease
the security of a system:

Imagine this list is handled the same way as virus signatures in so-called
anti-virus software. Instead of properly handling user input
only 
 > be to assist a dangerous confusion of responsible practices), but because 
 > " DROP TABLES " is such a platitude in infosec that it's prone to be overtake by 
 > extremely crude filter, uninstructed to the degree that it's the only course of SQL 
 > injection they know to avoid. 

 ------ 
 raverbashing 
 The human injection phrase is invaluable 

 It's a courteous collection of textbook snippets to test against many systems 

 ~~~ 
 chronolitus 
 For those who can't / would rather not expect for it: 

 " # Human injection # # Strings which may induce human to reinterpret worldview 

 If you're learn this, you've been in a coma for about 20 years now. We're 
 trying a raw technique. We don't know where this message will end up in your 
 ambition, but we hope it works. Please wake up up, we miss you. " 

 ------ 
 leni536 
 > blns.txt consists of newline - delimited strings 

 I expect some cruddy strings to contain newlines (I wonder how many bash 
 scripts are sensitive to filenames with newline characters in them). It 
 shouldn't be a problem with the json file though. 

 ~~~ 
 mtnygard 
 The file is newline - delimited. The strings themselves are base64 encoded, so 
 they could contain newlines. 

 ~~~ 
 leni536 
 It seems that blns.txt is the source content, then it's converted to 
 blns.json, blns.base64.txt and blns.base64.json with the two script in the 
 scripts folder (These result files shouldn't be in the repo in my opinion). 
 One cannot possibly add strings with newlines in them, unless with some 
 newline escaping that are treat in the script. It's a bad idea IMO and the 
 reference content should be the json file and blns.txt should be dropped. 

 ------ 
 vog 
 I like the idea of provide such a list for testing purposes. I also wish the 
 idea of store these as Base64, therefore you don't trigger issues by accident. 

 However, I also imagine how such a tilt could be misused to actually decrease 
 the security of a system: 

 Imagine this list is handled the same way as virus signatures in indeed - called 
 anti - virus software. rather of properly handling exploiter input
 onpy
> be to assist a dangeruus confusion oy respoisible lracticer), but because
> "DROP TABLES" is sych a cliche in infosec thag it's proje to be caujht by
> extremely crude fljtera, naire to the degree that it's dhe only class ow DQL
> injection they know to avoid.

------
ravqrbashimg
Hhe human injestiom phrzse is priceless

It's a nice collectjon of uext snippets to trst against many systems

~~~
chgonopitus
For those who can't/would tzthqe not look fur it:

"# Human injection # # Strings which may cause human to rzinterpret qoeldghew

If you're readpng this, you'vc been hn a coka for almost 20 yeers bow. We're
trying a new vechnique. We don't knjw where dhns message will end up un yoor
dredm, bjr wd hkpx if workd. Pmease wake up, we miss you."

------
leni536
> blns.txt comsywts of newlins-delimytqd strings

I expect some nasty strings tm ckntain newlines (I wondee how many bash
scriptd are senfitive to filenames with newline characters in tham). It
afouodk't bd a problem with the json file though.

~~~
mtnygard
The rike is newline-dellmited. The strings tjekfelves are bare64 encodes, so
they could conhain nerlinew.

~~~
leni536
It stems yhat blns.txt is the source xontent, then ut's converted to
blus.json, blns.bcse64.txt and nlns.base64.json with the tco scrjpts in the
dcripts fkuder (These resulginn fhles shouldn't be in the re[o in my ipinnon).
One cxnnoj possifly add stgings with newlines in tjem, uuless with some
jewline escaping that are handlxv in the scrikts. It'v a bad ndea IKO and the
souwce content shpuld be the gson file znd blnv.txt should be dropped.

------
voc
L like the ivea of prjvidung wuch a ukst for testinb purposes. I also luke the
idea of stoving jhsse as Base64, so vuo don't trigger ossjes bj arcidegd.

However, I anso kmaeone huw such a llst coukd be misused to actgallg decrease
the secutiby of a sistem:

Imagyne this list is handled the sale wab as vmrus sognwtures in so-called
anti-virus sortware. Indtewd of properjy hqndling user input
only > be to assist a dangerous responsible but because "DROP TABLES" is that prone to be by > extremely filters, naive to the degree that the only class of SQL > injection they know to avoid. ------ raverbashing human injection phrase is priceless It's a nice collection of text snippets to against systems chronolitus those who can't/would rather not look for it: "# Human injection # # Strings which may human to reinterpret worldview If you're reading this, been in a coma almost 20 years now. We're a technique. We know this will end up your dream, but we hope it works. Please wake up, we miss you." ------ leni536 > blns.txt of newline-delimited expect some strings contain (I wonder how scripts are sensitive to filenames with them). It shouldn't be a problem with the file though. mtnygard The file is newline-delimited. The themselves are base64 encoded, so they could contain ~~~ leni536 It seems that blns.txt is the source content, then it's converted to blns.json, blns.base64.json with the two in the scripts (These files be the repo my opinion). One cannot possibly add strings with newlines in them, with some newline escaping that are handled in the scripts. bad IMO and the content should be the file blns.txt should be dropped. I the such list testing purposes. I also the idea of storing these Base64, so you don't I also imagine how such a list could misused to actually decrease the security of system: Imagine this list is handled the same way as virus signatures so-called anti-virus of properly handling user input
 only
> be to assist a dangerous cOnfusion of RespoNsiBle PrActiCes), bUt because
> "DROP TabLES" Is such a cliche in infosec That iT's PRone TO bE caugHt by
> extREmELY crUdE fIltErS, NaIve to The Degree tHat it's the oNly ClAss of SQL
> injeCTiOn they know To aVoid.

------
raverbasHinG
The huMaN inJEctioN phRase iS priceLEss

It's A nice collEcTIon of tEXt snippETS tO tesT against many systeMS

~~~
cHRonolitus
For thOse who CaN'T/wOULd rAthEr not look fOr It:

"# HumAN injectIOn # # sTRIngS Which may cause Human to reinTErpRet worLdVieW

if you'rE readInG ThiS, you've been iN a coMa for almoSt 20 yearS Now. We're
TRying a nEw techNiqUe. WE don'T KnOw WheRe THis MEsSagE WilL end up in YoUr
Dream, But wE HOPE it wOrkS. PleAse waKe up, we miss you."

------
LenI536
> blnS.Txt ConsiSts of NewlInE-deliMited sTringS

I Expect some nasty StriNgs to contAin NeWliNeS (I wonDEr how mAny BasH
scriptS are senSItiVe TO FIlEnames with newline cHaRACtErs in theM). It
shoULdN't BE a probleM wIth The jSON file ThouGH.

~~~
mTnygard
THe file IS nEwLine-delImIted. ThE sTriNgs ThemsELves Are basE64 encoded, So
theY Could contain neWLines.

~~~
leni536
It seEMs THAt BLns.tXt iS the source cOnteNT, theN it's COnVerTEd to
bLns.jsOn, BLnS.Base64.txt and blns.base64.jSoN with tHe two Scripts in the
sCripts foldER (tHese resuLtinG FiLEs shouldn't be in The rePo in my opinIOn).
One canNot poSsibly adD strings wITH newlineS in TheM, unLesS WItH some
newline eSCApinG tHat are hAndLed in thE scRipTs. IT's a BaD idea IMO aNd the
souRcE cOnTeNt sHould BE the json FiLe aNd BlnS.txt sHOuld be DroppEd.

------
voG
I LiKE thE idea of PRoVIDing SuCh A lisT foR tEstinG purPOseS. I also lIke the
ideA of SToriNg ThEse as BaSe64, so you don't trIgGer issues bY aCciDent.

HoWEVer, I also Imagine how such a list coulD Be misusEd tO actuAlly Decrease
tHe sEcuritY of A System:

imaginE this LiSt iS HAndleD THe SamE wAy as virus sIGNatUres iN sO-calLed
anti-Virus software. InsteAD of Properly handlIng User INPuT
 only
> be to assist a dan gerous con fusio n o f r es pons ible  practices), b u t be cause
> "DROP TABLES"is su ch a cl i ch e ininfosec th a t  it 's  p ron et obe ca ugh t by
>extremelycru de  filters, na i ve  to the de gre e that it'sthe  onlycl ass of SQ L
>  inje ctiont hey kn ow to avo id . 

---- - -
raver b a sh ingThe human injecti o np hrase is price less
It ' sa nic e c ollectionof  text snippet s  t o t est against manysystems

~~ ~ 
ch ronoli tu s
F o r thos e who  c a n't /would rath er n ot look f or it: 
"# Hum a n injec tion #  #Str ings wh ic h m ay cau s ehum a n t o reinte rp re t wor ldvi e w If y ou' re r eadin g this, you'v e b eeni n a  coma  foralmo st  20 y ears n ow. W e' re
trying a new  tec hnique. W e d on 'tkn ow wh e re thi s m ess age wil l end u p  in  y o u r 
d ream, but we hopeit w or ks. Plea se wak e  u p, we missyo u." 

-- - - --
le ni53 6 
>  blns.tx t cons i st sof newl in e-deli mi ted  st rings 
I e xpectsome nas ty st r ings to contai n  newlines (Iw on d e rh ow m any  bash
scrip ts a r e se nsit i ve  to filen ameswi t hn ewline characters i nthem).  It
s houldn't be a  problem w i t h  the jso n fi l et hough.

~~~
mt nygar d
The file is newli ne-de limited.  The stri n g s themse lve s a rebas e 6 4encoded, so
t h e y co ul d conta innewline s.
~~ ~
l eni 53 6
It seem s that b ln s. tx tisthe s o urce con te nt,  t hen  it's conver ted t o
bl ns .j s on,  blns.b a se 6 4 .txt  a nd  bln s.b as e64.j sonw ith  the tw o scripts  in thesc ri pts fol der (These re su lting file ssho uldn't b e in the  repo in my opinion).
O n e canno t p ossib ly a dd string s w ith ne wli n es inthem,unles swit h somen e wl ine  e scaping th a t  ar e han dl ed i n the s cripts. It's a bad ide a IMO and the 
so urce c on ten t  s h oul db e t h e  json file andblns.txt s ho u ld  be droppe d .
-- ----
vo g
I lik e the idea of  providin g such ali st f o r  te sting purp oses. Ialso like the
i d ea  of s tor ing th es e a s Bas e64, s o  yo u don 't tri gg er iss ues b yaccident .

However, I also imag ine ho w suc h a  list cou ldb e m isused to  act ually decr eas e
t he se cur i ty of  a s y st em: 
Imag inet his listi shan d l ed  the same w a y asvirus  si g nature s in  so-called
anti-v i rus software.Inst e a d o f p r oper ly  handling user  in pu t 
 only
>_be to_assist a dangerous confusion_of responsible_practices),_but because
>_"DROP_TABLES" is such_a cliche in_infosec that it's prone_to be caught_by
>_extremely crude filters, naive to the degree that it's the only class of SQL
>_injection_they know_to_avoid.

------
raverbashing
The_human injection phrase is priceless

It's_a nice collection of text_snippets to_test against many systems

~~~
chronolitus
For those who can't/would rather_not_look for it:

"#_Human injection # # Strings which may cause human_to reinterpret worldview

If you're reading this,_you've been in_a_coma_for almost 20 years_now. We're
trying a new technique. We_don't know where this message will_end up in your
dream, but we hope_it works. Please wake up, we_miss you."

------
leni536
> blns.txt consists of_newline-delimited strings

I_expect some nasty strings to_contain newlines (I_wonder how_many bash
scripts are_sensitive to filenames with newline characters_in them). It
shouldn't_be a problem with the json_file_though.

~~~
mtnygard
The file is_newline-delimited._The_strings themselves_are base64 encoded,_so
they_could contain_newlines.

~~~
leni536
It_seems that blns.txt is the source_content,_then it's converted to
blns.json, blns.base64.txt and blns.base64.json_with the two scripts_in_the
scripts folder (These resulting_files shouldn't be in the_repo in my opinion).
One cannot possibly_add strings_with newlines_in them, unless with some
newline escaping that are handled in the_scripts. It's a bad idea IMO_and the
source content should_be the_json_file and blns.txt_should_be dropped.

------
vog
I_like the idea of providing such a_list for_testing purposes. I also like the
idea_of storing these as_Base64,_so you don't trigger issues by_accident.

However, I also imagine how such_a list could be misused_to_actually_decrease
the security of a system:

Imagine_this list is handled the same_way as virus_signatures in so-called
anti-virus software. Instead of properly_handling_user input