Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror

Comment Re:Not going to happen anytime soon (Score 1) 128

It's too easy and they refuse to change.

It's not just "easy". Fax is as secure as the phone network we pretend is secure, so if you act on a fax which appears to come from a specific phone number then you have some level of legal protection from liability. If you use a website or email then you are only as protected from liability as your identity verification system.

My monthly bank payments are electronic, but a few don't have bank account destinations, so it gets done via the bank's paper check service.

If I need to deposit a check, I take a photo of it with my cellphone using the bank's app and it gets processed just fine. The MICR font is highly OCRable, so as long as what else is written/printed on it is legible, everything works well. Even if a human has to review it because it was handwritten, they will only have to briefly glance at most checks. The only thing I actually write checks for any more is my rent. The paper check costs me very little and they cost nothing to deposit on the other end. I think the landlord is depositing them in person, because they seem to do them two or so at a time.

Comment Re:I still write about 15 checks a year... (Score 1) 128

E.g. Create a system to digitally scan a shared thing describing a transfer, but instead of using a standard QR code, keep using cheques.

You appear to have not read anything above your comment. I can't do a QR code by hand. I need a printer to produce one. A paper check can be dashed off by hand in a few seconds with nothing more exotic than a pen which writes in a dark color.

Or Adopt a system that finally eliminates the use of unsecured magnetic stripes on credit cards, but then keep the completely unsecure signature for verification.

We haven't even eliminated magstrips. We still have them around for backup. An attacker can disable a chip reader by making a special card that applies epoxy to the contacts when it's inserted, which you can do with e.g. a dremel, forcing subsequent users to fall back to the strip.

It's like a competition to see how close they can get to a good idea while still fucking up the implementation.

That's the US for you. Electoral college, scotus with no term limits, yada yada.

Comment Re:Just shows he does not really understand hardwa (Score 1) 75

One major difference, assuming you've got full platform support(should be the case on any server or workstation that isn't an utter joke; but can be a problem with some desktop boards that 'support' ECC in the sense that AMD didn't laser it off the way Intel does; but don't really care); is that ECC RAM can (and should) report even correctable errors; so you get considerably more warning than you do with non-ECC RAM.

If you pay no attention to error reports ECC or non-ECC are both rolling the dice; though ECC has better odds; but 'proper' ECC and Linux-EDAC support will allow you to keep an eye on worrisome events(normally with something like rasdaemon, not sure what other options and preferences there are in terms of aggregating the kernel-provided data) and, unless the RAM fails particularly dramatically and thoroughly, will give you much better odds of knowing that you have a hardware problem while that problem is still at correctable levels; so you can take appropriate action(either replacement, or on the really fancy server systems, some 'chipkill'-like arrangement where the specific piece of DRAM that is failing gets cut out of use when deeemed unreliable without having to bring the system down.

Comment Re:BSoD was an indicator (Score 1) 75

Sometimes you'd get a BSOD that was a fairly clear call to action; when the error called out something recognizable as the name of part of a driver; but that is mostly just a special case of the "did you change any hardware or update any drivers recently?" troubleshooting steps that people have been doing more or less blind since forever; admittedly slightly more helpful in cases where as far as you know the answer to those questions is 'no'; but windows update did slip you a driver update; or a change in OS behavior means that a driver that used to work is now troublesome.

Realistically, as long as the OS provides suitable support for being configured to collect actual crash dump material if you want it; it's hard to object too strongly to the idea that just rebooting fairly quickly is probably the better choice vs. trying to make the BSOD a genuinely useful debugging resource; especially given how rare it is for the person with useful debugging ability to happen to be at the console at the time of crash(rather than just an end user who is ill equipped to make sense of it; or a system that mostly does server stuff, quite likely not on actual physical hardware, where nobody has even touched the physical console in months or years; and it's more or less entirely useless to display a message there; rather than rebooting and hoping that things come up enough that management software can grab the dump files; or giving up and leaving the system in EMS so that someone can attach to that console.

Comment Re: Huh? (Score 0) 199

He's just being a typical American MORE BIGGER FASTER tool. I drive an 08 Versa with a 1.8l with 122hp and I have absolutely no problem being one of the fastest people on the road, because even a slow ass car by modern standards can do all the things. I never have trouble getting up to speed on a ramp or whatever.

Slashdot Top Deals

"If you lived today as if it were your last, you'd buy up a box of rockets and fire them all off, wouldn't you?" -- Garrison Keillor

Working...