Last week, I wrote about a subtle security enhancement that password managers provide out of the box. This week I want to highlight the main reason why I like password managers.
Password managers are undervalued. Not only do they provide an easier way to store passwords, they offer so many little security enhancements I start to take for granted.
In the newer services at my client, AutoMapper is used to map DTO‘s to database objects and back. Because mocking a mapping isn’t obvious, a lot of behaviour wasn’t tested and that’s unacceptable. Let’s find out how to properly inject an
IMapper with actual mappings.
At work, I have a small gripe about a
Response class. It’s minor, but it keeps bugging me.
The software I’m working on needs a new authorisation system. The system needs to be prepared for 3 scenarios: to restrict access to a page, to hide part of a page and to block access to data. Let’s solve these problems using claims.
To create a report, I had to combine the contents of several PDFs into one. Thanks to iTextSharp, it’s really easy. Then I had the problem, how do I test this?
Troy Hunt tweeted how a site uses a fake password field so that browsers wouldn’t show the insecure warning. If you want to know the details of this incident, I gladly refer to Troys blog post. In this blog, I want to talk about the deliberate malpractice that goes into this behaviour.
While writing an XML parser I customised, my unit tests all failed with an error message along the lines of “Could not load file ‘C:\Users[username]\AppData\Local\Temp[guid]\Data\test.xml’ or one of its dependencies. The system cannot find the file specified.”.