For a language-agnostic consideration of the design decision, see What is the advantage of having this/self pointer mandatory explicit?. To close debugging questions where OP omitted a self parameter for a method and got a TypeError, use TypeError: method () takes 1 positional argument but 2 were given instead. If OP omitted self.

Context Explanation

in the body of the method and got a NameError, consider How can ... What is the purpose of the `self` parameter? Why is it needed? The W3C's WebAppSec Working Group is starting to look at the issue.

Insight Material

See, for example, Proposal: Marking HTTP As Non-Secure. How to create a self-signed certificate with OpenSSL The commands below and the configuration file create a self-signed certificate (it also shows you how to create a signing request). I've gone through the steps detailed in How do you use HTTPS and SSL on 'localhost'?, but this sets up a self-signed certificate for my machine name, and when browsing it via https://localhost, I receive the Internet Explorer warning. Is there a way to create a self-signed certificate for "localhost" to avoid this warning? This creates a self-signed (-r) certificate, with an exportable private key (-pe).

Final Conclusion

It's named "My CA", and should be put in the CA store for the current user. We're using the SHA-256 algorithm. The key is meant for signing (-sky). The private key should be stored in the MyCA.pvk file, and the certificate in the MyCA.cer file. security - How do I create a self-signed certificate for code signing ... I get this warning while testing in Spring Boot: Mockito is currently self-attaching to enable the inline-mock-maker.

This will no longer work in future releases of the JDK. Please add Mockito as an You have a certificate which is self-signed, so it's non-trusted by default, that's why OpenSSL complains. This warning is actually a good thing, because this scenario might also rise due to a man-in-the-middle attack.