Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 18 Jun 2013 03:03:39 +0200
From: Lukas Odzioba <lukas.odzioba@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Daniel's weekly report #1

2013/6/17 Dániel Bali <balijanosdaniel@...il.com>:
> Accomplishments:
> 1. Tried CodeXL on keccak-256's kernel which is a profiler for OpenCL
> applications

Please post your conclusions about that in sha3-opencl topic.

> 2. Worked on a more detailed and relevant timeline

As far as I know you spend near a day to setup your Linux development
environment, this is revelant and you should mention it.
I assume that this is finished by now.

> Priorities:
> 0. Adding a long description for my project on Melange. I really need to
> submit this soon.

Please finish it asap, It should be already done. We do not want to
spend more time on that.

> 1. Finishing the timeline for my project. I'm a bit stuck with this one.

Beacause planning this research project is painfull and possibly
inefficient I think that we should focus on tasks, sort them in time
and just do as much as you can each week.
Some of the tasks will have to be added ad hoc but since project will
be moving in a good direction this should not be a problem.
This is really challenging project and without a lot of work it will
be hard to achieve goals.
What stays placed in time is all gsoc important dates, status reports
and date of your absence.

> 2. Working on my first task, which is an ELF patching utility

I think that it should take max 2 days to make something usefull
enough for our initial purposes.
After that you should move to researching kernel structure, and
creating code able to convert isa asm to binary for a limited set of
ALU instructions.

Lukas

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.