How do your clients deal with information complexity?
by Bernice de Braal and Peter Newman, Information World Review People deal with information complexity by either reducing that complexity or absorbing it. Knowing whether your clients are shrinkers or swallowers is a key insight for information professionals There is a consensus that the world has entered a knowledge era where information is power and rapid learning [...]
Hi,
I am setting password complexity in SLES 11. I am able to do most of things
pam-config -d --pwcheck
pam-config -a --cracklib
pam-config -a --cracklib-minlen=8
pam-config -a --cracklib-dcredit=-1
pam-config -a --cracklib-ocredit=-1
pam-config -a --pwhistory
pam-config -a... (1 Reply)
Hi,
How to configure minimum passphrase (Not UNIX password) requirements on any UNIX box?
Passphrase - the one user enteres while generating pub/pvt keys using ssh-keygen.
Thanks!
Reddy (3 Replies)
This is a general question about the practical use of computational complexity in security. Wikipedia has a good article about the theoretical background of computational complexity. In the course of conversation with colleagues, a topic that is brought up occassionally is the security of any... (2 Replies)
Hi,
I am looking for a simple way to :
- force the user to change his password following the first connexion
- check the complexity of a password (password should has a least 8 characters with 1 special char and 1 alpha...).
Thinks for your help (1 Reply)
Perl::Critic::Policy::Modules::ProhibitExcessMainComplexUser3Contributed Perl DocuPerl::Critic::Policy::Modules::ProhibitExcessMainComplexity(3pm)NAME
Perl::Critic::Policy::Modules::ProhibitExcessMainComplexity - Minimize complexity in code that is outside of subroutines.
AFFILIATION
This Policy is part of the core Perl::Critic distribution.
DESCRIPTION
All else being equal, complicated code is more error-prone and more expensive to maintain than simpler code. The first step towards
managing complexity is to establish formal complexity metrics. One such metric is the McCabe score, which describes the number of possible
paths through a block of code. This Policy approximates the McCabe score by summing the number of conditional statements and operators
within a block of code. Research has shown that a McCabe score higher than 20 is a sign of high-risk, potentially untestable code. See
<http://en.wikipedia.org/wiki/Cyclomatic_complexity> for some discussion about the McCabe number and other complexity metrics.
Whereas Perl::Critic::Policy::Subroutines::ProhibitExcessComplexity scores the complexity of each subroutine, this Policy scores the total
complexity of all the code that is outside of any subroutine declaration.
The usual prescription for reducing complexity is to refactor code into smaller subroutines. Mark Dominus book "Higher Order Perl" also
describes callbacks, recursion, memoization, iterators, and other techniques that help create simple and extensible Perl code.
CONFIGURATION
The maximum acceptable McCabe score can be set with the "max_mccabe"
configuration item. If the sum of all code outside any subroutine has a McCabe score higher than this number, it will generate a Policy
violation. The default is 20. An example section for a .perlcriticrc:
[Modules::ProhibitExcessMainComplexity]
max_mccabe = 30
NOTES
"Everything should be made as simple as possible, but no simpler."
-- Albert Einstein
Complexity is subjective, but formal complexity metrics are still incredibly valuable. Every problem has an inherent level of complexity,
so it is not necessarily optimal to minimize the McCabe number. So don't get offended if your code triggers this Policy. Just consider if
there might be a simpler way to get the job done.
SEE ALSO
Perl::Critic::Policy::Subroutines::ProhibitExcessComplexity
AUTHOR
Jeffrey Ryan Thalhammer <jeff@imaginative-software.com>
COPYRIGHT
Copyright (c) 2005-2011 Imaginative Software Systems. All rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of this license
can be found in the LICENSE file included with this module.
perl v5.14.2 2012-06-07 Perl::Critic::Policy::Modules::ProhibitExcessMainComplexity(3pm)
