Pedophiles of Sluthate AND Lookism (MRZ, Brian Peppers and many more!)

  • Thread starter Thread starter JU 199
  • Start date Start date

Which user is a bigger faggot?

  • @drz

  • Marijan Siklic

Results are only viewable after voting.
Ass Manager 3000 said:
HAHAHAHAHAHAHA

View attachment 39908
Click to expand...
I know I abuse these gifs but goddammit the idea of someone legit freaking out over a wrinkle underneath their eyebrow has made me lose it so hard that a worded reaction isn't enough
tumblr_mwltw5mkml1s8akkwo4_250.gif
 
  • Winner
Reactions: Sanae Kochiya and (deleted member)
reallyitisnotme said:
People typically say that IQ isn't a measure of intelligence because black people do so poorly on IQ tests. It's liberal propaganda.
Click to expand...


That's it? That's your response? You have failed at applying your own "theory of reality".
 
Frank Rizzo said:
Indeed, with the whole Mrz "Fail Hack, Dog sucked him off" fest that's been going on, we forgot about ole Peppers for awhile.
Click to expand...

I'm still working on implementing a timing attack, it's more complicated than I originally thought but I will stick with it. Primarily it is complicated because so many things are getting in the way of accurate/precise timing measurements. I found an academic paper that discusses the implementation of accurate enough clocks to do this sort of attack though, and now I'm making frequent reference to it in furtherance of implementing my own, which will help a lot. It's already helped, because at first I was using a nanotime function to get nanoseconds elapsed, but then I started reading this paper and learned that I should be getting CPU cycles with assembly + rdtsc instead, and then I found out how to do that.

//Using this for time as it is more accurate than the clock function I was using before
//as I learned in Opportunities and Limits of Remote Timing Attacks SCOTT A. CROSBY, DAN S. WALLACH and //RUDOLF H. RIEDI Rice University
__inline__ unsigned long long getCpuCycle(void)
{
unsigned long long int x;
__asm__ volatile (".byte 0x0f, 0x31" : "=A" (x));
return x;
}

I plan to stick it through though. So far I can't even predict an unknown string in a C program itself though, I need to get around some problems I'm running into, mainly interference in timing measurements from optimizations and cache in particular (cache makes earlier timing measurements more latent than subsequent ones). So far in a C program itself, with no jitter from the network or anything, this is my best timing differential attempt

guess for ""qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq" is "qqqqqqqqqqqqqqqqqqqqqqqbdrtdivx"

Once I get it accurately guessing the string in the C program itself I will work on increasing the precision by following this paper which explains the best way to go about it, I know I will need to disable cache and various other things that are introducing noise. Then I will add networking code to it and have it spoof cookies. It's turned out to be significantly more of a challenge than I thought it would be at first, but I'm confident I can do it, particularly since I started reading that paper that discusses the topic.
 
Last edited:
  • Dumb
Reactions: Simplicity111
Igivedogswoofies said:
I'm still working on implementing a timing attack, it's more complicated than I originally thought but I will stick with it. Primarily it is complicated because so many things are getting in the way of accurate/precise timing measurements. I found an academic paper that discusses the implementation of accurate enough clocks to do this sort of attack though, and now I'm making frequent reference to it in furtherance of implementing my own, which will help a lot. It's already helped, because at first I was using a microtime function to get microseconds elapsed, but then I started reading this paper and learned that I should be counting CPU cycles with assembly instead, and then I found out how to do that.

//Using this for time as it is more accurate than the clock function I was using before
//as I learned in Opportunities and Limits of Remote Timing Attacks SCOTT A. CROSBY, DAN S. WALLACH and //RUDOLF H. RIEDI Rice University
__inline__ unsigned long long getCpuCycle(void)
{
unsigned long long int x;
__asm__ volatile (".byte 0x0f, 0x31" : "=A" (x));
return x;
}

I plan to stick it through though. So far I can't even predict an unknown string in a C program itself though, I need to get around some problems I'm running into, mainly interference in timing measurements from optimizations and cache in particular (cache makes earlier timing measurements more latent than subsequent ones). So far in a C program itself, with no jitter from the network or anything, this is my best timing differential attempt

guess for ""qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq" is "qqqqqqqqqqqqqqqqqqqqqqqbdrtdivx"

Once I get it accurately guessing the string in the C program itself I will work on increasing the precision by following this paper which explains the best way to go about it, I know I will need to disable cache and various other things that are introducing noise. Then I will add networking code to it and have it spoof cookies. It's turned out to be significantly more of a challenge than I thought it would be at first, but I'm confident I can do it, particularly since I started reading that paper that discusses the topic.
Click to expand...


why are you running away you faggot
also you can't computer for shit
 
  • Winner
Reactions: Sanae Kochiya
Igivedogswoofies said:
I'm still working on implementing a timing attack, it's more complicated than I originally thought but I will stick with it. Primarily it is complicated because so many things are getting in the way of accurate/precise timing measurements. I found an academic paper that discusses the implementation of accurate enough clocks to do this sort of attack though, and now I'm making frequent reference to it in furtherance of implementing my own, which will help a lot. It's already helped, because at first I was using a microtime function to get microseconds elapsed, but then I started reading this paper and learned that I should be getting CPU cycles with assembly rdtsc instead, and then I found out how to do that.

//Using this for time as it is more accurate than the clock function I was using before
//as I learned in Opportunities and Limits of Remote Timing Attacks SCOTT A. CROSBY, DAN S. WALLACH and //RUDOLF H. RIEDI Rice University
__inline__ unsigned long long getCpuCycle(void)
{
unsigned long long int x;
__asm__ volatile (".byte 0x0f, 0x31" : "=A" (x));
return x;
}

I plan to stick it through though. So far I can't even predict an unknown string in a C program itself though, I need to get around some problems I'm running into, mainly interference in timing measurements from optimizations and cache in particular (cache makes earlier timing measurements more latent than subsequent ones). So far in a C program itself, with no jitter from the network or anything, this is my best timing differential attempt

guess for ""qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq" is "qqqqqqqqqqqqqqqqqqqqqqqbdrtdivx"

Once I get it accurately guessing the string in the C program itself I will work on increasing the precision by following this paper which explains the best way to go about it, I know I will need to disable cache and various other things that are introducing noise. Then I will add networking code to it and have it spoof cookies. It's turned out to be significantly more of a challenge than I thought it would be at first, but I'm confident I can do it, particularly since I started reading that paper that discusses the topic.
Click to expand...

I think you may have autism of the soul...
 
  • Agree
Reactions: Rin
cat said:
why are you running away you faggot
also you can't computer for shit
Click to expand...

This is definitely taking me to a lower level than I've gone before, for example it required assembly to get the most precise timer measurements, and it's likely going to require assembly again + writing a kernel module to be able to disable cache. In the past I've not gone lower level than C, and didn't need to directly interact with more than RAM.
 
  • Dumb
Reactions: Simplicity111, Dynamite Ninja and Rin
Igivedogswoofies said:
This is definitely taking me to a lower level than I've gone before, for example it required assembly to get the most precise timer measurements, and it's likely going to require assembly again + writing a kernel module to be able to disable cache. In the past I've not gone lower level than C, and didn't need to directly interact with more than RAM.
Click to expand...


lower level than your retart iq? lol you can't get dumber
 
Igivedogswoofies said:
Actually I corrected my first post on this topic, I said I was using a microtime function, but I was actually using a nanotime function, but now I'm counting CPU cycles with assembly, which according to the paper I'm reading is the most precise way to measure time.
Click to expand...


lol you're just a scared faggot afraid of actual conversation
 
Igivedogswoofies said:
Actually I corrected my first post on this topic, I said I was using a microtime function, but I was actually using a nanotime function, but now I'm counting CPU cycles with assembly, which according to the paper I'm reading is the most precise way to measure time.
Click to expand...
Dear sweet god get a life dude.
 
Remember, if MRZ went outside to get a starbucks he would never find it. :lol:
 
we need to have odds for each mrz visit.
what will his reply be?
1. jbjbjbjbjbjbjbjbjbjbjbjbjbjbjb
2. beepboop i am an autistic hackin robot
3. fucks off like a coward
 
  • Agree
Reactions: Rin
cat said:
when u hackin the forums when should we be scurred. you have a low iq. is it tru u can't hack the forums bc your a dipshit?
Click to expand...

Well I'm still developing the timing measurement code and everything, I admit it's more complicated than I originally thought it would be, but I'm sure I can do it eventually. I'm not sure if it will actually work against the forum, but theoretically I believe it should, though in any case I'm just doing this for fun and practice and such. One of the big problems I'm running into right now is cache distorting the timing measurements, and it looks like this will require me to write a kernel module in assembly to set a value in a register of the CPU to disable the cache. I also need to finish reading this paper, but as I mentioned it already has assisted me, as now rather than using a nanotime function I'm counting CPU cycles. I probably wouldn't have been able to do it entirely myself without the assistance of a paper, as I originally set out to do, but once I have a paper I can typically implement the system it describes.
 
  • Dumb
Reactions: Simplicity111, Dynamite Ninja, Rin and 1 other person
iscrewedthepooch said:
Well I'm still developing the timing measurement code and everything, I admit it's more complicated than I originally thought it would be, but I'm sure I can do it eventually. I'm not sure if it will actually work against the forum, but theoretically I believe it should, though in any case I'm just doing this for fun and practice and such. One of the big problems I'm running into right now is cache distorting the timing measurements, and it looks like this will require me to write a kernel module in assembly to set a value in a register of the CPU to disable to cache. I also need to finish reading this paper, but as I mentioned it already has assisted me, as now rather than using a nanotime function I'm counting CPU cycles.
Click to expand...


lol so no you can't hack the forums jesus ur stupid
 
  • Agree
Reactions: Rin
You must log in or register to reply here.
Back