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

How about a closer collaboration? #90

Open
ltfish opened this issue Feb 2, 2019 · 5 comments
Open

How about a closer collaboration? #90

ltfish opened this issue Feb 2, 2019 · 5 comments

Comments

@ltfish
Copy link

ltfish commented Feb 2, 2019

I stumbled upon hase today when I was googling for an VEX IROp. This is a really cool project, and I like it (it actually killed one of my project ideas).

I wonder what the status of hase is, and what plan you have in mind for hase to move forward in the near future. We have some research projects that can really benefit from hase.

It seems that some angr updates broke hase in the past. One way to solve this problem gracefully is to add hase to angr CI, so we can make sure that new commits and PRs to master will not break hase (or at least, you will get a notification from us if we really have to break compatibility).

Also, it would be great if we can incorporate your "angr hacks" in your angr fork to angr master. Most of the code there looks legitimate to me.

Looking forward to your reply!

@Mic92
Copy link
Contributor

Mic92 commented Feb 5, 2019

I am sorry to say that I gave up on this project. There were too many problems I didn't know how to solve given the time constraint of my PhD. And also my motivation dropped in the process.

Feel free to use any code or data of this project or ask questions regarding the implementation. In particular the recording part should be quiet good, having only up to 1% overhead in the SPEC benchmark: https://github.com/hase-project/hase/blob/master/hase/pt.py

We also collected crash traces of a large corpus for a rather large corpus, that might be helpful: https://github.com/hase-project/bug-db
You can download the collected traces/coredumps using via the rsync protocol:

rsync -va thalheim.io::hase /tmp/hase

@ltfish
Copy link
Author

ltfish commented Feb 5, 2019

Thanks for replying! I think this is a great project, and I’m sorry to hear that you do not plan to continue it.

What license does hase use? There isn’t any license as far as I know.

@Mic92
Copy link
Contributor

Mic92 commented Feb 5, 2019

Good point. I actually added a license file to my project, but forgot to push it:

https://github.com/hase-project/hase/blob/master/LICENSE.md

Same license as angr to keep things simple.

@kasikci
Copy link

kasikci commented Feb 5, 2019

Hey Fish, I hope you are doing well. I hope we can collaborate on this. We are trying to see what kind of resources we can dedicate to this on our end, and we'll be in touch very soon.

@ltfish
Copy link
Author

ltfish commented Feb 5, 2019

I hope we can collaborate on this.

Yep! That'll be great. It would be awesome to know your plans for this project to move forward, as well as your research ideas. We should collaborate on both fronts.

@Mic92 Thanks for choosing BSD 2!

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

3 participants