« first day (757 days earlier)      last day (4115 days later) » 
00:00 - 22:0022:00 - 00:00

Gilles
Gilles
10:00 PM
@Iszi Hollywood exploit?
(I just made that up, but it fits)
 
Thomas Pornin
Thomas Pornin
@Iszi I told you, greek names are better.
 
Iszi
Iszi
Thereby:
The Arses are Great.
Great Arse, we praise you !
We fear the Great Arseholes.
The Glory of the Great Arse-eye is eternal.
We sacrifice our first-borns to the Great Arseholes.
In the Great Arsehole we trust.
 
Rory McCune
Rory McCune
@Iszi Parameter Tamplering/manipulation ? / Authorisation flaw?
 
Iszi
Iszi
@RoryMcCune See, I've been trying to say the former. Others are coming back with CSRF or XSS.
And I'm all like WTF?
 
Gilles
Gilles
@Iszi you, sir, are lucky that goatse.cx is not what it used to be and I can't be arsed to see where it's gone to
 
Thomas Pornin
Thomas Pornin
10:01 PM
@Iszi The Jesus Christ attack ("Ask and ye shall receive !")
3
 
Jeff Ferland
Jeff Ferland
I mean, basically if somebody has a URL that says, "page.html?admin=0" and you change it to 1, there's no name for that
 
Rory McCune
Rory McCune
@Iszi well it's not CSRF or XSS I'll tell you that much :)
 
Jeff Ferland
Jeff Ferland
That it's a hidden field in a POST doesn't doesn't give it a new name from... well, no name.
 
Iszi
Iszi
@RoryMcCune See, I know that...
@JeffFerland Yeah, that's pretty much what I'm trying to name.
 
Jeff Ferland
Jeff Ferland
@Iszi Well, get a bunch of followers on Twitter, make up a name, and see if it sticks.
 
Rory McCune
Rory McCune
10:03 PM
@Iszi when I write that flaw up (and I do, quite frequently) I'll either call it parameter tampering or an authorisation flaw or both :)
 
Jeff Ferland
Jeff Ferland
I'd call it client-side security failure
There we go. It's not the action we're naming, it's the flaw.
You used client-side security and let the client say what privileges it should have.
 
Iszi
Iszi
@JeffFerland The opening presumption is flawed in that statement.
 
Jeff Ferland
Jeff Ferland
@Iszi Just because you didn't intend to doesn't mean you didn't.
 
lynks
lynks
could someone explain these 3 instructions in english?
1: `mov %eax, (%ebx)`
2: `mov $0x03(%eax), %ebx`
3: `mov 0x03(%eax), %ebx`
 
Iszi
Iszi
@JeffFerland No, I mean it presumes any security consideration was in place at all.
Unless the statement is to imply (and I'm probably just being dense for not first realizing this) that "client-side security" != "security".
 
Scott Pack
Scott Pack
10:10 PM
@RoryMcCune %s/Authorisation/Authorization/ There, I fixed that for you.
 
Rory McCune
Rory McCune
@ScottPack %s/fixed/broke/ There, I fixed that for you :op
 
Scott Pack
Scott Pack
@RoryMcCune %s/McCune/Douchewaffle/ There, I fixed that for you.
 
Gilles
Gilles
@lynks 1: copy the value in the register eax to the address pointed to by ebx, I think
(I can't really read x86 assembly)
 
Rory McCune
Rory McCune
@ScottPack %s/*/Your Face/
 
Jeff Ferland
Jeff Ferland
@lynks Context would help, but EAX is the accumulator and EBX is the base. Moving the accumulator the base, so basically setting the start to the end.
I think
 
Scott Pack
Scott Pack
10:13 PM
@RoryMcCune I see you have a syntax error in your regex. I suggest you see to it.
 
lynks
lynks
@Gilles I'm mega confused, I've never need to understand assembly much, finding myself needing to read a whole bunch and really understand it.
also, im switching to intel syntax as it seems easier...
 
Gilles
Gilles
no, ebx has nothing to do with the stack
@lynks I prefer arm or mips
 
lynks
lynks
@Gilles guess i'll just have to stare at it for a few hours :P
 
Jeff Ferland
Jeff Ferland
Scratch that
@lynks Can you post the hex that goes with it?
I have an easier time with that :(
 
lynks
lynks
@JeffFerland those weren't consecutive instructions sorry, I was just trying to get my head around what each one did in turn.
 
Scott Pack
Scott Pack
10:20 PM
@JeffFerland 54:68:69:73:20:64:6f:65:73:6e:27:74:20:73:75:72:70:72:69:73:65:20:6d:65:20:61:74‌​:20:61:6c:6c:2e
 
Jeff Ferland
Jeff Ferland
@ScottPack 2c:21:2c:2c
X86 assembly language
x86 assembly language is a family of backward-compatible assembly languages, which provide some level of compatibility all the way back to the Intel 8008. x86 assembly languages are used to produce object code for the x86 class of processors, which includes Intel's Core series and AMD's Phenom and Phenom II series. Like all assembly languages, it uses short mnemonics to represent the fundamental instructions that the CPU in a computer can understand and follow. Compilers sometimes produce assembly code as an intermediate step when translating a high level program into machine code. Reg...
 
Scott Pack
Scott Pack
 
Gilles
Gilles
blowfish.smashthestack.org is back up, I'm looking at the first levels
I think I've found a way to level4, but it's not what they intend
I haven't actually tried it, but it's not blocked in the normal way
oh, scratch that, I'm an idiot
5
 
Jeff Ferland
Jeff Ferland
My hobby: getting supreme moderator super powers; waiting until the 4th vote to close has been cast before adding mine.
 
Gilles
Gilles
@JeffFerland sounds boring
I prefer to close questions first and answer on meta later
close questions first, shoot users later
 
lynks
lynks
10:51 PM
@Gilles thanks, (incedentally I'm working my way through blackbox.smashthestack.org, it is significantly more difficult than io., level 2 on blackbox is around the difficulty of level 6 on io)
 
Gilles
Gilles
@lynks I've looked at blowfish and io. Haven't looked at blackbox
 
Thomas Pornin
Thomas Pornin
11:15 PM
Second instruction is weird; it does not seem to conform to x86/AT&T syntax.
Instruction 1 is: write the 32-bit contents of %eax into RAM at the address contained in %ebx.
Instruction 3 is: read the 32-bit word at address %eax+3, into register %ebx.
 
00:00 - 22:0022:00 - 00:00

« first day (757 days earlier)      last day (4115 days later) »