|
.
667: The neighbour of the Beast
|
|
|
|
|
|
.
667: The neighbour of the Beast
|
|
|
|
|
|
gone
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|
|
|
Possible he is the author of the book? Look like most of the contents were copied from the book.
For instance, just to point out a few, the below paragraphs are from page 106
Quote: First: anything that comes from the outside world should not be trusted initially. Malicious users can enter all sorts of exploits through a form that can undermine the security of your site. So, any form data must be sanitized before you use them.
Secondly: the field values in request.POST or request.GET are just strings. Even if your form field can be defined as an integer (say, age) or date (say, birthday), the browser would send them as strings to your view. Invariably, you would like to convert them to the appropriate Python types before use. The form class does this conversion automatically for you while cleaning.
page 109
Quote: CSRF_Token is the security mechanism against Cross-Site Request Forgery (CSRF) attacks for your forms. It works by injecting a server-generated random string called a CSRF token, unique to a user's session. Every time a form is submitted, it must have a hidden field that contains this token. This token ensures that the form was generated for user by the original site, rather than a fake form created by an attacker with similar fields.
Bryian Tan
|
|
|
|
|
Well ... the names aren't even close, and if you wrote a book on this, and you copied whole passages for an article wouldn't you want to reference the original in the hope that someone might buy it?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
"This is the third article..."
Did you look at the other two?
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
|
|
gone
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|
|
|
Richard Deeming wrote: Anyone brave / foolish enough to try running the exe to see if it's genuine?
I thought that's what VMs are for.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
I did suggest to the author that it should go in Free Tools. But I guess the term "Free Tools" when translated to American comes out as "Tip/Trick" "Well I'll just post it somewhere else and hope they don't notice".
modified 17-May-18 10:46am.
|
|
|
|
|
Neither the other article: Easy Log Viewer. Yet another log viewer tool, but Easier.[^] not the tip/Trick Open Source .NET License Tool, EasyLicense ![^] contain code.
In addition, the tip/trick even has accusations of plagiarism / bad licensing although the author asked the original creator and posted a Screenshot of the email.
I am not that trusted with licenses... @Sean-Ewington I think you should have a deeper look in this topic to clarify if it is legal or not what he is doing.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
|
|
.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
|
|
|
|
|
gone
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|