The ~50Hz hum you're hearing is actually 60Hz AC. This is usually caused by a ground loop. It can be eliminated using a ground loop isolator or (more cheaply) hooking the stereo and computer to the same power strip. Removing the ground connection from the computer via a 2-prong to 3-prong adapter can also eliminate it (although you're not supposed to do that.:)
Any tech and any ISP will do anything they can to eliminate anything between your computer and the cable modem/cpe/whatever to eliminate variables.
If you pay enough money, you can get an ISP that calls you in less than 10 minutes if your circuit goes down. They don't tell you to reboot your computer, they don't tell you to doublecheck your workgroup name, they look at the alarm light on their router's interface and call the telco for you.
It doesn't matter how cheap the equipment is, or whether it's "for consumers", BLINDLY REBOOTING EQUIPMENT IS NOT THE ANSWER. If the crappy cable modem on your end is overheating and needs rebooting every 2 weeks, they should replace the modem. If DOCSIS authentication isn't happening because @home needs to unfuck their gateway, rebooting won't help anyway, it'll just make your cable modem try to sync endlessly until the gateway becomes unfucked. If your Windows PC suddenly forgot how to do TCP/IP, there's a bug that needs to be addressed and probably a patch to address it. Etc, etc etc.
All dns verification systems such as tcp wrappers and ssh will work as long as the reverse dns hostname for your ip address resolves to the same ip.
For example, take a random cable modem user (if you have the itch to portscan someone, PLEASE pick your own completely random ips), 24.5.2.24. This address reverses to cx54499-b.dt1.sdca.home.com, which in turn resolves to 24.5.2.24.
That machine may host example.com and example.net... You'll still be able to ssh to example.com and example.net, send mail to them, or do whatever, even though 24.5.2.24 does not reverse to example.com or example.net.
make -n install used to be really useful, but now most apps that use autoconf have an install target that iterates over several directories and output several hundred lines of junk. You really have to know what you're doing to find out what it's doing. I'd hate to have to use that feature to determine if something malicious was in there.
For those kind of apps, it's faster to build a chroot (Debian chroots are really simple to make - unpack the base2_2.tgz to a dir somewhere, cd to it, and do chroot . bin/bash), make a copy of it, then do rsync --dry-run --verbose or diff -u --recursive on the two dirs to find out what changed.
What I usually do with abcde is generate a playlist (which is created before any of the tracks are read), wait for one or two tracks to encode, and then play the list in any playlist-capable player. By the time the player gets to the next track, that track would have finished encoding.
abcde1.9.x can do non-interactivity and you can even add all the track titles when you're done if there's no CDDB entry. Plus there's Ogg support, you can format the filenames any way you please, and you can use other machines for remote encoding.
Nobody flies 747's upside down because the plane is not designed to do stunts - I don't know what its negative G rating is but I do know it's only rated for 2.5G's positive G's (most aerobatic planes are rated for +/-12 - some properly trained humans can tolerate up to +9 for short periods, and some of the big roller coasters pull +2 G's now). If it's only rated for something like -1.2G's, flight upside down only leaves you with.2G's of wiggle room before the wings tear off.
How to get mail to @microsoft.com with postfix
on
Microsoft's DNS Down
·
· Score: 2
My day job's responsibilities include making sure mail from us actually gets to Microsoft, so here's what we did on our postfix mail gateway - I figure others out there would like to know how to do the same thing.
Create an/etc/postfix/transport file with the contents:
(.124 is mail2.microsoft.com;.125 is mail1, which is apparently down right now.)
Put this in your/etc/postfix/main.cf:
transport_maps = hash:/etc/postfix/transport
Reload or restart postfix and have it flush all the mail. It might take a while, especially if you have a lot of mail queued up. To speed things up, try these two settings:
You will still be able to do that, but as for the people running servers with disk arrays that are a significant fraction of a terabyte, well, they need the choice of being able to bring the server up now rather than waiting several hours (or days) for an fsck to finish.
For an array where you've promised 99.99% uptime (an hour a year), you simply can't check it like that. You wait until you can upgrade the array to new hardware that you can start with a fresh filesystem on.
For the less extreme circumstances, it's still nice to be able to plan downtime for this. That way you can schedule it to automatically happen Thanksgiving day instead of when someone trips over the power cord.
And yes, you are correct that having filesystem integrity does not necessarily mean you also have file integrity. You can't do much about that unless you go the VMS route of keeping versions of files around.
Make a plausible (legal) replacement for what was encrypted, use chaffing to place both items in the same file along with a bunch of other random garbage, and when they ask for the passphrase, give them the one that decodes the file to the birdwatching tapes you've been recording.
If you do it properly they won't be able to prove there's any other data there. There's not much to tell them it's 32x chaff instead of 64x chaff.
Command-line based, can be non-interactive, has support for all the major encoders + distmp3 remote encoding support, does cddb, playlists, id3 tagging, customizable output filenames, etc.
Some people use it with
autocd
for that truly hands-off feel.
Any package marked with a Priority: of "standard" or higher is automatically selected for install by dselect if it's a new package (everything is a new package at install time). AFAIK this isn't customizable.
At one point in time I tried to get tex and emacs pulled from standard, but I never got the concensus necessary from the policy cabal to carry out my evil schemes. Oh well.
Wonderful. I'm not familiar enough with the intricacies of the MD5 algorithm to know exactly how many bits of input randomness are needed to guarantee the full 128 bits of output randomness, but the several hundred bits you're using above should be plenty.
How do you store the random 56 character string so you can verify it later though? If you need to put all these pieces back together again at a later date, and the only thing the customer is entering is the credit card number, you have to store the other pieces in cleartext or a cleartext-equivalent. If the hypothetical cracker can get their paws on that table and the customer id table, you're back to a few dozen bits to bruteforce.
Does a lot of talking make your system more insecure, or does it just make you feel insecure?
It is much safer to be frightened by talk and let the fear drive you to education than to wallow in ignorance.
Anyway, please check http://security.debian.org/ if you're using Debian.
Making a network more secure requires an admin to think of what could possibly happen in any situation. For example once upon a time in a land far far away, someone pondered:
"Hmmm, packet sniffers make it possible for someone else on a network to capture transmitted data."
"Waitasec, telnet is unencrypted! Everything is sent out in the clear."
"Maybe I should stop typing in my passwords via telnet to access a machine remotely."
Slashdot Mirror
DL360's have two PCI slots.
The ~50Hz hum you're hearing is actually 60Hz AC. This is usually caused by a ground loop. It can be eliminated using a ground loop isolator or (more cheaply) hooking the stereo and computer to the same power strip. Removing the ground connection from the computer via a 2-prong to 3-prong adapter can also eliminate it (although you're not supposed to do that. :)
If you pay enough money, you can get an ISP that calls you in less than 10 minutes if your circuit goes down. They don't tell you to reboot your computer, they don't tell you to doublecheck your workgroup name, they look at the alarm light on their router's interface and call the telco for you.
It doesn't matter how cheap the equipment is, or whether it's "for consumers", BLINDLY REBOOTING EQUIPMENT IS NOT THE ANSWER. If the crappy cable modem on your end is overheating and needs rebooting every 2 weeks, they should replace the modem. If DOCSIS authentication isn't happening because @home needs to unfuck their gateway, rebooting won't help anyway, it'll just make your cable modem try to sync endlessly until the gateway becomes unfucked. If your Windows PC suddenly forgot how to do TCP/IP, there's a bug that needs to be addressed and probably a patch to address it. Etc, etc etc.
</rant>
A quick google search reveals amplitude modulation was first demonstrated in 1906.
Of course, AC3 isn't just about finding a way to encode 6 channels of discrete audio in one signal.
For example, take a random cable modem user (if you have the itch to portscan someone, PLEASE pick your own completely random ips), 24.5.2.24. This address reverses to cx54499-b.dt1.sdca.home.com, which in turn resolves to 24.5.2.24.
That machine may host example.com and example.net... You'll still be able to ssh to example.com and example.net, send mail to them, or do whatever, even though 24.5.2.24 does not reverse to example.com or example.net.
For those kind of apps, it's faster to build a chroot (Debian chroots are really simple to make - unpack the base2_2.tgz to a dir somewhere, cd to it, and do chroot . bin/bash), make a copy of it, then do rsync --dry-run --verbose or diff -u --recursive on the two dirs to find out what changed.
It needs to be run after the cd is in. It has no "waiting state". I'd recommend running it from something like autorun.
What I usually do with abcde is generate a playlist (which is created before any of the tracks are read), wait for one or two tracks to encode, and then play the list in any playlist-capable player. By the time the player gets to the next track, that track would have finished encoding.
Email the compile errors to me (not just the "make : *** [target] Error 1" stuff please) and I'll see if I can help.
Disclaimer: I wrote abcde.
Sustained level inverted flight in calm air generates exactly -1G.
Those big jets do fly upside down though.
Create an /etc/postfix/transport file with the contents:
microsoft.com smtp:[131.107.3.124]
.microsoft.com smtp:[131.107.3.124]
(.124 is mail2.microsoft.com; .125 is mail1, which is apparently down right now.)
Put this in your /etc/postfix/main.cf:
transport_maps = hash:/etc/postfix/transport
Reload or restart postfix and have it flush all the mail. It might take a while, especially if you have a lot of mail queued up. To speed things up, try these two settings:
default_destination_concurrency_limit = 200
qmgr_site_hog_factor = 100
For an array where you've promised 99.99% uptime (an hour a year), you simply can't check it like that. You wait until you can upgrade the array to new hardware that you can start with a fresh filesystem on.
For the less extreme circumstances, it's still nice to be able to plan downtime for this. That way you can schedule it to automatically happen Thanksgiving day instead of when someone trips over the power cord.
And yes, you are correct that having filesystem integrity does not necessarily mean you also have file integrity. You can't do much about that unless you go the VMS route of keeping versions of files around.
Lots of people.
unsigned char *a="\x98mWPS\x1\x87hSJH\0159F",b;main(){for(;b+=*a ++-80;putchar(b));}
If you do it properly they won't be able to prove there's any other data there. There's not much to tell them it's 32x chaff instead of 64x chaff.
If your CD duplicator is a bunch of drives hooked up via a SCSI bus, you'll find abcde extremely handy for this.
http://frantica.lly.org/~rcw/abcde/page/
Command-line based, can be non-interactive, has support for all the major encoders + distmp3 remote encoding support, does cddb, playlists, id3 tagging, customizable output filenames, etc.
Some people use it with autocd for that truly hands-off feel.
In this instance, that's wishful thinking, see: #15865, #24950, #65690.
Any package marked with a Priority: of "standard" or higher is automatically selected for install by dselect if it's a new package (everything is a new package at install time). AFAIK this isn't customizable.
At one point in time I tried to get tex and emacs pulled from standard, but I never got the concensus necessary from the policy cabal to carry out my evil schemes. Oh well.
How do you store the random 56 character string so you can verify it later though? If you need to put all these pieces back together again at a later date, and the only thing the customer is entering is the credit card number, you have to store the other pieces in cleartext or a cleartext-equivalent. If the hypothetical cracker can get their paws on that table and the customer id table, you're back to a few dozen bits to bruteforce.
For example, with potassium-argon dating, how do we:
- know that potassium-40's half-life is 1.3 billion years? Even over 10 years, that's a part-per-billion experiment.
- know that there wasn't argon trapped in the rock along with the potassium in the first place?
Some good scientists admit these assumptions up front, for example http://www.icr.org/research/sa/sa-r03.htm clearly says:Also, how are half-lifes measured to millions of years? We've only known about this stuff for about 100 years...
Intel is releasing a chip that will require modifications to ATX.
Therefore, it would be worthwhile to assume this chip will consume over 100 watts.
The idea of the game is that you start at a web page of a competitor's choice and compete to find smut the fewest number of links away.
Bookmark pages, search engines, etc, are off limits as they make the game too easy.
Does a lot of talking make your system more insecure, or does it just make you feel insecure?
It is much safer to be frightened by talk and let the fear drive you to education than to wallow in ignorance.
Anyway, please check http://security.debian.org/ if you're using Debian.
Making a network more secure requires an admin to think of what could possibly happen in any situation. For example once upon a time in a land far far away, someone pondered:
"Hmmm, packet sniffers make it possible for someone else on a network to capture transmitted data."
"Waitasec, telnet is unencrypted! Everything is sent out in the clear."
"Maybe I should stop typing in my passwords via telnet to access a machine remotely."