NVidia's Detonator drivers for Geforce graphics cards has an extension called nView that adds a submenu to each window (right click on title bar). From there you can toggle always-on-top, transparency, appearantly send it to other desktops (I don't use multiple desktops).
Granted, it's tied to a specific driver and thus to a specific hardware manufacturer, but still..
'Network users have a back door to your hard drive while you're online, thereby seeing your personal, private information, such as bank records, social security number, etc.'
they can also get this information even if you don't have it stored anywhere on your computer! I tell you, those nasty cr^Whackers can do anything!
This goes along the same line as morons telling you anyone can "enter" your system as soon as a port is open, i.e. an application is waiting for connections on it. No mention of the need for an exploitable bug in that application.
Was this commentary really necessary? This software looks like neat stuff, [...]
From parent:
by ADOT Troll (687975) on 2003-07-28 11:20 (#6549294)
Was this commentary in the article really necessary? This software looks like neat stuff, [...]
The post I replied to probably has disappeared below your threshold. No problem, I have made some quick shots myself just to see I was wrong after that.
But the AC is right./file/..uid is not ascending out of/file/. The name of the metadata file is simply..uid. Files can start with dots, not to be confused by the files whose whole name is '.' and '..' respectively. But you know this, right? One might get the idea you don't.
Backwards out of it again would be/directory/../owner and be indistinguishable from/owner. In this case we simply have a file named..owner inside a directory named/directory.
Because it's the nature of the web to not differentiate by user agents or the way they access your free (it's http on port 80, you get no 403 or otherwise, so it's free. "Content" providers and your fucked up ideas bite my ass) information? I find it logical to make it an extra step to prevent automatic crawlers from automatic crawling.
I was thinking more along the lines of a proxy that sits between the X apps and the X server. With VNC, as I understand it, you attach to an already running X session. The analogy would be to attach to a local terminal (ttyv0 in FreeBSD for example). That's not how screen works.
If the X server crashes all your graphical apps lose their connection and get killed. With screen(1), if your connection gets killed all your apps keep running happily.
Unless I missed something I don't think it's possible to tear down the X server on one machine, keep the whole session running and then start another X server on a second machine and reattach to the session, is it?
1. start X 2. start dozens of terminals/browsers 2. detach the whole thing while leaving everything running 3. attach it again at a later time, maybe on another box
Just like screen(1) does now for text terminals. And come on, who can live without screen(1)?
Minor nitpick, but his name is Karl-Heinz Brandenburg. It's composed of two names that can also be used separately. You don't usually write it as Karlheinz.
Slashdot Mirror
Bad day. Move along PLZ K THX.
Where's the "test, test, test" part?
If you just want to block that port to the internet (as oppose to ethernet) [...]
Ethernet knows about ports? Since when? Why can't my internet run over ethernet (with PPPoE it actually does)?
Don't use those funky tech buzzwords if you don't know what they mean.
no real-life but real goods.
Just do a 'make package'. This will install the port and create a binary package which you can install with pkg_add(1) on other boxes.
Poor naive AC. Read about Safedisc, SecuROM, ProtectCD, Starforce and what not, then try again.
Solution.
Solution: possess anyway and don't tell
Mod parent funny you insensitive clods!
You have more problems than you realise.
Remember, this is /.
:(
I don't reach 16 myself, though
NVidia's Detonator drivers for Geforce graphics cards has an extension called nView that adds a submenu to each window (right click on title bar). From there you can toggle always-on-top, transparency, appearantly send it to other desktops (I don't use multiple desktops).
Granted, it's tied to a specific driver and thus to a specific hardware manufacturer, but still..
do
'Network users have a back door to your hard drive while you're online, thereby seeing your personal, private information, such as bank records, social security number, etc.'
they can also get this information even if you don't have it stored anywhere on your computer! I tell you, those nasty cr^Whackers can do anything!
This goes along the same line as morons telling you anyone can "enter" your system as soon as a port is open, i.e. an application is waiting for connections on it. No mention of the need for an exploitable bug in that application.
What a load of crap FUD.
Except that I wasn't replying to the PIS comment.
From my link:
by Osty (16825) on 2003-07-28 11:17 (#6549290)
[...]
Was this commentary really necessary? This software looks like neat stuff, [...]
From parent:
by ADOT Troll (687975) on 2003-07-28 11:20 (#6549294)
Was this commentary in the article really necessary? This software looks like neat stuff, [...]
The post I replied to probably has disappeared below your threshold. No problem, I have made some quick shots myself just to see I was wrong after that.
plagiarism is hardly insightful.
A 2TB partition made of exactly 8 250G disks and you don't see the problem? ..
But the AC is right. /file/..uid is not ascending out of /file/. The name of the metadata file is simply ..uid. Files can start with dots, not to be confused by the files whose whole name is '.' and '..' respectively. But you know this, right? One might get the idea you don't.
Backwards out of it again would be /directory/../owner and be indistinguishable from /owner. In this case we simply have a file named ..owner inside a directory named /directory.
ed2k://|file|Aphex.Twin,.The.-.Drukqs.tar|55257088 0|BAC185B1D8B5C22B252F11A7D00A2A1E|/
:(
Haven't gotten around to ripping the other ones yet. No disk space
(Score: -1, True)
Because it's the nature of the web to not differentiate by user agents or the way they access your free (it's http on port 80, you get no 403 or otherwise, so it's free. "Content" providers and your fucked up ideas bite my ass) information? I find it logical to make it an extra step to prevent automatic crawlers from automatic crawling.
I was thinking more along the lines of a proxy that sits between the X apps and the X server. With VNC, as I understand it, you attach to an already running X session. The analogy would be to attach to a local terminal (ttyv0 in FreeBSD for example). That's not how screen works.
If the X server crashes all your graphical apps lose their connection and get killed. With screen(1), if your connection gets killed all your apps keep running happily.
Unless I missed something I don't think it's possible to tear down the X server on one machine, keep the whole session running and then start another X server on a second machine and reattach to the session, is it?
Now that would be cool.
1. start X
2. start dozens of terminals/browsers
2. detach the whole thing while leaving everything running
3. attach it again at a later time, maybe on another box
Just like screen(1) does now for text terminals. And come on, who can live without screen(1)?
Minor nitpick, but his name is Karl-Heinz Brandenburg. It's composed of two names that can also be used separately. You don't usually write it as Karlheinz.
I don't think that's always the case! :)