Forgot your password?
typodupeerror

Comment: Re:its all about selling Autoloaders (Score 1) 124

by Cramer (#48464609) Attached to: Is LTO Tape On Its Way Out?

From the very origins of LTO... magnetic tracking marks, just like a hard drive, and floppies before that. If the servo tracking data is ever damaged or unreadable, the tape (and your data) is trash. No LTO drive ever sold can "format" a tape.

(Yes, it makes tapes cheap to manufacture. But above all, it means not paying Quantum for their patented laser optical tracking tech -- DLT has physical tracking marks on the back of the tape.)

Comment: Re:Shyeah, right. (Score 1) 124

by Cramer (#48464581) Attached to: Is LTO Tape On Its Way Out?

Actually, there's an enormous difference. Disc is designed for high capacity, and thus has insanely high bit densities. They rely on significant technology to work at all. With the bits so small and packed so close together, modern hard disks tend to self-destruct if not constantly maintained. (read: powered on and left to run recalibrations) Tape is designed for long term storage, so bigger bits, less densely packed. Tape will maintain the pattern written to it for a very long time.

If your tape drive doesn't work, it can be replaced (usually -- older tech can be a problem), and the tape(s) read perfectly from it. When your hard drive fails -- bearings, circuits, or (99.999999% of the time) the firmware the cheap bastards stored on the media becomes unreadable -- You. Are. Screwed. (options: 1) throw it away, 2) pay a data recovery company $$$$ to get your data back.)

Flash drives aren't magnetic storage.

Enterprises use disc backups for two simple reasons: cost and speed. In most cases, the data backed up will be obsolete in a few weeks or months. Anything that has to outlast the quarter finds it's way to more stable storage -- tape, cd/dvd/bluray (unwise, but still used), flash drives, and/or SSDs.

Comment: Re:Sue Them or Give Up (Score 1) 153

by Cramer (#48408045) Attached to: Ask Slashdot: Dealing With VoIP Fraud/Phishing Scams?

The CO (switch) never cared. Despite having the ability to check/reject CLID values, no one ever has. Today, with SIP and soft switches, it's even easier, and they still don't do it. (I bet your voip.ms personal account could send out whatever it wants -- not a cutomer, so I don't know.)

Comment: Re:Sue Them or Give Up (Score 1) 153

by Cramer (#48408037) Attached to: Ask Slashdot: Dealing With VoIP Fraud/Phishing Scams?

There is no technological solution.

There is, and always has been. With a simple POTS line, there's no means for the caller to manipulate anything -- it's all set by the serving switch. With ISDN (PRI and to some extent BRI), the caller was allowed to set CLID fields to indicate which "extension" is calling, ANI would be set by the switch to indicate the billing number for the line, however, your phone doesn't show ANI (even if it's a ISDN phone.) ISDN was expensive, so only a business would have them, and businesses could be trusted to not abuse the feature. That has worked out so well. :-)

Every phone switch I'm aware of supports limiting what's allowed for CLID. It's obvious most (all?) telcos cannot be bothered to use this feature.

Comment: Re:Level3? (Score 1) 153

by Cramer (#48407927) Attached to: Ask Slashdot: Dealing With VoIP Fraud/Phishing Scams?

IF you take the call directly from a scammer, and the SIP call is completed...

And just who in their right mind allows random SIP traffic from the internet to reach their PBX? ABSOLUTELY FUCKING NO ONE! Page one, step one of toll-fraud: allow access only from authorized sources. So, if a SIP call is "completed", it came from your phone service provider.

If they're spoofing the caller-id, then you have NO WAY to know where it came from. Only a "trap and trace" can follow it back, hop by hop, to the origin -- one switch at a time, one provider at a time, all the way back to China (or where ever.) That's the basis for the hollywood phone trace, but in reality, it takes people combing through records to see what's going on. (unless it's crossing metered lines, in the US, it's almost a certainty no CDRs are being generated and/or recorded, and even then, only for the segment that's metered -- eg. your cellphone.)

Comment: Re:Well, I for one feel safer... (Score 1) 328

by Cramer (#48407807) Attached to: Former Police Officer Indicted For Teaching How To Pass a Polygraph Test

"Secret" is the most basic of our (US) government clearances. It's an entirely clerical check. It's not like you're being authorized for nuclear launch codes, but something closer to knowing phone numbers and extensions for people's desks.

(I've had a "secret clearance"; it was the .gov's equiv of an NDA.)

Comment: FOUND IT! (Score 1) 405

by Cramer (#48382835) Attached to: Ask Slashdot: How To Unblock Email From My Comcast-Hosted Server?

/ip-log/karma.log.11:virus 23.31.69.157 fimble.com NOTQUIT [S=5 - FakeMX NoQuit] X=tarbaby H=mail.fimble.com [23.31.69.157] HELO=[fimble.fimble.com] F=[lollypop@fimble.com] T=[terrydw@mkl.com] S=[Feeling adventurous tonight? Multiple mega hot lasses, free access!]

Hostkarma still had it in the logs.

You sent junk mail; you got blacklisted. Nothing more to see here.

Comment: Re:First step is to collect data. (Score 1) 405

by Cramer (#48382739) Attached to: Ask Slashdot: How To Unblock Email From My Comcast-Hosted Server?

Unless you've been keeping detailed records long BEFORE the event(s) that triggered your blacklisting, odds are you'll have no record of what actually caused it. With Yahoo, you may not even know who was sent what, so you don't know who might have clicked the "spam" button. (and it used to be far to easy for complete idiots to click spam instead of delete, and not have any idea the difference between them.)

NET-23-30-0-0-1 was assigned to Comcast Business two and a half years ago. Your (apparent) netblock [NET-23-31-69-152-1] was assigned to you about a year ago. If anti-spam outfits were, as you claim, blocking all Comcast addresses, you'd've been blocked from day-one. The fact that you weren't, and have now mysteriously been blocked very strongly suggests something occurred from within your netblock to cause it. That means ANY device within your network could be the "bad apple".

Comment: s/flag/command/ (Score 3, Informative) 245

by Cramer (#48365737) Attached to: ISPs Removing Their Customers' Email Encryption

It's not a flag, it's a command. Support for the feature is signaled after the client hello (EHLO). It's not just hiding the indicator in the hello, but actively blocking the command.

The issue Goldenfrog whined about was a simple oversight from Cricket Wireless(?). That's the default behavior (even today) for Cisco firewalls -- which is why everyone with a clue disables (or at least tweaks) that idiotic inspection rule.

Comment: Re:Science fiction comes to life, again (Score 1) 176

by Cramer (#48355403) Attached to: The Disgruntled Guys Who Babysit Our Aging Nuclear Missiles

Right. Manned by a pair of people inside a bunker that would take days to breach from the outside -- by design. One of the goes nuts and kills the other, he's got plenty of time to rig shit. Someone on the surface would have to notice this, and then get maintenance crews to the site(s) and into the silo(s) to physically disable the launchers. Every step in that chain is measured in multiple HOURS -- assuming anyone outside even notices before a missile comes flyin' out.

Ever notice that even the busiest people are never too busy to tell you just how busy they are?

Working...