AFAIK wiping the drive does not remove their tracker unless you do a low-level BIOS format. Also if I remember correctly they had an option of having the tracker in the bios itself, so it was executing even before mbr is referenced. I talked to their CTO at some point and these guys were actually involved with IEEE and IETF to move forward some related standards. It is far more complex stuff than it seems from the first glance.
Almost everything boils down to a matter of syntax
In case of Windows it actually boils down to being ready for most bizzare sh*t you cant even imagine.
Like installing buggy USB driver f*cking up DHCP client's ability to renew IP address. Or installing desktop skinning software causing Windows to start failing installation of virtual network adapters. Or that disabling (certain) personal firewall software actually not having a full effect on a traffic until the next reboot.
Truly entertaining stuff. Far more lively than just mastering command syntax:)
Maybe someone will find it interesting and help... but most likely noone will. And the guy will blew his only chance to make good first impression (which he is wise enough to care about actually).
Common practice is to embed steel pins into side of the door (where the hinges are) so that they would enter the door frame when the door is closed. Removal of hinges' pins wont do much in this case as the door can be opened by swinging only.
Are you implying that Skupe lets you to communicate securely ? Last time I checked that claim that but offer no prove. Sorry, but closed-standard security should be treated as no security at all.. or you'll be in for a big surprise.
I have no idea what the strength of the language is, but I do know that Pascal is a Context Free Grammar language. That what gives it an incredible compilation speed, but it also automatically means that it has very basic semantics compared to other languages in general and to C in particular.
Not having integrity protection enabled automatically opens ESP to the replay attacks, which are easier to mount and far more practical than the one described in TFA.
Two types of 32bit binaries won't work in 64bit Windows -
* drivers * shell extensions
Don't know about latter, but it is trivial to rebuild former using x64 DDK. If the code is not a complete hack and has a grain of abstraction, then literally there's all there is to it - modify few header files and rebuild the sources.
Ethics is a subjective matter. I personally think what he did perhaps was legal, but not ethical. He is a person who is about to complicate kernel development process, because he decides to solve an non-critical problem in a highly contraversial manner.
Slightly offtopic, but I wish I could say that about their network stack.
NDIS is like a nightmare on steroids. Accompanying userspace API (IP helper, NetCfg, CM_xxx & co.) are not much prettier and far more buggier. Makes you really appreciate the simplicity of *nix networking.
a simple mod to the TCP/IP stack that alters the timestamp by some tiny, random amount
No, this won't help as it changes the dispersion of the skew samples, but the mean value (that's what they measure) stays the same.
What you need to do is to make your machine clock to appear run slower or faster to the external observer. You can do that by applying constant skew offset to your true clock gradually.
For example, say clock() returns true machine clock, then
uint my_clock() { return clock + clock()/1000; }
will make it appear to be running.1% faster. Then if at the moment c0 you decided to slow it down, my_clock should look like -
and it will make the clock slow down to 99.9% of the true frequency.
PS I guess it would still be possible to identify machines that skew their clock skew, but analyzing how they skew the skew, but I generously donate this idea to a post-grad community:)
Slashdot Mirror
AFAIK wiping the drive does not remove their tracker unless you do a low-level BIOS format. Also if I remember correctly they had an option of having the tracker in the bios itself, so it was executing even before mbr is referenced. I talked to their CTO at some point and these guys were actually involved with IEEE and IETF to move forward some related standards. It is far more complex stuff than it seems from the first glance.
Repeat after me - security architecture must be open in order to be secure.
Skype developers saying they use 32768 bit keys means absolutely zero if you cannot verify that.
Depends on the show, you know.
Almost everything boils down to a matter of syntax
:)
In case of Windows it actually boils down to being ready for most bizzare sh*t you cant even imagine.
Like installing buggy USB driver f*cking up DHCP client's ability to renew IP address. Or installing desktop skinning software causing Windows to start failing installation of virtual network adapters. Or that disabling (certain) personal firewall software actually not having a full effect on a traffic until the next reboot.
Truly entertaining stuff. Far more lively than just mastering command syntax
.. it should have plenty of Mars rocks spattered on the surface
...
Funny that they mentioned it...
Can anyone explain how can 'a plenty of rocks' leave Mars and land on its moon ?
Bonus question is to explain the appearance of 'martian meteorits' on Earth.
Somehow I have troubles imagining the level of volcanic activity required to catapult rocks to the neighbouring planets
Maybe someone will find it interesting and help. .. but most likely noone will. And the guy will blew his only chance to make good first impression (which he is wise enough to care about actually).
Common practice is to embed steel pins into side of the door (where the hinges are) so that they would enter the door frame when the door is closed. Removal of hinges' pins wont do much in this case as the door can be opened by swinging only.
It is really hard to open outwards-swining door with a mighty foot kick :)
.. do you really care about the anonymity of others to donate your bandwidth to the cause ?
Relay-based anonymous p2p won't take off the ground unless they include enforcable fairness provisions. Does anyone know such p2p frameworks ?
..communicate securely..
.. or you'll be in for a big surprise.
Are you implying that Skupe lets you to communicate securely ? Last time I checked that claim that but offer no prove. Sorry, but closed-standard security should be treated as no security at all
Let me spell it out for you -
R e a l - M e n - D o n t - U s e - P a s c a l
Well it's got the strength of C ..
I have no idea what the strength of the language is, but I do know that Pascal is a Context Free Grammar language. That what gives it an incredible compilation speed, but it also automatically means that it has very basic semantics compared to other languages in general and to C in particular.
Not having integrity protection enabled automatically opens ESP to the replay attacks, which are easier to mount and far more practical than the one described in TFA.
NAT traversal just adds another level of encapsulation and this 'vulnerability' applies to ESP itself.
> If this thing drives in reverse most of the time, wouldn't it be .. err .. 'rear wheels' ?
> more convenient to name front wheels
Or "the wheels formerly known as front"
Two types of 32bit binaries won't work in 64bit Windows -
* drivers
* shell extensions
Don't know about latter, but it is trivial to rebuild former using x64 DDK. If the code is not a complete hack and has a grain of abstraction, then literally there's all there is to it - modify few header files and rebuild the sources.
> WE GET IT
Next time try to speak for yourself.
What he did was perfectly ethical.
Ethics is a subjective matter. I personally think what he did perhaps was legal, but not ethical. He is a person who is about to complicate kernel development process, because he decides to solve an non-critical problem in a highly contraversial manner.
First choise make you a slave forever. Second makes you a partner.
But neither makes you wealthier, which was the point Mr. Schwartz was trying to make across.
The underlying NT is quite well-designed
Slightly offtopic, but I wish I could say that about
their network stack.
NDIS is like a nightmare on steroids. Accompanying
userspace API (IP helper, NetCfg, CM_xxx & co.) are
not much prettier and far more buggier. Makes you
really appreciate the simplicity of *nix networking.
No, this won't help as it changes the dispersion of the skew samples, but the mean value (that's what they measure) stays the same.
What you need to do is to make your machine clock to appear run slower or faster to the external observer. You can do that by applying constant skew offset to your true clock gradually.
For example, say clock() returns true machine clock, thenwill make it appear to be running
PS I guess it would still be possible to identify machines that skew their clock skew, but analyzing how they skew the skew, but I generously donate this idea to a post-grad community
It is a Novell server :)
It won't impact it much, because they always welcomed Other/Proprietary Licenses.