Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Framework build #4

Open
AldarHawk opened this issue May 11, 2012 · 5 comments
Open

Framework build #4

AldarHawk opened this issue May 11, 2012 · 5 comments

Comments

@AldarHawk
Copy link
Member

We need to work on the Systems Framework.
I think the language we should utilize is Ruby, as the documentation for it is good, and you can pick it up easy coming from PHP programming.
For the database we should utilize PostgreSQL because of the sheer speed and the likes.

We also should set a goal for the base system to be completed. I am thinking putting a target of June 22, 2012 as our target date to have the basic database schema built and the basic system framework built.

Please let me know all your thoughts and start pull requests on these issues so we can start building.

@0xRoM
Copy link
Contributor

0xRoM commented May 11, 2012

I don't know ruby, don't really have time to learn a new language, don't know the ins and outs of securing ruby applications, if I did know ruby I would be dev'ing for metasploit or BeeF

@richo
Copy link
Contributor

richo commented May 14, 2012

Ruby's pretty easy to pick up, honestly.

I took a job as a rails dev with no ruby (lots of python though) and was productive inside a month or so. Securing it boils down to "don't be retarded" for the most part, happily it dodges most of the shitful things in PHP that is full of pitfalls (apache escaping null bytes, your routing being bound to the filesystem, magic_quotes (urgh), templated SQL being considered a sane practice, inline templating for views, $_REQUEST etc....)

@samurai
Copy link

samurai commented May 31, 2012

I think I'm still in-line with nanoy's comments tho, I'd prefer to see this in PHP. That being said, if we decide to go ruby, I'll be fine with that as well, personally I'd just prefer to work with PHP.
I'll agree that some of PHP's "I'll let you do it however you want" model results in pitfalls, but with proper code I think that can be overcome. I'm also not sure I agree with some of the issues you listed as "why PHP sucks." :P

Postgres is win, so I'm +1 on that for sure

@baweaver
Copy link

Oh hey, old redux stuff. We ever going to touch this again? (Lemur)

@AldarHawk
Copy link
Member Author

Yeah this is old stuff. It fell to the side and nothing has or will come of it from what I know L

I have not touched HBH since Dan handed it to what’s his name...

From: Brandon Weaver [mailto:[email protected]]
Sent: January-12-15 3:02 AM
To: HBHRP/Redux
Subject: Re: [Redux] Framework build (#4)

Oh hey, old redux stuff. We ever going to touch this again? (Lemur)


Reply to this email directly or view it on GitHub #4 (comment) .Image removed by sender.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants