[Logic-security-developers] Project status

[Greg T. <gre...@ya...>]

Hello to logic-sec developers.

I worked on the project a lot today, but due to its
structure, it's extremely frustrating to work on. I
narrowed the build errors down from over 300 to less
than 100, but it's still not complete. And, as you can
see in my forum post, none of those changes were
committed.

From this point on, I will lend advice to project
developers and will remain on the developer team, but
will not actively code for the project. I will leave
the following as an excercise to the other
developers-in-learning.

- Do not use system() calls. They are Windows-specific
and will not port.

- Do not create secret, undocumented back doors.

- Always use UNIX file encoding.

- Do not implement your own encryption and
pseudo-random-number generation. Instead, you could
try coding for OpenSSL's library.

- Do not include all functions and classes from one
header file. Instead, so that dependencies are more
clear, create an invididual header/module pair for
each associated set of functionality (not each
individual function), and then perform individual
#includes.

- You may completely discard the ASCII reverse module,
the notepad module, and all other modules which do not
specifically contribute to the useful functionality of
the project.

- You may discard plugin functionality, as it is
rather superfluous and will likely never actually be
used.

- You may discard the menu-driven interface
completely, relying instead on command-line switches.

- It is a bad idea to mix iostream calls and stdio
calls, such as getch(). This can often corrupt the
stream buffer and produce undesireable results. Once
the menu-driven interface is discarded, this will not
be an issue.

I am free to field any questions you may have.

- Greg Toombs

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com