freenode/#mezzano - IRC Chatlog
Search
12:46:34
froggey
housel: I think I've fixed all the ironclad failures. the latest sharplispers git builds without any issues and the testsuite passes almost all the tests
14:55:41
froggey
fixing timing side-channels proper should probably involve a compiler declaration to force it to generate code in a way that is side-channel free and to make sure that changes to the compiler don't break any hand-tuned code
18:57:23
fittestbits__
I looked through the ironclad code. Under #+unix, ironclad reads /dev/urandom. So we would want to implement something like /dev/urandom for mezzano.
18:58:23
fittestbits__
I'm not sure what that would take. On linux, it does use the entropy pool until it runs out, then uses a pseudo random number generator.
18:58:43
fittestbits__
I've never looked it to creating an entropy pool, so I have no idea what it takes.
19:08:38
froggey
there is a paper on how linux acquires and manages entropy, though I can't remember what it's called
20:53:58
fittestbits__
What's the command to upload a file to ix.io? I have a sample of a stream that I think does what you want.
20:55:47
fittestbits__
I just tried that and got "no results to fetch". So, no pointer to the file - maybe it failed?
20:59:08
fittestbits__
This is code for the "tag" file system I was playing around with on mezzano. The stream creates contains only a portion of the file - reads more when needed in the read case, writes portions in the write case as it needs more room in the buffer.
20:59:50
fittestbits__
Takes into account "seek" operations. I don't remember if it handles overwrite.
21:03:36
fittestbits__
Sure, but you have to handle the cases where only a portion of a sector is modified. So, for example, if you write just byte 0, you have to have read the at least a sector's worth of data
21:03:54
fittestbits__
so that when you writing it out, only the first byte of the sector gets overwritten.
21:06:57
fittestbits__
It's not, just another case that has to be handled everywhere. For example, when you seek (set position) you need to read enough around the new position so data that doesn't get overwritten