I actually asked this question once. Nobody could really give me a good answer. I personally prefer 10.0.0.0 over 192.168.0.0. It does look pretier, it's easier to type, and you do have more IPs to play with. Who has need for all those IPs is beyond me, but I say you can never have too many IPs.
It does look prettier. here is how I broke down my NAT network
I came up with the list in about 5 mins of work space-out time. I am not a security expert and I agree with some of your points.
I do question frequent password changes, probably the biggest advantage is security from internal attacks. Giving out a password to a co-worker who needs access to some files I have access to, but am not around to retrieve for them is a common occurance (I don't do it myself, but I wouldn't mind getting a penny for every time this example occurs). There are still flaws with that reasoning as well. People start to use incremental passwords, etc..., but I do feel a little more comfortable in that instance. What about hardware tokens? I don't know if this is a good way to go either. Increased costs, more support, single point of intrusion (key stores) are all pretty negative sides to using a solution to such. Perhaps it's best that people consider as many possibilities and decide what's best for their situation.
I don't go for unplugging devices or nodes on a whim. If an area does become completely infected, then I would say that losing productivity by bringing network connectivity down is a moot point by then. Productivity is already lost. Preemptive isolation, however, is just plain wrong.
(Damn...I should learn to think a little longer on some of my ideas)
I don't assume IM is evil. Again, this is a choice that each company must make. I use IM internally to contact several different departments with speed and grace. IM DOES increase speed of communications.
I am all for IM, but if your company does not need IM for internal/external BUSINESS productivity, why use it? This isn't about cutting peoples rights. IM is a relatively new concept in the business model, you really aren't doing anything so bad as "doing away with paid vacations." After all, they didnt' have IM readily available to all employees back in the late 90s and earlier. I was really aiming at closing unneccesary ports, considering the necessity of the software that is generally installed, etc...I still contact friends by e-mail, and I am talking to you by/. comments:)
Security is as each company does. I just scratched up a list, slapped some pretty on it and out the door it went. I would ask for a strong firewall, a serious plan of attack/defense. And I always love my patches/updates.
It probably isn't. A secure network is a network with all devices unplugged from the network. A secure server/workstation is a server/workstation that is powered down, in a vault with the key thrown away.
What's the most secure option?
- Constantly update all software/firmware/antivirus.
- ALL employees should frequently change passwords (consider forcing changes on a regular basis (1 week where I work).
- Monitor your networks.
- Create restrictive firewall rules (boo hoo...the workers can't IM their buddies...GET BACK TO WORK!!!).
- Antivirus should be installed on all machines (servers/workstations).
- E-mail virus filtering solutions must be implemented.
- Keep up to date with security publications, lectures, software, concepts, etc..
That's all the prentative requirements. Now on to the most important part of security, realizing that you still have a good chance of being compromised.
- Intrusion detection software wherever possible.
- Have a plan ready to implement in the case of an intrusion.
- Use the 5Ws and an H (Who, what, where, when, why and how.).
- Make sure you have contacts for any help handy and available to any personel who might be involved in post-intrusion procedures.
All of this is a pretty big job. Something that should perhaps be handed to a person or group of persons (depending on the size of the company you represent) who can work this on a full-time basis.
Security is as strong as your weakest link. You are the weakest link. Get some stacker 2 and beef up!
I actually never thought of using a system like CVS. I kept master copies of the documents on an intranet, but it was my responsibility to copy the documents up to the intranet site when I created or updated my documents.
As a side note, stupid me attempted to use as common variable placeholders for my previous example. It should have read more like:
--- foo.bar.com Built on 6/20/2003 Built by (name)
On any machine that I work on, I create a directory similar to '/-Build/' or 'C:\-Build\'. In this folder I keep subdirectories w/ drivers, software, updates, configs, etc. One other thing I include is a file called build.txt. In this file I put some nice information to have:
--- foo.bar.com Built on 6/20/2003 Built by
Installation notes:
Updates: 6/26/2003 -
---
I am a big fan of making sure everybody knows "who-dun-it" and how to do it again.
MTBF is probably determined by taking a bunch of drives, putting them into PERFECT conditions that NEVER exist in the real world. Run them in a way that, although test all functionality, really doesn't provide true conditions for drives (IE head always reading/writing up and down the disk probably never seeking, disks always spinning, etc..). Something that drives never do in real life. Statistics...statistics...statistics...(speeling too:)
Questions for your question
on
Wireless VOIP?
·
· Score: 1
What type of recording are you doing? Voice? Instrumental, etc.?
What type of audio quality are you looking for? Sorta goes back to voice, intstrumental or mixture, but I was thinking more along the lines of bit rates, etc..
These 15 mics, are they in seperate locations (rooms or distances greater than 1 Km/Mi)recording seperate audio (multiple sources not intended to be mixed together)?
Is this a live broadcast, a live broadcast with an archive or just an archive?
Without answering these, it's really hard to decide how much you should/could spend and/or what technology you could/should use.
You know...I was wondering the same thing myself. It could get awefully confusing if you are attempting to install something from what you THINK is the latest feed. I guess you just have to look at it as stable = Even and testing/unstable=odd. Dunno...
1) I could never get it to play nice. You couldn't see the icons or button pictures correctly. It also tended to puke every now and then.
2) Finally I was able to install Konquerer ok. It appears to hit the sites w/o even a hiccup. I got it to work by installing as many libs as I felt might be needed to run Konq. Don't ask, I just picked them at random. I really don't feel like digging around in the ipkgs to find the damed dependencies.
3 or 2) There is always opiemail. I can't get it to work, but I probably didn't install enough libs or dependencies to make it work. As before, I am too lazy to figure out what they are.
4 or 3) I have only been able to get word and sheet to work. The rest...well I don't do presentations from my PDA:)
4 or 5) Dunno. I use alternative apps that work similar for less (free).
According to several posts on the OpenZaurus-Users mailing list, any problems w/ 3rd party applications should be posted as bug reports. OZ is supposed to be as compatible w/ Sharp's ROM for 3rd party apps. That is a pretty hard standard to keep at all times in my opinion.
All in all OZ 3.2 isn't bad, but if you only use your Zaurus for PIM stuff, I still say Sharp ROM is the way to go.
I have been playing around w/ it for the past few days. I must say this is the best release so far (as it should be:). Only beef I ever had involves the lack of documentation for installing stable feed ipkgs. You almost have to stumble around and pray you can install the correct dependencies. For instance, I am unable to install LIRC as it requires kernel-modules-2.4.6-rmk1-np2-embedix. Well...I have the kernel modules installed (duh...). I don't see any other ipkgs that meet this requirement in the stable feed.
Planning is fine, but I doubt that CDMA v/s GSM is really on the top 10 list of things needing rebuilt...I would be more concerned about food, medicine, shelter. Then I would start worrying about gov't. THEN after everything is smoothed out, I would start worrying about the LITTLE details such as how my cell phone can send text messages.
There is an old and VERY familar saying. "Don't count your chickens before they hatch." We don't even have Baghdad yet and we are already arguing for what CELL phone STANDARD to use?!?!?! Come ON... I would be more worried about how to take Baghdad and what is needed to keep Baghdad before we start worrying about CDMA vs. GSM.
Well...This sucks...I am stuck in limbo because of this. I had DSL through NP at my old place. I cancelled it and had a new order in place for the new apartment placed just a few days ago. NorthPoint is the ONLY broadband I have (had) in the area. No cable, no wireless, no DSL, even dialup is pretty crappy. This must not be my day:/ I just went from 1.5M to 28.8k in less than a week.
Pittsburgh is a good example of how NOT to attract the younger "geek" culture. Let me list them.
1. No really good clubs (except for Metropol, Bar Pittsburgh, and a few other choice hang-outs). Other than that. You don't have much going for you.
2. Pittsburgh has become decentralized. With the recent growth of Fore Systems, people have begun to move towards Cranberry. Other similar suberbs (or "distant" branches) have begun to grow, moving a lot of big business out of downtown (Major companies such as Westinghouse have moved out completely.
3. Cost of living around here isn't bad, but most places you work for are WAY under the national salary average.
4. We don't (currently) have any major attractions other than the Steelers (don't think so next year with the way they played THIS year).
5. Our local government is run by an older generation that remembers when they had to do calculations on punch cards (cool stuff, but WAY outdated). We don't seem to have a very good influx of younger politicians to help "stir things up."
6. With the way the Job Market is right now, a lot of companies are pulling people currently employed from Pittsburgh to other cities. Pittsburgh is either too nice, or too dumb to do the same.
7. With the way us native Pittsburgher's talk n'at, yeunz would wonder why those out-of-towners look at us a little askew:)
8. Did I mention lower pay versus cost of living?
9. Everything gets TOO quiet at around 6:00pm downtown. Everywhere else shuts down at 9:30pm. Only places left open are your bars, Eat-N-Puke's, and the occasional decent Hang-out (still no better than point 1).
10. We are slow to get technology here. Even though we have had DSL since around Dec. 1998 and cable-modems slightly before that, almost 40% of the surrounding and downtown areas cannot get their high-speed kicks.
11. Traffic is terrible. I HATE taking the Parkway East in to downtown. It takes me about an hour to move 3 miles, where as it would only take me 5 minutes to move the same distance at night.
12. Weather isn't always the greatest. One minute it could be snowing, the next minute you are out at the local pool trying to cool off:)
13. Starlake is a RIP-OFF!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!
There ARE a few redeeming qualities.
1. Steelers, Pens 2. TONS of movie theaters 3. TONS of local brews 4. John Harvards 5. Low crime rates (relatively) 6. Major/Minor Bands tour/reside here frequently 7. Perogies (prolly misspelled) 8. Retirement Plans are normally MOVE TO FLORIDA! 9. You can make fun of West Virginia, but NOT New York 10. CMU, UPMC, PITT. 11. Perogies (prolly misspelled, but I STILL like 'em)
Keep in mind this is the jaded view of a younger person. so BLAH, n'at
Part of the problem that has haunted Open Source is the fact that there are many people willing to develop their own code because the code that they have been using "doesn't quite cut it." Don't get me wrong, that is also part of what makes Open Source so great. It can also be it's downfall. GNOME and KDE being a potential example of this. Although both were designed as an X Environment, they have-for the most part-gone seperate ways in how each interacts with X. By meeting on common grounds on certain issues, they are giving your everyday user (such as myself) better choices without much hassle.
Now keep in mind, these are my opinions...I am not all knowing, and not a very good speller. Please feel free to correct me if I am wrong.
Would be perfect for those do it yourself Car MP3 Players. Either that or you brag about how small your computer is (that whole "mine's smaller than yours" thing).
Slashdot Mirror
To each their own :)
I actually asked this question once. Nobody could really give me a good answer. I personally prefer 10.0.0.0 over 192.168.0.0. It does look pretier, it's easier to type, and you do have more IPs to play with. Who has need for all those IPs is beyond me, but I say you can never have too many IPs.
It does look prettier. here is how I broke down my NAT network
10.0.0.0-255 = Routers/Server - Kinda, sorta DMZ
10.0.1.0-255 = Wired Workstations
10.0.2.0-255 = Wireless Workstations
10.0.3.0-255 = Test stuffage
192.168.0.0 is the defacto standard for just about any router you buy off the shelf. Perhaps there is a valid reason?
I came up with the list in about 5 mins of work space-out time. I am not a security expert and I agree with some of your points.
/. comments :)
I do question frequent password changes, probably the biggest advantage is security from internal attacks. Giving out a password to a co-worker who needs access to some files I have access to, but am not around to retrieve for them is a common occurance (I don't do it myself, but I wouldn't mind getting a penny for every time this example occurs). There are still flaws with that reasoning as well. People start to use incremental passwords, etc..., but I do feel a little more comfortable in that instance. What about hardware tokens? I don't know if this is a good way to go either. Increased costs, more support, single point of intrusion (key stores) are all pretty negative sides to using a solution to such. Perhaps it's best that people consider as many possibilities and decide what's best for their situation.
I don't go for unplugging devices or nodes on a whim. If an area does become completely infected, then I would say that losing productivity by bringing network connectivity down is a moot point by then. Productivity is already lost. Preemptive isolation, however, is just plain wrong.
(Damn...I should learn to think a little longer on some of my ideas)
I don't assume IM is evil. Again, this is a choice that each company must make. I use IM internally to contact several different departments with speed and grace. IM DOES increase speed of communications.
I am all for IM, but if your company does not need IM for internal/external BUSINESS productivity, why use it? This isn't about cutting peoples rights. IM is a relatively new concept in the business model, you really aren't doing anything so bad as "doing away with paid vacations." After all, they didnt' have IM readily available to all employees back in the late 90s and earlier. I was really aiming at closing unneccesary ports, considering the necessity of the software that is generally installed, etc...I still contact friends by e-mail, and I am talking to you by
Security is as each company does. I just scratched up a list, slapped some pretty on it and out the door it went. I would ask for a strong firewall, a serious plan of attack/defense. And I always love my patches/updates.
It probably isn't. A secure network is a network with all devices unplugged from the network. A secure server/workstation is a server/workstation that is powered down, in a vault with the key thrown away.
What's the most secure option?
- Constantly update all software/firmware/antivirus.
- ALL employees should frequently change passwords (consider forcing changes on a regular basis (1 week where I work).
- Monitor your networks.
- Create restrictive firewall rules (boo hoo...the workers can't IM their buddies...GET BACK TO WORK!!!).
- Antivirus should be installed on all machines (servers/workstations).
- E-mail virus filtering solutions must be implemented.
- Keep up to date with security publications, lectures, software, concepts, etc..
That's all the prentative requirements. Now on to the most important part of security, realizing that you still have a good chance of being compromised.
- Intrusion detection software wherever possible.
- Have a plan ready to implement in the case of an intrusion.
- Use the 5Ws and an H (Who, what, where, when, why and how.).
- Make sure you have contacts for any help handy and available to any personel who might be involved in post-intrusion procedures.
All of this is a pretty big job. Something that should perhaps be handed to a person or group of persons (depending on the size of the company you represent) who can work this on a full-time basis.
Security is as strong as your weakest link. You are the weakest link. Get some stacker 2 and beef up!
I actually never thought of using a system like CVS. I kept master copies of the documents on an intranet, but it was my responsibility to copy the documents up to the intranet site when I created or updated my documents.
As a side note, stupid me attempted to use as common variable placeholders for my previous example. It should have read more like:
---
foo.bar.com
Built on 6/20/2003
Built by (name)
Installation notes:
6/20/2003 - (name)
(some stuff)
Updates:
6/26/2003 - (name)
(More stuff)
---
with folders more like 'c:\(machine-name)-build\' and '/(machine-name)-build/'.
On any machine that I work on, I create a directory similar to '/-Build/' or 'C:\-Build\'. In this folder I keep subdirectories w/ drivers, software, updates, configs, etc. One other thing I include is a file called build.txt. In this file I put some nice information to have:
---
foo.bar.com
Built on 6/20/2003
Built by
Installation notes:
Updates:
6/26/2003 -
---
I am a big fan of making sure everybody knows "who-dun-it" and how to do it again.
That's the key word.
:)
MTBF is probably determined by taking a bunch of drives, putting them into PERFECT conditions that NEVER exist in the real world. Run them in a way that, although test all functionality, really doesn't provide true conditions for drives (IE head always reading/writing up and down the disk probably never seeking, disks always spinning, etc..). Something that drives never do in real life. Statistics...statistics...statistics...(speeling too
WHERE'S THE BEEF!!!
What type of recording are you doing? Voice? Instrumental, etc.?
What type of audio quality are you looking for? Sorta goes back to voice, intstrumental or mixture, but I was thinking more along the lines of bit rates, etc..
These 15 mics, are they in seperate locations (rooms or distances greater than 1 Km/Mi)recording seperate audio (multiple sources not intended to be mixed together)?
Is this a live broadcast, a live broadcast with an archive or just an archive?
Without answering these, it's really hard to decide how much you should/could spend and/or what technology you could/should use.
You know...I was wondering the same thing myself. It could get awefully confusing if you are attempting to install something from what you THINK is the latest feed. I guess you just have to look at it as stable = Even and testing/unstable=odd. Dunno...
1) I could never get it to play nice. You couldn't see the icons or button pictures correctly. It also tended to puke every now and then.
:)
2) Finally I was able to install Konquerer ok. It appears to hit the sites w/o even a hiccup. I got it to work by installing as many libs as I felt might be needed to run Konq. Don't ask, I just picked them at random. I really don't feel like digging around in the ipkgs to find the damed dependencies.
3 or 2) There is always opiemail. I can't get it to work, but I probably didn't install enough libs or dependencies to make it work. As before, I am too lazy to figure out what they are.
4 or 3) I have only been able to get word and sheet to work. The rest...well I don't do presentations from my PDA
4 or 5) Dunno. I use alternative apps that work similar for less (free).
According to several posts on the OpenZaurus-Users mailing list, any problems w/ 3rd party applications should be posted as bug reports. OZ is supposed to be as compatible w/ Sharp's ROM for 3rd party apps. That is a pretty hard standard to keep at all times in my opinion.
All in all OZ 3.2 isn't bad, but if you only use your Zaurus for PIM stuff, I still say Sharp ROM is the way to go.
I have been playing around w/ it for the past few days. I must say this is the best release so far (as it should be :). Only beef I ever had involves the lack of documentation for installing stable feed ipkgs. You almost have to stumble around and pray you can install the correct dependencies. For instance, I am unable to install LIRC as it requires kernel-modules-2.4.6-rmk1-np2-embedix. Well...I have the kernel modules installed (duh...). I don't see any other ipkgs that meet this requirement in the stable feed.
Yes it does. Read..well..just about anything on www.zaurus.com/dev.
Planning is fine, but I doubt that CDMA v/s GSM is really on the top 10 list of things needing rebuilt...I would be more concerned about food, medicine, shelter. Then I would start worrying about gov't. THEN after everything is smoothed out, I would start worrying about the LITTLE details such as how my cell phone can send text messages.
There is an old and VERY familar saying. "Don't count your chickens before they hatch." We don't even have Baghdad yet and we are already arguing for what CELL phone STANDARD to use?!?!?! Come ON... I would be more worried about how to take Baghdad and what is needed to keep Baghdad before we start worrying about CDMA vs. GSM.
Well...This sucks...I am stuck in limbo because of this. I had DSL through NP at my old place. I cancelled it and had a new order in place for the new apartment placed just a few days ago. NorthPoint is the ONLY broadband I have (had) in the area. No cable, no wireless, no DSL, even dialup is pretty crappy. This must not be my day :/ I just went from 1.5M to 28.8k in less than a week.
Their download site seems to be down. Sucky
Pittsburgh is a good example of how NOT to attract the younger "geek" culture. Let me list them.
:)
:)
! !!!!!!!!!!!!!!!!!!!!!!!!!
1. No really good clubs (except for Metropol, Bar Pittsburgh, and a few other choice hang-outs). Other than that. You don't have much going for you.
2. Pittsburgh has become decentralized. With the recent growth of Fore Systems, people have begun to move towards Cranberry. Other similar suberbs (or "distant" branches) have begun to grow, moving a lot of big business out of downtown (Major companies such as Westinghouse have moved out completely.
3. Cost of living around here isn't bad, but most places you work for are WAY under the national salary average.
4. We don't (currently) have any major attractions other than the Steelers (don't think so next year with the way they played THIS year).
5. Our local government is run by an older generation that remembers when they had to do calculations on punch cards (cool stuff, but WAY outdated). We don't seem to have a very good influx of younger politicians to help "stir things up."
6. With the way the Job Market is right now, a lot of companies are pulling people currently employed from Pittsburgh to other cities. Pittsburgh is either too nice, or too dumb to do the same.
7. With the way us native Pittsburgher's talk n'at, yeunz would wonder why those out-of-towners look at us a little askew
8. Did I mention lower pay versus cost of living?
9. Everything gets TOO quiet at around 6:00pm downtown. Everywhere else shuts down at 9:30pm. Only places left open are your bars, Eat-N-Puke's, and the occasional decent Hang-out (still no better than point 1).
10. We are slow to get technology here. Even though we have had DSL since around Dec. 1998 and cable-modems slightly before that, almost 40% of the surrounding and downtown areas cannot get their high-speed kicks.
11. Traffic is terrible. I HATE taking the Parkway East in to downtown. It takes me about an hour to move 3 miles, where as it would only take me 5 minutes to move the same distance at night.
12. Weather isn't always the greatest. One minute it could be snowing, the next minute you are out at the local pool trying to cool off
13. Starlake is a RIP-OFF!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
There ARE a few redeeming qualities.
1. Steelers, Pens
2. TONS of movie theaters
3. TONS of local brews
4. John Harvards
5. Low crime rates (relatively)
6. Major/Minor Bands tour/reside here frequently
7. Perogies (prolly misspelled)
8. Retirement Plans are normally MOVE TO FLORIDA!
9. You can make fun of West Virginia, but NOT New York
10. CMU, UPMC, PITT.
11. Perogies (prolly misspelled, but I STILL like 'em)
Keep in mind this is the jaded view of a younger person. so BLAH, n'at
Part of the problem that has haunted Open Source is the fact that there are many people willing to develop their own code because the code that they have been using "doesn't quite cut it." Don't get me wrong, that is also part of what makes Open Source so great. It can also be it's downfall. GNOME and KDE being a potential example of this. Although both were designed as an X Environment, they have-for the most part-gone seperate ways in how each interacts with X.
By meeting on common grounds on certain issues, they are giving your everyday user (such as myself) better choices without much hassle.
Now keep in mind, these are my opinions...I am not all knowing, and not a very good speller. Please feel free to correct me if I am wrong.
Would be perfect for those do it yourself Car MP3 Players. Either that or you brag about how small your computer is (that whole "mine's smaller than yours" thing).