Opensource maskerkeying project proposal - restarted

[WhiteHat]

Hi all,

I'm looking at starting a sourceforge project to create an open source
master key system generator to commence next year sometime. I'm
hoping for some feedback on the following proposal. any feedback
is good - from programmers and lockies alike.

Critical things are:
1. does something like this exist already?
2. would it be used?
3. what are some critical features missed below?

Please note that this is a proposal, not a complete specification.
please also note that I know very little about master keying so I may
not be considering something in the proposal below that could be obvious
to the rest of the world.

----------------------------------------
Project title:
Open-Source Master Key (OMK)

Overview:
This project will produce an open source master key system generator
equivalent to current commercial products.

Scope:
In it's initial phase, this project will not produce a key management system,
merely an automated tool to generate key depths etc. perhaps as an
additional release, a key management tool could be added.

There will be a requirement for a file format for the import/storage
of data such as keying depths/macs etc, including standardised identifiers
for manufacturers. example: delimited or fixed width file format similar
to the one I generated here:
viewtopic.php?t=5240
with the ability to include I.C. locks, rotating pins (corbin-russwin/medeco)
etc.

Proposed Duration:
12 months

Project advantages:
1) Lockies will have access to free, high quality master key system generator.
2) A standard for storing key depth information will have been developed that
can potentially be used for other comercial products
3) Project and software has funky Three letter acronym which rolls off the
tounge.

Preliminary Specs:
- Must be able to import standardised file types (to be developed) containing
keying data. file format changes to be managed by project team.

- Must allow manual entry of keying information.

- Must be able to create a printable sheet for the master key system generated

- Must allow transfer of data into common spreadsheeting products.

- interface must be user friendly and proffessional looking.

- include options for customisation of MK system rules such as "all master keys
must have cuts higher than lower level change keys" (to prevent filing down
a change key to make a master key etc).

[skold]

WhiteHat..That will be extremely useful. . . and very popular

[Hojo]

http://www.secsoft.com/keymastery.htm

This has got what you mean in it, I can program in VB (Visual Basic) and I was thinking of making my own, would be preatty tricky, Ill give it a go...

[WhiteHat]

well hojo - if you can whip up something like that the product in that link by yourself, then by all means go for it, but I think that you'd seriously be underestimating the amount of work required.

I am actually serious about doing this. Commencing a project on sourceforge would mean that the team would have access to programmers, graphic designers, documentation writers and all the project tools that are given to projects accepted on sourceforge.

by going through the proper software development life cycle, then there is for one a higher chance of the project being completed to a professional level.
-----standard SDLC-------------------
Identification
specification (design)
formalisation
development
Testing
implimentation
with documentation all the way through...
------------------------

I'm also looking for comments describing desired features, problems with existing systems, potential issues that people can see etc.

[Rockford]

Whitehat - I have a background in Performance and Integration testing of software products, so I was surprised to see testing towards the bottom of your list of activities. Testing should be an on-going process throughout the development lifecycle. If you've heard of the "V model" approach to testing, this will identify the various testing activities, the point at which it should be performed, and who should undertake them.

Cheers
Rockford.....

[32768]

I spend most of my time doing requirements elicitation and validation and automated testing. I'm involved in several projects on sourceforge, and I was somewhat concerned by this statement:

Commencing a project on sourceforge would mean that the team would have access to programmers, graphic designers, documentation writers and all the project tools that are given to projects accepted on sourceforge.

The programmers, graphic designers, and documentation writers are all here already. I see evidence of that every time I log on. It has been my experience that you don't generally find much new programming talent through sourceforge. I think it will work much better to recruit them from here than to post up a new listing and wait for the offers of help to come in.

The requirement that the user should be able to enter new keying rules is very interesting. It implies that we have some way for the user to formulate the rules in a precise enough way that it can be automatically translated into code which will test a set of keying combinations for compliance and reject those bittings which violate the rules.

And this has to be usable by a typical institutional locksmith- not to put them down, but training in mathematical logic isn't usually a job requirement. We could have them formulate rules in Prolog then use an automated theorem prover to find bittings which pass. I think some kind of menu system which allows the user to customize rules, or possibly choose from a set of pre-written rules is much more practical. i.e., "Reject bittings which have adjacent cuts which differ by more that [3,4,5,6]. [yes/no]"

It could even have themes which would set all the options according to some standard- for example, key according to Foley-Belsaw's rules.



[/quote]

[Chucklz]

Count me in. I think alot of work will be necessary to "de-geek" the software. Just look at the goodies in say, KDE. Far too much for the average non-geek to take the time to learn. But then look at the success of the Firefox project-- the moz people keep it simple and funtional.

[PickPick]

For setting the rules, it might be best to generate rule files with some sort of logical script language so the pros can edit it by hand but keep a GUI with just a couple of yes/no questions for the rest. Like an extra wizard-mode for the experts and easy-mode for the logically challenged.

As for feature suggestions, here's my personal feature wish for X-mas:
When I enter the bittings of a change key and the manufacturer/model/series I'd like the program to give me a printable chart on which the necessary keys for TMK extrapolation are lined out. So at least with some of the straight to semi-straight keyways I can cut the keys out of plastic and start extrapolating. And if you could call that entry "PickPick function" you'd make me very happy. (I'm starting to experiment with this extrapolation stuff a bit and plan to do a presentation on it, hopefully without my university kicking me out for messing up their MK system)

Another very important function would be hard cryptographic protection for keying records. I don't know how other programs handle it, but if the keying records are obtained and the program to use them is easily accessible, attacks become easier.

[Varjeal]

I'm a locksmith with a fair amount of info on masterkey systems...you can ask me stuff regarding "rules" and such like. Just don't ask me to do any programming.

[32768]

I'm a locksmith with a fair amount of info on masterkey systems...you can ask me stuff regarding "rules" and such like. Just don't ask me to do any programming.

Great! That'll be essential. Also test driving...

I have a big feature request. Let's not tie it to any one specific OS / platform. This could be done by, for example, coding it in java or using ansi c with gtk. If you don't like interpreted languages, compile the java bytecode to native code for your favorite platform. I don't think speed will be an issue, and we could run it on mobile phones or PDAs.

And finally, a name suggestion:
Masterkey Automation, Zoning, and Organization for Lock Authorities.

[Jarod]

if its for linux and free then i'm in!!

[Pickey]

And finally, a name suggestion:
Masterkey Automation, Zoning, and Organization for Lock Authorities.

Lol

[Hak]

It would seem Mazola is this forum's "secret" little fetish

[Buggs41]

Well, after all, we are at the top of the 'google' list.

[WhiteHat]

Testing should be an on-going process throughout
the development lifecycle. If you've heard of the "V model" approach
to testing, this will identify the various testing activities, the
point at which it should be performed, and who should undertake them.

yes, I have the V model somewhere *rummages through papers on desk*
and you're right, I just regurgitated the standard sdlc that I learnt
in high school. I do believe that testing at all stages of
development is an extremely important part of project work.

I spend most of my time doing requirements elicitation
and validation and automated testing. I'm involved in several projects
on sourceforge,

awesome - this is what we want - people from many disciplines who are
able to add their skills to the project.
you've probably guessed that I have 0 experience on sourceforge
until recently. I also agree and this thread has already demonstrated
that the required talent exist already on this board.

And this has to be usable by a typical institutional
locksmith- not to put them down, but training in mathematical logic
isn't usually a job requirement.

you're probably right, however varjeal has mentioned that he does
his master keying by hand, so I'd assume that they'd have a general
idea. it will depend on how complicated it gets of course.

It could even have themes which would set all the
options according to some standard- for example, key according to
Foley-Belsaw's rules.

that's an excelent idea - what other standards like that exist?

Count me in. I think alot of work will be necessary
to "de-geek" the software. Just look at the goodies in say, KDE. Far
too much for the average non-geek to take the time to learn. But then
look at the success of the Firefox project-- the moz people keep it
simple and funtional.

yes, must be user friendly, not only that, but locksmith friendly...
much UAT is required.

I'd like the program to give me a printable chart on
which the necessary keys for TMK extrapolation are lined out.

I have no Idea what you're talking about *googles for masterkey
extrapolation* but it sounds like a good idea. one of the reasons
I included "must produce a printable sheet" is because it's often
easier to carry a piece of paper arround to
scribble on than even a PDA etc.

Another very important function would be hard
cryptographic protection for keying records.

hadn't thought about that sort of thing. it's probably a good idea.

that got me thinking - perhaps as well as a standardised key info
input file format, there could be developed a standardised masterkey
system file (*.omk or whatever) which would be encrypted and could
be transfered and in the future be imported by other comercial
products... hmmmm..

I'm a locksmith with a fair amount of info
on masterkey systems...you can ask me stuff regarding "rules"
and such like

thank you for your offer! - we'll need all the help we can get from
lockies all the way through the process.

homework for everyone - get your head around how masterkeying works.

I have a big feature request. Let's not tie it to any
one specific OS / platform.

yep - agree with that. I think it would be quite cool to have
zero software expenses to run a business.

Masterkey Automation, Zoning, and Organization for Lock Authorities.

developed by the Open Institute for Locksmithing Software

I'm far from the best programmer or even requirements gatherer
on this board (however I ever end up going head to head with anyone in a PL/SQL write-off, then I'll woop all your butts! )
so what I'm hoping to do is provide motivation, moderation, management
and mazol....uh....

For a starting date, I'm hoping early in the new year, and preferably after
this LP101 guide gets sorted finally... but that's not to stop requirements
gathering.

32768 - can you give us a rundown on requirements gathering processes?
I studied for but never took the microsoft 70-100 exam, and as part of my
job I gather requirements for whatever piece of work is next in line,
I've even taken a few project management courses, but I've never
managed a large project before. so bear with me. or if there's anyone
here who wants to take on the job, I'm happy to sit on the sidelines
and cheer the project on!