Infidelled: Owasp Orizon and I am sad from it
Latest Job Opportunities in India
Discover top job listings and career opportunities across India. Stay updated with the latest openings in IT, government, and more.
Check Out Jobs!Read More
✨ Infidelled: Owasp Orizon and I am sad from it
uncovered
In 2006, it started an ambitious project, an OpenSORCE SAST engine that was built in Java I Owasp Orizon.
Of course, the name was intended to be Horizon But I made a mistake in the word and found ridiculous to cover my lexical mistake.
After 3 years without no new symbol, I think the project can be considered closed, and also if some people are interested in it.
Yesterday and I found two email messages about Owasp Orizon in my country
Owasp.org account. In a first email, an American man asked how he could help me improve the tool and in a second email from a young man from the Asian region, which he asked about Milk Java’s interface for Orizon was written in 2006.
It is true that the saying is that the milk is deserted more than Oreson. When I answered the latter, he must use Orizon instead, he said that even this seems to have not been updated since 2009.
The truth is that I no longer have a new energy to put it in this project anymore. I have turned my software interests from Java to Ruby and I am working on it
in order to Now that it has become a mixed safety test tool and the application start -up engine,
Symbols.
Concept
The first idea I was thinking when I designed Owasp Orizon was the translation of the source code as part of a safety review in the representation of XML intermediate and safety checks on it.
If you make the safety engine build XML, support a new programming language is just writing a translator to this XML representation. Of course, you will add some checking of the specified safety to the base of knowledge.
This approach is logical to me until today, but it does not work (or at least I could not implement it in a way of working).
Translation from different languages to building one XML sentence makes a lot of linguistic expression strength for its loss.
Java has a very complex sub -classification mechanism. There are facades that can be used to design a common API interface for example, there are abstract categories, and there is a common hierarchical sequence system that the category can extend one or more category.
Ruby has a completely different approach to the form. The common Twos translation in XML will read the XML knot full of options, features, etc.
Support
In 2008 we were married and Owis Orizon had one of his most abundant moments. I had the opportunity to travel in New York City for Owasp Appsec 2008 to tell the world about the code that I was writing.
The feedback was good and I had two jobs today and I was sorry that I refused.
Fall
But in 2009, I received some harsh emails from a man who contributes to the project, saying that I was unable to listen and attract people.
Many people, from Italy I had to be honest, they came here and say “I want help” and after some mail they disappeared. In the end, I discovered that they used Owasp Orizon as self -reinforcement during preparations for consultations.
I lost motivation and energy. The code was ugly and the writing of Antlr analyst instead of translating XML was really difficult. We eventually moved to Freecc, but this does not last.
Owasp Orizon Source Code is no longer updated and you can imagine the entire story.
Something you learned
Being part of the Owasp Orizon project was inspiring and learned a lot in terms of coding it in society.
I traveled a lot and started to meet the public sermons.
I enjoyed being part of Owasp.
But it’s time to go forward. It’s time to improve and become larger and larger.
Enjoy it!
A winter sea horizon image is by I
📌 Read more at: Full Article
Tags: #Infidelled #Owasp #Orizon #sad
Authored by Paolo Perego on 2012-11-20 12:24:00
Via armoredcode.com – the application security blog that gets the job done
✨ Infidelled: Owasp Orizon and I am sad from it
explained
In 2006, it started an ambitious project, an OpenSORCE SAST engine that was built in Java I Owasp Orizon.
Of course, the name was intended to be Horizon But I made a mistake in the word and found ridiculous to cover my lexical mistake.
After 3 years without no new symbol, I think the project can be considered closed, and also if some people are interested in it.
Yesterday and I found two email messages about Owasp Orizon in my country
Owasp.org account. In a first email, an American man asked how he could help me improve the tool and in a second email from a young man from the Asian region, which he asked about Milk Java’s interface for Orizon was written in 2006.
It is true that the saying is that the milk is deserted more than Oreson. When I answered the latter, he must use Orizon instead, he said that even this seems to have not been updated since 2009.
The truth is that I no longer have a new energy to put it in this project anymore. I have turned my software interests from Java to Ruby and I am working on it
in order to Now that it has become a mixed safety test tool and the application start -up engine,
Symbols.
Concept
The first idea I was thinking when I designed Owasp Orizon was the translation of the source code as part of a safety review in the representation of XML intermediate and safety checks on it.
If you make the safety engine build XML, support a new programming language is just writing a translator to this XML representation. Of course, you will add some checking of the specified safety to the base of knowledge.
This approach is logical to me until today, but it does not work (or at least I could not implement it in a way of working).
Translation from different languages to building one XML sentence makes a lot of linguistic expression strength for its loss.
Java has a very complex sub -classification mechanism. There are facades that can be used to design a common API interface for example, there are abstract categories, and there is a common hierarchical sequence system that the category can extend one or more category.
Ruby has a completely different approach to the form. The common Twos translation in XML will read the XML knot full of options, features, etc.
Support
In 2008 we were married and Owis Orizon had one of his most abundant moments. I had the opportunity to travel in New York City for Owasp Appsec 2008 to tell the world about the code that I was writing.
The feedback was good and I had two jobs today and I was sorry that I refused.
Fall
But in 2009, I received some harsh emails from a man who contributes to the project, saying that I was unable to listen and attract people.
Many people, from Italy I had to be honest, they came here and say “I want help” and after some mail they disappeared. In the end, I discovered that they used Owasp Orizon as self -reinforcement during preparations for consultations.
I lost motivation and energy. The code was ugly and the writing of Antlr analyst instead of translating XML was really difficult. We eventually moved to Freecc, but this does not last.
Owasp Orizon Source Code is no longer updated and you can imagine the entire story.
Something you learned
Being part of the Owasp Orizon project was inspiring and learned a lot in terms of coding it in society.
I traveled a lot and started to meet the public sermons.
I enjoyed being part of Owasp.
But it’s time to go forward. It’s time to improve and become larger and larger.
Enjoy it!
A winter sea horizon image is by I
🔗 Read more at: Source
Explore more: #Infidelled #Owasp #Orizon #sad
📰 Published by Paolo Perego on 2012-11-20 12:24:00
From: armoredcode.com – the application security blog that gets the job done