Security/Mentorships/MWoS/2014/Cross-platform memory scanning in Go: Difference between revisions

m
(Meeting notes from 2014-09-05)
Line 20: Line 20:


=== 2014-09-05 ===
=== 2014-09-05 ===
Agenda:
Summary of the week and Meeting:
    * Basic linux memory searcher and windows memory regions listing
* Basic linux memory searcher and windows memory regions listing
    ** We talked about the source code and different approaches in using C and handling errors.
** We talked about the source code and different approaches in using C and handling errors.
   
   
    * Double licensing: GCore uses GPL license so we would have to use both licenses if we want to use Gcore's source code.
* Double licensing: GCore uses GPL license so we would have to use both licenses if we want to use Gcore's source code.
    * Document the need for root access whenever is present: In Mac and windows there are many things that can be done without root access, but we will use root for ease of development and document those areas.
* Document the need for root access whenever is present: In Mac and windows there are many things that can be done without root access, but we will use root for ease of development and document those areas.
    * University's essay: start writing down notes
* University's essay: start writing down notes
    * Development in the open on github? Yes. Also discussions should be held in the open.
* Development in the open on github? Yes. Also discussions should be held in the open.
    * Memory maps can change, so the addresses may be invalid: For memory searching we won't stop the processes because it may take too long, just for core dumps if we need to.
* Memory maps can change, so the addresses may be invalid: For memory searching we won't stop the processes because it may take too long, just for core dumps if we need to.
    * Grep something more than the heap and the stack? Not for now.
* Grep something more than the heap and the stack? Not for now.
    * grep on go or C: figure out what's better, performance may or may not be an issue. go'd probably result in more robust code.
* grep on go or C: figure out what's better, performance may or may not be an issue. go'd probably result in more robust code.
    * #mwos has been created in mozilla's irc. That's the preferred channel to contact Julien through irc.
* #mwos has been created in mozilla's irc. That's the preferred channel to contact Julien through irc.
      
      
For Next Week:
For Next Week:
    * Pato has working code to read memory on MacOS
* Pato has working code to read memory on MacOS
    * looking at finishing the memory grepper next week
* looking at finishing the memory grepper next week
    * Julien to ask Mozilla's lawiers about double licensing
* Julien to ask Mozilla's lawiers about double licensing
    * test if reading invalid memory sections crashes the process in each os
* test if reading invalid memory sections crashes the process in each os


=== 2014-08-29 ===
=== 2014-08-29 ===
8

edits