I second this. I have Kopete set up with two Jabber accounts, two IRC networks, AIM, and SMS.
That's a lot of screen real estate. Even minimized, that would eat up a lot of space in the taskbar. Kopete takes up a 24x24 icon in KDE's systray, and however many chat windows I choose to have visible.
And let me just mention that Kopete's tabbed windows are great.
Re:War "Your Favorite Activity Here"
on
War Kayaking
·
· Score: 1
I used to use Qwest, before they got out of the ISP business and tried to get all their customers to use MSN.
A few months back, I happened to get a bounce on a message to that address. I'd forgotten to update an email notification on a web app I'd built some years back, and the mailbox was full of spam and couldn't accept the message from the webapp.
It's been... oh, 2? 2 1/2? years since I switched away from Qwest, and the email account is still active. I could probably dial in if they still have dialup access.
Like I said, I don't think it's a huge risk. But how's this scenario for you? One of your commonly-used apps (say, Mozilla, or Evolution) has a security hole which allows a malicious user to have it write - but not execute - files. It could put a malicious program in ~/bin, thereby compromising your entire account, and possibly springboarding to get root. Sure, it could just write to your.ssh/authorized_keys, but it could install a trojan 'su' or 'sudo' binary that would save the passwords entered, compromising other accounts, either of yours or others on the system.
If your account is compromised, a trojan or other malicious program could install, say, a keylogger and sniff your online banking password. Having your account completely compromised may not be the end of the world, but it may not be the end of the attack, either.
As for the ~ comment, you're right; what I meant to say was ~/bin. If you accidently open permissions on ~/bin, someone could trick you into running a malicious program, the implications of which have been outlined already.
The last comment has little to do with malicious intrusion - perhaps the site admin just doesn't want his users killing X with C-A-BS and has disabled it. The point is, X can be configured to allow apps to intercept that sequence, so you should not assume that pressing it means that you have a clean terminal.
"Huh? I can understand not putting . in your PATH-- icky nasty security issues abound-- but what's wrong with ~/bin?"
If your user account is compromised, you can be tricked into running a different program than you intend. Alternately, if you mess up the permissions on your ~, you can be made to run a different program, compromising the account.
While I don't think it's a huge risk, it's not exactly good practice, and should definitely be disabled in a corp. desktop/multiuser environment.
"I also would expect that it's a good idea to hit it before logging in, to make sure you're really looking at XDM. This is why you hit Ctrl-Alt-Delete to log into NT: apps can't intercept it."
If you disable it in your X config, apps can intercept it, so it's foolish to assume that you're looking at a genuine X/K/GDM after hitting it.
But it's ugly and unnecessary, really. If you're rolling out Linux desktops, you should be training users how to log out anyways.
So... that means that we should believe random people's unsubstantiated claims?
The fact here is that the statement on the JPEG patent is a single sentence quoted from someone with an obvious anti-patent bias. There is no transparency here, no explanation of why the patent is (or should be) invalid.
Call me crazy, but I'm not going to believe something like that - even if I do support the cause - without some justification.
Slashdot Mirror
True, but they are testing with "Mozilla 5."
Since Mozilla just hit 1.7, this webpage must have fallen backwards in time through a freak wormhole.
If you look in the comments, it also mentions something about IE developers being "the first up against the wall when the revolution came."
Yeah, it seems like IE is moving away from being a "Web browser," and rapidly becoming Windows Virus Update.
Remember to keep your malware up-to-date, kids.
Don't document anything. It's called job security, you fool!
I second this. I have Kopete set up with two Jabber accounts, two IRC networks, AIM, and SMS.
That's a lot of screen real estate. Even minimized, that would eat up a lot of space in the taskbar. Kopete takes up a 24x24 icon in KDE's systray, and however many chat windows I choose to have visible.
And let me just mention that Kopete's tabbed windows are great.
WarTrolling.
And don't forget Tripping the Rift.
If it's outgoing mail, it's a mail client.
I doubt that their TOS disallows one to use a mail client.
Yup. I just checked, and I can still dial in.
Handy.
I used to use Qwest, before they got out of the ISP business and tried to get all their customers to use MSN.
A few months back, I happened to get a bounce on a message to that address. I'd forgotten to update an email notification on a web app I'd built some years back, and the mailbox was full of spam and couldn't accept the message from the webapp.
It's been... oh, 2? 2 1/2? years since I switched away from Qwest, and the email account is still active. I could probably dial in if they still have dialup access.
No, really... In the days of 3ghz Pentium 4s, there really isn't much use for a 66mhz 486 in the western world.
Anyone who has a spare 486 is also likely to have a spare Pentium, P2, P3, Duron, or something with a bit more horsepower.
If you have a 486, donate it to someone who needs it, or get rid of it.
"It's not time for fucking in the streets yet..."
What the hell are you talking about? It's always time for fucking in the streets.
Yeah, the two negatives cancel themselves out, so it's akin to installing a virus on purpose.
Damn you, Peter Norton.
I believe the common term for this is a dead man's switch.
And what do you do if the person or persons controlling that military starts abusing their power in a violent way?
Yeah, though their pictures are pretty small. Some of the crash photos in a.b.p.grotesque are pretty decent, though.
"How do you keep a passenger car on the road at 250+ MPH?"
The answer for most people is: you don't.
Like I said, I don't think it's a huge risk. But how's this scenario for you? One of your commonly-used apps (say, Mozilla, or Evolution) has a security hole which allows a malicious user to have it write - but not execute - files. It could put a malicious program in ~/bin, thereby compromising your entire account, and possibly springboarding to get root. Sure, it could just write to your .ssh/authorized_keys, but it could install a trojan 'su' or 'sudo' binary that would save the passwords entered, compromising other accounts, either of yours or others on the system.
If your account is compromised, a trojan or other malicious program could install, say, a keylogger and sniff your online banking password. Having your account completely compromised may not be the end of the world, but it may not be the end of the attack, either.
As for the ~ comment, you're right; what I meant to say was ~/bin. If you accidently open permissions on ~/bin, someone could trick you into running a malicious program, the implications of which have been outlined already.
The last comment has little to do with malicious intrusion - perhaps the site admin just doesn't want his users killing X with C-A-BS and has disabled it. The point is, X can be configured to allow apps to intercept that sequence, so you should not assume that pressing it means that you have a clean terminal.
"Huh? I can understand not putting . in your PATH-- icky nasty security issues abound-- but what's wrong with ~/bin?"
If your user account is compromised, you can be tricked into running a different program than you intend. Alternately, if you mess up the permissions on your ~, you can be made to run a different program, compromising the account.
While I don't think it's a huge risk, it's not exactly good practice, and should definitely be disabled in a corp. desktop/multiuser environment.
"I also would expect that it's a good idea to hit it before logging in, to make sure you're really looking at XDM. This is why you hit Ctrl-Alt-Delete to log into NT: apps can't intercept it."
If you disable it in your X config, apps can intercept it, so it's foolish to assume that you're looking at a genuine X/K/GDM after hitting it.
But it's ugly and unnecessary, really. If you're rolling out Linux desktops, you should be training users how to log out anyways.
So... that means that we should believe random people's unsubstantiated claims?
The fact here is that the statement on the JPEG patent is a single sentence quoted from someone with an obvious anti-patent bias. There is no transparency here, no explanation of why the patent is (or should be) invalid.
Call me crazy, but I'm not going to believe something like that - even if I do support the cause - without some justification.
And if there's anyone in the patent lawyer field who's studied the issues and has a valid opinion on this issue, it's that BurnAllGIFS.org guy.
I mean, come on. 'BurnAllGIFS.' It practically reeks of professionalism and years of law school.
As an aside, I have this CD full of GIFs I burned, but nobody ever told me what I was supposed to do with them after I burned them. Anyone?
I've always wanted a 104 Connection reset by peer for my birthday!
KDE CVS gets tagged a week before the announcement is made, so you'll usually see Debian packages before the 'official' release.
Yes.
I think you mean "a fool and his money are soon parted."
Thank you, I was about to post something similar.
It's a long time to us puny humans, but it's the blink of an eye in the planetary timescale.