PHP tutorial for beginners.
Preface I’m cranky. I complain about a lot of things. There’s a lot in the world of technology I don’t like, and that’s really to be expected—programming is a hilariously young discipline, and none of us have the slightest clue what we’re doing. This is not the same. PHP is the lone exception. DeveloperWorks : Open source : Technical library. Top Design Magazine - Web Design and Digital Content - StumbleUpon.
Laravel. Auth/ACL implementation strategies « Internet Strategy Guide. I’m going to talk more about ACLs than Auth.
Auth is simple, it’s the ACL that will trip you up. Since both concepts are coupled together when you’re making a login system, I feel it’s appropriate to at least touch on Auth. What I want to cover is the ways we can create the ACL object to suit needs based on the scale of the project. I’m going to assume that readers have a passing familiarity with using the Auth and Acl objects and may have even implemented them into projects. Zend_Auth The reason I say Auth is simple is because Zend Framework makes it simple with their Zend_Auth class. Zend_Acl So how do we create our Acl? Scaling I tend to put my scaling into one of the following categories: small,decent or ZOMG.
HardcodedAs part of my Navigation Object propertiesPulled from a database Hardcoded This one is easy to implement since if you follow the ZF reference or the numerous guides/posts you find when you google for auth/acl systems, you’ll be able to hardcode your ACL. How to build role-based access control in SQL at Xaprb. The posts I’ve been reading and writing recently have reminded me how Object-Relational Mapping (ORM) systems make it fun and convenient to interact with databases.
For some of the reasons they’re a developer’s favorite, they can be a database administrator’s nightmare (think surrogate keys). But designing tables with a consistent set of columns has its benefits. Just because the columns are meta-data that have no intrinsic meaning doesn’t mean they have no value. In this series of articles I’ll show you several ways to use such “meaningless” meta-data to enable powerful, efficient application-level role-based access control (RBAC) in the database, with a focus on web applications, though you could do this for any application. A lightweight approach to ACL - The 33 lines of Magic » Debuggable Ltd. Ok, I just finished a terrible (extended) weekend that featured 12 hours of CSS coding.
The only reason I didn't loose my sanity was that I finally decided to figure out what the heck is wrong with IE. Those of you who have to do get their hands dirty in the field of graphics, css, and other non-php work from time to time as well, make sure to check out Position is Everything at some point, it really helped me out quite a bit so far. Anyway, that's not really what I want to talk about today. One of the topics I have been very silent about for months is ACL. At the end of May I was somewhat unhappy with some of the things regarding the CakePHP DB ACL implementation. But let me go a step back and explain my initial idea. Posts:index,Posts:view,Posts:admin_edit,Articles:index,... Datenbank-Verwaltung in einer einzigen PHP-Datei.
The Usability of Passwords (by @baekdal) #tips. Security companies and IT people constantly tells us that we should use complex and difficult passwords.
This is bad advice, because you can actually make usable, easy to remember and highly secure passwords. In fact, usable passwords are often far better than complex ones. So let's dive into the world of passwords, and look at what makes a password secure in practical terms. Update: Read the FAQ (updated January 2011) Update - April 21, 2011: This article was "featured" on Security Now, here is my reply! How to hack a password The work involved in hacking passwords is very simple. Asking: Amazingly the most common way to gain access to someone's password is simply to ask for it (often in relation with something else). When is a password secure? You cannot protect against "asking" and "guessing", but you can protect yourself from the other forms of attacks.
The measure of security must then be "how many password requests can the automated program make - e.g. per second". Getting Real. Here are the 16 chapters and 91 essays that make up the book.
Introduction chapter 1 What is Getting Real? A smaller, faster, better way to build software About 37signalsOur small team creates simple, focused software Caveats, disclaimers, and other preemptive strikesResponses to some complaints we hear The Starting Line chapter 2.
Security. Tools. Articles. Libraries. Xampp.