I'm not sure it's practical to take into account all the expected sources, but a far advanced civilization may be able to communicate by converting energy to mass and back to create a gravitational signal that presumably travels faster than light.
I don't think that makes sense... If they're leaving resi's at IPv4, to speak seemlessly with IPv6 servers would mean NAT that doctors DNS in both directions at least.
Been waiting to see mention of this without having to read up on nosql yet =) it seems there could be a db engine that provides sql features backed by nosql data stores when things mature there.
My opinion is the best bang-for-the-buck would be to integrate RAM into the CPU. Perhaps a decent GPU with lightweight CPU added in would make sense if netbook continues as a separate niche, but again it might be better to put the RAM in as well. Between allowing multiple memory paths (no longer restricted by pins on the chip as much) and presumably lower power required to access the bits, it seems like a reasonable path to take. Imagine if the RAM were fast enough that little cache were needed on the CPU for added benefit.
The one idea I've not seen talked about that seems like it'd help magnetic disks is to just store the first megabyte or so in cache, so that the disk can seek to the next part of a file and read at whatever expected transfer speed. In other words, cache away the seek time and live with the transfer. It seems like a nice match for an SSD cache if the goal is to pretend you have a huge SSD storage but can't afford it. It'd stretch the cache across a whole lot more files, so that almost all files could appear to live in cache. Well, if the number turned out to be as high as 1 MB than I guess 16000 files could live in it, not accounting for smaller libraries that could fully fit within it.
I can't find it now (can't remember the name used) but I had referenced a webpage for an online authen system awhile back that "solved" that problem nicely. I'm probably going to mess up a step by rushing but it went something like this:
1. Server sends tokenA and tokenB to client
2. Client returns hmac(password, tokenA), and hash(hmac(password, tokenB).
3. Server verifies hash of the first part matches what is stored, and stores the second part for next time.
So the hash on the server changes everytime the login is successful, without changing the password, and it doesn't inconvience users. Also there's nice javascript libraries for things like md5/sha that do not take noticeable time on any client I've tried.
I get an order of magnitude more attempts to deliver spam from msn/hotmail servers than anywhere else, so, no, they haven't "solved" it in their own system yet. My spamtrap addresses get hit so frequently from their servers I had to whitelist their address space.
[Tue Nov 8 19:14:47 2005] [error] [client 154.37.34.90] client denied by server configuration:/htdocs/awstats
[Tue Nov 8 19:14:48 2005] [error] [client 154.37.34.90] client denied by server configuration:/htdocs/cgi-bin ...
[Tue Nov 8 19:14:53 2005] [error] [client 154.37.34.90] client denied by server configuration:/htdocs/blogs
[Tue Nov 8 19:14:54 2005] [error] [client 154.37.34.90] client denied by server configuration:/htdocs/drupal
[Tue Nov 8 19:14:55 2005] [error] [client 154.37.34.90] client denied by server configuration:/htdocs/phpgroupware
Of course, since code red came out, even though I was not running IIS nor Windows, I decided to disallow any requests sent to the IP of the server itself, IOW, only requests to a hostname that is setup as a VirtualHost are allowed.
I looked into PV panels for the roof of my home, which is not large, and does not use electric heat. $80k to provide for my electricity requirements. I was hoping it would be 1/5 that, as loan repayments would be reasonable if I had a zero electric bill in summer and a small bill in winter. Unless the quote I had gotten was way off, it doesn't seem feasible in the short-term.
The flip-side to that, is that I live in a 30 year old home. From what I understand, new construction can be had that will greatly reduce heating and cooling costs while increasing the price of the home by small (around 10%) amount, via passive solar heating and natural cooling.
Of course encryption serves a different purpose, note I didn't say this is exactly what you want. But if you're worried someone will recover data from the disk after it's deleted, what about the same data before it's deleted?
Apparently I misunderstood why you want this daemon, and wrongly assumed the threat of recovery you're considering.
An encrypted filesystem will get you most of what you want. It'll require overhead for every file, not just deleted ones, can't push that overhead to the background, and could make recovery of the files you didn't delete more difficult (although this is a feature =)
If you use things like PGP, look into encrypted swap anyway, and set/proc/sys/vm/swappiness to 5 to make it less painful as linux loves to swap
Considering how really quick it was when I ran it years ago on a 400Mhz laptop, I would say this would be useful in set-top boxes, DVR and email checking, that sort of thing, on fairly low power processors.
Of course, that doesn't mean anyone will use it for that purpose, just seems like a natural fit for what was designed as a multimedia OS IIRC.
In 2003, two vulnerabilities were discovered in mpg123 that could result in remote code execution when using untrusted input or streaming from an untrusted server.
Just one implementation's example, it's been quite some time since anybody could say that documents in general are harmless.
There are a couple of useful replies here already, but I'll throw this out as well.
I had roughly the same problem a few minor versions back, I did the feedback agent thing, now I don't have the problem anymore since two things changed.
One is that I upgraded, so that likely corrected a few cases (where it crashed on one of the first few pages after starting firefox), but the other is what I suspect has made it more stable overall: setting limits on memory usage.
in about:config the main one that jumps out for me is browser.cache.memory.capacity, I set it to 16000. Another sanity check: browser.cache.disk.capacity, I have no idea why these aren't accessible in the preferences.
My question about this is whether you could get anything odne in this kind of environment as a developer.
I read the article to imply that someone should be responsible for knowing what things are needed and allow just those things. A developer would need to use a compiler, while billing staff probably doesn't. And while it's not specifically spelled out, I would assume development stations need not be sitting on an unrestricted network in the first place.
Exactly right, I think the time for light to travel all the way around the earth is 1/7 of a second. So, a terminal half-way around the world will have that as a (theoretical/best) round trip time...for each packet. Yea you'd never notice that while watching streaming video, but I wouldn't want my desktop response times in that range.
By way of example, without echo cancellation, a phone call from NY to LA could be annoying.
The individual software's not so much of problem... It's more about the dependencies...
How so? Why should it matter whether a package happens to be compiled locally or centrally? Seriously, aren't the dependancies exactly the same for a given app?
I've seen a few suggestions in the thread about using the AllowUsers option in sshd_config. I'll throw in my opinion that using AllowGroups is easier to maintain. For example, have 2 groups, one for human users and one for automated scripts. Then the ssh config doesn't need to be updated whenever a user is added or deleted.
I've never used Pegasus, but I'd say the same thing about Kmail, versus Thunderbird.
Part of my antispam approach is the tried-and-true method of using unique email addresses for every site/company/whatever. It doesn't make sense to have to go into the account settings and setup a new address every time, just make the From field editable =)
Isn't there a rule for iptables to redirect traffic coming into one IP, into another one? a one-liner, if I remember right.
Really though, if this worked at your location, you'd be able to spoof the packets without Lycos or anybody sending the traffic to you in the first place, no?
Slashdot Mirror
I'm not sure it's practical to take into account all the expected sources, but a far advanced civilization may be able to communicate by converting energy to mass and back to create a gravitational signal that presumably travels faster than light.
I don't think that makes sense... If they're leaving resi's at IPv4, to speak seemlessly with IPv6 servers would mean NAT that doctors DNS in both directions at least.
Been waiting to see mention of this without having to read up on nosql yet =) it seems there could be a db engine that provides sql features backed by nosql data stores when things mature there.
My opinion is the best bang-for-the-buck would be to integrate RAM into the CPU. Perhaps a decent GPU with lightweight CPU added in would make sense if netbook continues as a separate niche, but again it might be better to put the RAM in as well. Between allowing multiple memory paths (no longer restricted by pins on the chip as much) and presumably lower power required to access the bits, it seems like a reasonable path to take. Imagine if the RAM were fast enough that little cache were needed on the CPU for added benefit.
The one idea I've not seen talked about that seems like it'd help magnetic disks is to just store the first megabyte or so in cache, so that the disk can seek to the next part of a file and read at whatever expected transfer speed. In other words, cache away the seek time and live with the transfer. It seems like a nice match for an SSD cache if the goal is to pretend you have a huge SSD storage but can't afford it. It'd stretch the cache across a whole lot more files, so that almost all files could appear to live in cache. Well, if the number turned out to be as high as 1 MB than I guess 16000 files could live in it, not accounting for smaller libraries that could fully fit within it.
I can't find it now (can't remember the name used) but I had referenced a webpage for an online authen system awhile back that "solved" that problem nicely. I'm probably going to mess up a step by rushing but it went something like this:
So the hash on the server changes everytime the login is successful, without changing the password, and it doesn't inconvience users. Also there's nice javascript libraries for things like md5/sha that do not take noticeable time on any client I've tried.
Almost sounds like any app launcher could be a door and the exit widget a back door.
wish I could mod that up
That's along the lines of what I assumed, but didn't see it in the article and it wasn't clear in the paragraph quoted. Thanks!
So what is it about tracking unique contexts via cookie that is less prone to abuse than tracking half-open connections on the server?
I get an order of magnitude more attempts to deliver spam from msn/hotmail servers than anywhere else, so, no, they haven't "solved" it in their own system yet. My spamtrap addresses get hit so frequently from their servers I had to whitelist their address space.
[Tue Nov 8 19:14:47 2005] [error] [client 154.37.34.90] client denied by server configuration:
[Tue Nov 8 19:14:48 2005] [error] [client 154.37.34.90] client denied by server configuration:
[Tue Nov 8 19:14:53 2005] [error] [client 154.37.34.90] client denied by server configuration:
[Tue Nov 8 19:14:54 2005] [error] [client 154.37.34.90] client denied by server configuration:
[Tue Nov 8 19:14:55 2005] [error] [client 154.37.34.90] client denied by server configuration:
Of course, since code red came out, even though I was not running IIS nor Windows, I decided to disallow any requests sent to the IP of the server itself, IOW, only requests to a hostname that is setup as a VirtualHost are allowed.
I looked into PV panels for the roof of my home, which is not large, and does not use electric heat. $80k to provide for my electricity requirements. I was hoping it would be 1/5 that, as loan repayments would be reasonable if I had a zero electric bill in summer and a small bill in winter. Unless the quote I had gotten was way off, it doesn't seem feasible in the short-term.
The flip-side to that, is that I live in a 30 year old home. From what I understand, new construction can be had that will greatly reduce heating and cooling costs while increasing the price of the home by small (around 10%) amount, via passive solar heating and natural cooling.
Of course encryption serves a different purpose, note I didn't say this is exactly what you want. But if you're worried someone will recover data from the disk after it's deleted, what about the same data before it's deleted?
Apparently I misunderstood why you want this daemon, and wrongly assumed the threat of recovery you're considering.
An encrypted filesystem will get you most of what you want. It'll require overhead for every file, not just deleted ones, can't push that overhead to the background, and could make recovery of the files you didn't delete more difficult (although this is a feature =)
If you use things like PGP, look into encrypted swap anyway, and set /proc/sys/vm/swappiness to 5 to make it less painful as linux loves to swap
echo '123...testing...123' > test.txt
openssl enc -bf < test.txt > test.txt.bf
mv test.txt test.txt.orig
openssl enc -d -bf < test.txt.bf > test.txt
diff test.txt.orig test.txt
Considering how really quick it was when I ran it years ago on a 400Mhz laptop, I would say this would be useful in set-top boxes, DVR and email checking, that sort of thing, on fairly low power processors.
Of course, that doesn't mean anyone will use it for that purpose, just seems like a natural fit for what was designed as a multimedia OS IIRC.
Just one implementation's example, it's been quite some time since anybody could say that documents in general are harmless.
There are a couple of useful replies here already, but I'll throw this out as well.
I had roughly the same problem a few minor versions back, I did the feedback agent thing, now I don't have the problem anymore since two things changed.
One is that I upgraded, so that likely corrected a few cases (where it crashed on one of the first few pages after starting firefox), but the other is what I suspect has made it more stable overall: setting limits on memory usage.
in about:config the main one that jumps out for me is browser.cache.memory.capacity, I set it to 16000. Another sanity check: browser.cache.disk.capacity, I have no idea why these aren't accessible in the preferences.
I read the article to imply that someone should be responsible for knowing what things are needed and allow just those things. A developer would need to use a compiler, while billing staff probably doesn't. And while it's not specifically spelled out, I would assume development stations need not be sitting on an unrestricted network in the first place.
In that case, why not have it rewritten to say what it means?
Exactly right, I think the time for light to travel all the way around the earth is 1/7 of a second. So, a terminal half-way around the world will have that as a (theoretical/best) round trip time...for each packet. Yea you'd never notice that while watching streaming video, but I wouldn't want my desktop response times in that range.
By way of example, without echo cancellation, a phone call from NY to LA could be annoying.
The individual software's not so much of problem... It's more about the dependencies...
How so? Why should it matter whether a package happens to be compiled locally or centrally? Seriously, aren't the dependancies exactly the same for a given app?
I've seen a few suggestions in the thread about using the AllowUsers option in sshd_config. I'll throw in my opinion that using AllowGroups is easier to maintain. For example, have 2 groups, one for human users and one for automated scripts. Then the ssh config doesn't need to be updated whenever a user is added or deleted.
I've never used Pegasus, but I'd say the same thing about Kmail, versus Thunderbird.
Part of my antispam approach is the tried-and-true method of using unique email addresses for every site/company/whatever. It doesn't make sense to have to go into the account settings and setup a new address every time, just make the From field editable =)
Isn't there a rule for iptables to redirect traffic coming into one IP, into another one? a one-liner, if I remember right.
Really though, if this worked at your location, you'd be able to spoof the packets without Lycos or anybody sending the traffic to you in the first place, no?