I've never heard of it. Sounds like something a senior beaurocrat[sic] thought up. "Hey, I betcha this is more secure, let's do it and call it a best practice."
The senior "beaurocrats" at the NSA trump your security credentials.
Should I assume that my password is compromised "by methods other", distinguishable from magic
Don't be an ass. There are plenty of other ways to acquire a user's passwords than trying "joe123", "joe124", etc. These can include keyloggers on public terminals, users who like to write their passwords down, social engineering, alternative attack vectors that expose passwords on an unsecure system, etc.
As you can see, this is all very confusing and how do I know that a month is a good time between changes? It could be woefully inadequate or grossly pessimistic.
Or... it could be a best guess compromise that balances usability and security.
It's a lot easier to put up a better antenna than it is to redo last-mile cable runs. This goes double for areas that have buildings with history across a time period measured in centuries.
If you're using a strong password that is compromised by methods other than brute-force discovery, changing it on a regular basis reduces the window in which the attacker can access the system relatively undetected.
I'm not sure what your definition of "stealing" is, but he certainly didn't deprive the people of their personal information.
The RFID chips in the passports are designed to spew forth their data when asked for it. You can't accuse someone of "stealing" information that they read off a billboard, which is effectively how the RFID chips in these passports work. (I said effectively, so don't go down the tired road of debating which perfect analogy fits)
An easy way to avoid the physical server sprawl with having an empty root and multiple domains is to just virtualize. With just 2 physical servers, you can run DCs for the Empty Root, and any domains under it, with full redundancy.
The way we do it at my office is to have one workstation in each department deemed a "Patch test" computer. 3 work days of use is more than enough to detect major issues. That just leaves us with servers to manually test.
At 17,000 desktops, you should probably be running SMS or at least a tiered WSUS environment. It's not that hard to patch machines nightly, as long as you don't have them all going to a single poor WSUS server.
"Required by law" does not mean "required by an officer," it means whatever sobriety tests are required by the laws in your state governing implied consent. For example, in most states "field sobriety tests" such as the one-leg-stand are completely voluntary.
I worked at a company where our entire IT department (6 people) had an unofficial pact to quit together if management kept up its games. One day, it came to that. We all just left when we were told that unpaid overtime would be required on Saturdays to basically do manual labor in the warehouse.
They went out of business less than a month later, after spending nearly an entire month's cash flow on forensic network/systems engineering consultants.
Lazy? Odd choice of a word there. Most companies will terminate employment on the spot for off-the-clock or unapproved overtime. It's not a chance most IT workers want to take, especially for the type of boss that would call them lazy for expecting to be paid to work.
Management types like you give the rest of humanity a bad name.
Slashdot Mirror
I've never heard of it. Sounds like something a senior beaurocrat[sic] thought up. "Hey, I betcha this is more secure, let's do it and call it a best practice."
The senior "beaurocrats" at the NSA trump your security credentials.
Should I assume that my password is compromised "by methods other", distinguishable from magic
Don't be an ass. There are plenty of other ways to acquire a user's passwords than trying "joe123", "joe124", etc. These can include keyloggers on public terminals, users who like to write their passwords down, social engineering, alternative attack vectors that expose passwords on an unsecure system, etc.
As you can see, this is all very confusing and how do I know that a month is a good time between changes? It could be woefully inadequate or grossly pessimistic.
Or... it could be a best guess compromise that balances usability and security.
It's a lot easier to put up a better antenna than it is to redo last-mile cable runs. This goes double for areas that have buildings with history across a time period measured in centuries.
What about the "with intent that the same may be used" qualifier? Making a forgery doesn't seem to be illegal, as long as it's not used.
If you're using a strong password that is compromised by methods other than brute-force discovery, changing it on a regular basis reduces the window in which the attacker can access the system relatively undetected.
I'm not sure what your definition of "stealing" is, but he certainly didn't deprive the people of their personal information.
The RFID chips in the passports are designed to spew forth their data when asked for it. You can't accuse someone of "stealing" information that they read off a billboard, which is effectively how the RFID chips in these passports work. (I said effectively, so don't go down the tired road of debating which perfect analogy fits)
But you could just let your friend drive your car, which would deprive the car company their legally-entitled profit.
so the program would be able to return that money to congress.
I forgive you if you've never worked in government before, but Rule numbers 1, 2, and 3 of budgeting are: Never, EVER finish with unused funds. EVER.
a megawatt of electricity isn't cheap, especially at peak rates
1,000kWh is only $125 or so, down here, and that's after the big price hike.
I would grab two of these, put them in an OpenFiler set, and use them as disk backups of evey OTHER drive I have in the home.
Primary storage? Ehh...
Once you get to the terabyte range, which I assume you were meaning to refer to, the difference is nearly 10%. That becomes a big deal.
It's really only 1800 Gigs.
It seems like the write time is the most variable out of all these. FAT32/NTFS/ExFAT scores for reading are all within a few % of each other.
I wonder what makes NTFS so slow for writes? The journaling alone reduces it that far?
Wait, did I miss something? What does HD have to do with songs being DLC?
An easy way to avoid the physical server sprawl with having an empty root and multiple domains is to just virtualize. With just 2 physical servers, you can run DCs for the Empty Root, and any domains under it, with full redundancy.
The way we do it at my office is to have one workstation in each department deemed a "Patch test" computer. 3 work days of use is more than enough to detect major issues. That just leaves us with servers to manually test.
It wasn't a security patch that did that.
A subtle reference is not as awesome once you point it out clear as day.
At 17,000 desktops, you should probably be running SMS or at least a tiered WSUS environment. It's not that hard to patch machines nightly, as long as you don't have them all going to a single poor WSUS server.
Unfortunately, I still have to "use" their software.
Hey, it's just a job. With the economy and all...
"Required by law" does not mean "required by an officer," it means whatever sobriety tests are required by the laws in your state governing implied consent. For example, in most states "field sobriety tests" such as the one-leg-stand are completely voluntary.
That's justifiable homicide, as far as I am concerned.
I worked at a company where our entire IT department (6 people) had an unofficial pact to quit together if management kept up its games. One day, it came to that. We all just left when we were told that unpaid overtime would be required on Saturdays to basically do manual labor in the warehouse.
They went out of business less than a month later, after spending nearly an entire month's cash flow on forensic network/systems engineering consultants.
Lazy? Odd choice of a word there. Most companies will terminate employment on the spot for off-the-clock or unapproved overtime. It's not a chance most IT workers want to take, especially for the type of boss that would call them lazy for expecting to be paid to work.
Management types like you give the rest of humanity a bad name.
Funny. We received a shipment of computers from a top-three desktop manufacturer (120 or so), and over the past 6 months we've had 14 HDDs go bad.
No, it's not environmental.