Knowing anywhere that the NSA is looking is a security risk.
Now that we know facebook can lower your credit score, some of us may change our behavior. The same theory applies to the credit score of a terrorist.
Google, Facebook, and Twitter may have been considered secure through obscurity, TMI for the NSA to sift and sort through. Some valuable information could have been obtained through social media, but we really do not know.
The military uses Two Person Integrity (TPI) for the transport of physical assets. Because there is a secure internet running behind the scenes that contains all this classified material, require two individuals to authenticate access to a specific document or subject matter.
Their motivation to move to fiber has nothing to do with technology or the usability of copper. Due to regulations, Verizon is required to lease existing lines (at the time of the law) at a fixed price. This was to allow competition.
By replacing copper with new infrastructure (the fiber), these new lines no longer fall under the regulation. Allowing Verizon to charge whatever they want and effectively stifling competition.
The point of this ruling is that there's no "requirement of notice to the account holder." This does not change the need of probable cause and a legal warrant presented to the 'third-party' in order to obtain the e-mails. The same logic applies to wire taps, the government is not required to notify an account holder that their calls are being monitored for illegal activity. Kinda defeats the purpose of a wire tap.
In effect, this basically states that if it leaves (or is kept outside of) your home the government is not required to notify you (the account holder) that it is being looked at. But if the government does look at it, it still needs to be judicially sanctioned and supported by probable cause.
For those who are offering commands to get rid of the data, you need to understand the why they will not work.
This issue is that the storage system used is designed is such a way that you CAN NOT modify any data once it is written to the disk.
Once the data is written, it can not be modified or deleted. Now, the reasoning behind this is so the police can not digitally manipulate the timestamps or data in any way. This is to protect the integrity of the data so it can withstand legal challenges.
They are faced with a 'catch 22' situation. If they can figure out a way to delete a 'prohibited conversation' they could theoretically modify the data too. Opening up the possibility of having a criminal conversation being invalidated.
Outside of shoring up your connectivity to the remote site, you should use the structure of your company to your advantage.
It sounds like the wild west. You gave everyone full RW access to the fileserver.
Build a file structure the mirrors the organization of the company and apply permissions appropriately. Map drives in the same fashion. An added advantage to this, you can split the files across separate Samba servers later with a minor map change.
The finance department has no reason digging around in your design documents. The engineers don't have any reason to poke around in your sales collateral. Does everyone in the company need to be tempted to open "DOD_GPS_NOYB_47-090611.xls"
Getting every employee to adhere to a single naming convention is like herding cats. Delegate responsibility to the directors and managers to keep their areas on the server organized to their own needs. Then you just need to deal with the occasional outlaw.
You may also want to deploy Samba servers to the local offices and back them up to a central server regularly. Use this for personal shares and anything that is primarily used ONLY in the local office.
In most cases, I doubt that "the single person" working on Project X at Remote Site A needs to work off of a centralized copy of their document. Do you really need to share this document across your entire organization? Let the employee keep their file on the local offices share. Let a employee or a manager share it with the entire department. Let the director share it with sales.
In the end, you may find one small part of the organization that REALLY needs a naming or numbering convention. You can address that when they approach you. For now, you need to stop everyone from treating the company share like their own desktop.
This is just another example of Microsoft being deliberately anti-competitive.
I am not convinced this is a purely deliberate move by MS. I am reminded of something I found when Lucent introduced TCP/IP to their telecommunications network elements.
While Lucent was true to the specifications, just defining the gateway address was a complicated task. Effectively, Lucent built their TCP/IP stack from scratch without any understanding of common 'real world' practices. There were a few actual issues with the TCP/IP, but the most memorable was an outright frustrating configuration interface. 010.032.000.005/FFFFFF00
Both of these companies are used to building their software and then defining the standards. When presented with an accepted set of standards that are not based on their own designs, they can make it work OK but don't have the ability to apply the common practices. Which is the root cause of the ODF interoperability issues.
While I have made my own, I really just don't have the time. Especially when I need a few dozen patch cables.
Running to the store is great, but I've learned the hard way to trust only one manufacturer. Their cables are guaranteed for life!
Buy a few hundred 'Brand X' cables and a percentage of them could be useless. Once that happens, you'll have a box of cables you'll never want to use. Just can't trust them.
Beside, who has a spool of beige, black, blue, gray, green, orange, pink, purple, red (crossover only), white, and yellow laying around?
One little know fact is that your local telephone company (Verizon) typically must follow rules imposed by both the FCC and your States 'Public Utilities Commission' (PUC). Depending where you live, there is sometimes even a local PUC.
You can complain to both the FCC and PUC(s) about your service.
While it may not be enough to improve your service right away, the telephone company MUST pay attention these complaints.
"I think if it's worth pirating for someone, it's worth paying for." In my very non-scientific study of torrents, I found less than 2,000 seeders for Vista -and- over 10,000 for XP.
I would take the opportunity and discuss the difference between hobbyists and 'for profit' piracy. While the MPAA has changed the laws to include 'no monetary gain' through its lobbying efforts, the true pirates are still selling DVD's on the street.
You should also learn about his personal interests and use relevant analogies.
I would compare the hobbyists that post 0-day screeners to something like mountain climbers attempting to beat the fastest time to the peak of Mt. Everest. There are challenges and risk associated with both, but there is also the thrill that compels people to do both.
While I may not know who or what the current record may be, there are real climbers that do. Help him understand what he is really facing as the MPAA attempts to eradicate piracy. Help him understand that each 'tool' that the MPAA employs only presents new challenges to the hobbyists.
Overall, provide him with useful information that could help him do his job better.
Back when key caps could be removed with out damaging the spring mechanism...
I found that soaking the key caps in 409 and water would remove any finger crud.
While the key caps are off, tap and shake out the (INSERT FAVORITE SNACK) seasonings and give the other surfaces a quick wipe down.
The key caps dry in about an hour. Hopefully you know the layout of your keyboard when putting the key caps back on.
With later model keyboards I use 409 and cotton swabs to go after all accessible surfaces.
Slashdot Mirror
Knowing anywhere that the NSA is looking is a security risk.
Now that we know facebook can lower your credit score, some of us may change our behavior.
The same theory applies to the credit score of a terrorist.
Google, Facebook, and Twitter may have been considered secure through obscurity, TMI for the NSA to sift and sort through.
Some valuable information could have been obtained through social media, but we really do not know.
The military uses Two Person Integrity (TPI) for the transport of physical assets. Because there is a secure internet running behind the scenes that contains all this classified material, require two individuals to authenticate access to a specific document or subject matter.
Their motivation to move to fiber has nothing to do with technology or the usability of copper.
Due to regulations, Verizon is required to lease existing lines (at the time of the law) at a fixed price. This was to allow competition.
By replacing copper with new infrastructure (the fiber), these new lines no longer fall under the regulation.
Allowing Verizon to charge whatever they want and effectively stifling competition.
Microsoft is attempting to get everyone embrace the BSOD.
That would be the only reason I would even consider returning to windows.
I am surprised that nobody mentioned it.
Tcl/Tk is a scripting language specifically designed for automated testing and software quality assurance.
http://en.wikipedia.org/wiki/Tcl
router# wr me
.. disconnected from remote host (oops, wait for reload)
router# reload in 30
router# conf t
router(config)# (good luck)
Do I get an extra bonus if I pop them all?
The title of the article is pure sensationalism.
E-mail is still protected by the 4th Amendment.
The ruling was that there is no 'constitutional requirement of notice to the account holder' for items in possession of a third-party.
The point of this ruling is that there's no "requirement of notice to the account holder."
This does not change the need of probable cause and a legal warrant presented to the 'third-party' in order to obtain the e-mails.
The same logic applies to wire taps, the government is not required to notify an account holder that their calls are being monitored for illegal activity. Kinda defeats the purpose of a wire tap.
In effect, this basically states that if it leaves (or is kept outside of) your home the government is not required to notify you (the account holder) that it is being looked at. But if the government does look at it, it still needs to be judicially sanctioned and supported by probable cause.
This is a reasonable expectation.
For those who are offering commands to get rid of the data, you need to understand the why they will not work.
This issue is that the storage system used is designed is such a way that you CAN NOT modify any data once it is written to the disk.
Once the data is written, it can not be modified or deleted. Now, the reasoning behind this is so the police can not digitally manipulate the timestamps or data in any way. This is to protect the integrity of the data so it can withstand legal challenges.
They are faced with a 'catch 22' situation. If they can figure out a way to delete a 'prohibited conversation' they could theoretically modify the data too. Opening up the possibility of having a criminal conversation being invalidated.
Outside of shoring up your connectivity to the remote site, you should use the structure of your company to your advantage.
It sounds like the wild west. You gave everyone full RW access to the fileserver.
Build a file structure the mirrors the organization of the company and apply permissions appropriately.
Map drives in the same fashion. An added advantage to this, you can split the files across separate Samba servers later with a minor map change.
The finance department has no reason digging around in your design documents.
The engineers don't have any reason to poke around in your sales collateral.
Does everyone in the company need to be tempted to open "DOD_GPS_NOYB_47-090611.xls"
Getting every employee to adhere to a single naming convention is like herding cats. Delegate responsibility to the directors and managers to keep their areas on the server organized to their own needs. Then you just need to deal with the occasional outlaw.
You may also want to deploy Samba servers to the local offices and back them up to a central server regularly. Use this for personal shares and anything that is primarily used ONLY in the local office.
In most cases, I doubt that "the single person" working on Project X at Remote Site A needs to work off of a centralized copy of their document. Do you really need to share this document across your entire organization? Let the employee keep their file on the local offices share. Let a employee or a manager share it with the entire department. Let the director share it with sales.
In the end, you may find one small part of the organization that REALLY needs a naming or numbering convention. You can address that when they approach you. For now, you need to stop everyone from treating the company share like their own desktop.
The key thing to keep in mind is to make sure your system has enough resources to run it, because it is demanding.
Here is why Vista failed... and Windows 7 will too.
New hardware was not a requirement for the newest OS.
I was able to upgrade my Win3.1 machine to Win95.
When I was ready for a new machine, Win95 followed me to the higher spec hardware.
I was able to upgrade my Win95 machine to Win98.
When I was ready for a new machine, Win98 followed me to the higher spec hardware.
I was able to upgrade my Win98 machine to XP.
When I was ready for a new machine, XP followed me to the higher spec hardware.
I was not able to upgrade my XP machine to Vista.
I was not ready for a new machine, so I installed Linux.
When I was ready for a new machine, I bought a Mac.
---
I prefer; 'kill -9 PID' -over- Pressing 'end now' dozens of times in a dialog box and having to reboot anyway.
This is just another example of Microsoft being deliberately anti-competitive.
I am not convinced this is a purely deliberate move by MS. I am reminded of something I found when Lucent introduced TCP/IP to their telecommunications network elements.
While Lucent was true to the specifications, just defining the gateway address was a complicated task. Effectively, Lucent built their TCP/IP stack from scratch without any understanding of common 'real world' practices. There were a few actual issues with the TCP/IP, but the most memorable was an outright frustrating configuration interface. 010.032.000.005/FFFFFF00
Both of these companies are used to building their software and then defining the standards. When presented with an accepted set of standards that are not based on their own designs, they can make it work OK but don't have the ability to apply the common practices. Which is the root cause of the ODF interoperability issues.
Black Box
While I have made my own, I really just don't have the time. Especially when I need a few dozen patch cables.
Running to the store is great, but I've learned the hard way to trust only one manufacturer. Their cables are guaranteed for life!
Buy a few hundred 'Brand X' cables and a percentage of them could be useless.
Once that happens, you'll have a box of cables you'll never want to use. Just can't trust them.
Beside, who has a spool of beige, black, blue, gray, green, orange, pink, purple, red (crossover only), white, and yellow laying around?
Outside of the cartoon characters I use in the lab, I like to 'model' my naming scheme on 'Common Language Location Identifier' (CLLI)
DNS001NYNYUS
DNS002NYNYUS
SMTP01NYNYUS
POP301NYNYUS
FTP001LACAUS
etc...
/. has dropped to number 11
Guess no one took into account the large sector of (insert field) managers that read slashdot.
I would change the wallpaper to display a notice about the infection.
Let the user know that their computer is responsible for SPAM, identity theft, and don't forget file sharing.
Maybe even mention that the RIAA will get them if they do nothing about it.
One little know fact is that your local telephone company (Verizon) typically must follow rules imposed by both the FCC and your States 'Public Utilities Commission' (PUC). Depending where you live, there is sometimes even a local PUC.
You can complain to both the FCC and PUC(s) about your service.
While it may not be enough to improve your service right away, the telephone company MUST pay attention these complaints.
Obviously, XP is still worth paying for.
Microsoft just wants to remind everyone who uses FireFox that IE is not their default browser.
Flight of the Hamsters
I would take the opportunity and discuss the difference between hobbyists and 'for profit' piracy. While the MPAA has changed the laws to include 'no monetary gain' through its lobbying efforts, the true pirates are still selling DVD's on the street.
You should also learn about his personal interests and use relevant analogies.
I would compare the hobbyists that post 0-day screeners to something like mountain climbers attempting to beat the fastest time to the peak of Mt. Everest. There are challenges and risk associated with both, but there is also the thrill that compels people to do both.
While I may not know who or what the current record may be, there are real climbers that do. Help him understand what he is really facing as the MPAA attempts to eradicate piracy. Help him understand that each 'tool' that the MPAA employs only presents new challenges to the hobbyists.
Overall, provide him with useful information that could help him do his job better.
Back when key caps could be removed with out damaging the spring mechanism...
I found that soaking the key caps in 409 and water would remove any finger crud.
While the key caps are off, tap and shake out the (INSERT FAVORITE SNACK) seasonings and give the other surfaces a quick wipe down.
The key caps dry in about an hour. Hopefully you know the layout of your keyboard when putting the key caps back on.
With later model keyboards I use 409 and cotton swabs to go after all accessible surfaces.