Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: Re:Hopefully the applicants had a relevent backrou (Score 1) 809

Asking whether the document is PDF or Excel demonstrates a lack of understanding. The document type is irrelevant. It is a file of bytes. You want to send those bytes securely. (And you may want the receiver to be able to verify that it actually came from you.)

It demonstrates either a lack of understanding or more than a passing familiarity with the applications. MS Office has used AES for the built-in encryption since Office 2007. That would seem like a reasonable choice for sending a file to a contact, provided you choose a strong password and communicate it out-of-band.

Comment: Re:The former iPhone user is an idiot. (Score 1) 238

by Daniel Boisvert (#47024795) Attached to: Apple To Face Lawsuit For iMessage Glitch

They could change the timeouts. If an iMessage is sent to a destination that's a phone number (instead of an email address), and a device configured to receive messages for that phone number has not checked in within the past 5-7 days, deactivate iMessage for that phone number until a configured device checks in again.

I agree this is mostly user error and haven't had any problems resolving it for people who've asked me about it, but people don't typically anticipate this result when switching phones, so containing the undesired effects to a shorter transition window would seem like a helpful thing to do.

Comment: Re:But is it even usable? (Score 1) 208

IMHE tape is always an order of magnitude slower than the advertized speed, so it is likely even worse than what you calculated.

If your tapes are writing that slowly, something is wrong, and I'd be worried about shoe-shining. Without putting much effort into it, my LTO5 jobs currently run at around 125-135MB/s. With modern tape, it helps a lot to stage to disk first, or get software that can multiplex backup streams to keep the tape buffers fed.

Comment: Re:xp still works (Score 1) 520

by kernelistic (#44519291) Attached to: China Has a Massive Windows XP Problem

Windows 1.0, 2.0, 3.0, 3.11, 9x & ME were indeed built on top of DOS, but NT certainly wasn't! DOS on NT actually runs in NTVDM. DPMI (32-bit DOS) is also emulated through thunking to NT APIs.

For the uninitiated, Dave Cutler joined Microsoft in 1988 as a design lead for NT, long after Windows 1.0 was out. This chap also happens to have been instrumental in the design of VMS at DEC from 1975 to 1988. His Wikipedia bio is quite interesting.

Comment: Re:Makes sense (Score 1) 566

by kernelistic (#44238095) Attached to: HTTP 2.0 Will Be a Binary Protocol

I'm in the same boat in terms of diagnosis tools. You may already know this: PuTTY supports opening both telnet and raw TCP sessions.

The awesome thing about HTTP is its extensibility but changing to a binary protocol may make compat an interesting thing. I am interested in knowing how clients in particular are expected to operate when talking to 1.1 only servers.

"You're a creature of the night, Michael. Wait'll Mom hears about this." -- from the movie "The Lost Boys"

Working...