I still have a Newton that works, but I only show it to people for comic value.
I've never had problems with the battery compartment. It lasts for quite a long time on a set of AA batteries. Until you put an 802.11 PCMCIA card in it, that is, then you're lucky to get 2 hours out of it.
Unlikely. Most charities are scams charging outrageous "administration fees" that get redirected to the accounts of a few select ass-hats. If you actually want to help people out the best thing you can do is assist them directly - donate your time/money/wares in person.
Has anyone conducted an experiment using an artificial 'arm', with a constant pressure pulsing through it? That would be a much better way to determine relative accuracy.
I had wondered the same thing myself. It would seem to be a sane way to have a standardised test for devices. There's probably some degree of difficultly in simulating Korotkoff sounds and other idiosyncrasies that the devices are attempting to measure.
But Intel never had any problems w/ other CPUs like Alpha or MIPS trying to emulate x86, and those chips were far more powerful than ARM. It's bizarre that they'd object to this.
Hardly. By comparison Alpha and MIPS were niche/hobbyist processors very low numbers in the marketplace. ARM is ubiquitous and is a serious threat to Intel sales if it can emulate x86.
Why, certainly that would be because they didn't start soldering RAM in until 2012.
I have a Late 2013 iMac that proves otherwise. Apple couldn't (wouldn't) supply it with 32GB so I bought some Kingston RAM from Umart and upgraded it myself. There's a small door to access the SODIMM slots on the back of the iMac right beside the IEC power socket.
If you feel like getting a pizza cutter out you can also remove the glass display panel from the iMac frame and upgrade the SATA hard disk (or SSD) yourself. iFixit even have upgrade kits for this as Apple does funny business with the temperature sensors (over the SATA connection) on their OEM drives. If you don't get the iFixit temperature sensor dongle then the iMac's fan will go into "safe mode" and run at full speed to protect the system from over-temperature damage.
Siri is certainly better than it was a few years ago but it still does brain dead things like trying to route you to another continent when you ask "How do I drive to..." where "..." is usually just a suburb or three away.
The amount of background noise seems to be the determining factor: if I don't turn off the radio, wind the windows up and speak with about 1/2 second gaps between my words then I'll have to dictate messages to it three or four times before it gets them correct enough to actually send them.
Microsoft IIS (can't remember whether it was 3 or 4) had a similar bug where after ~49 days it would stop logging web site activity to the W3C format log files. Doesn't look like MSDN still has a KB article for it otherwise I would have linked it.
If you read TFA you'd have noticed that Microsoft isn't using Vanilla Git. Using their normal embrace-extend-extinguish mindset they've created their own GVFS (Git Virtual File System) and forks of Git server and client that only work in a GVFS-enabled ecosystem so that they can handle the massive number of files in the Windows source code.
IMO this, right here, is why Imzy didn't survive - lack of exposure.
I can't find any story submissions on/. that refer to Imzy, only this story and the one announcing its existence 13 months ago... Fired Reddit Exec Launches Competing Site.
You could have the greatest thing ever (e.g.: solving poverty, clean power generation and world hunger) but it's never going to make a difference if nobody actually knows about it.
This is absolutely a Windows problem. It's Windows Explorer initiating the connection and it should *not* be doing that for any files that have a Zone.Identifier alternate data stream (i.e.: any file downloaded from the internet that hasn't yet had the Unblock button clicked in its Properties tab).
How does it mean anything? Most (decent) Wi-Fi routers for sale now days support both public and private Wi-Fi networks, usually on both 2.5G and 5G bands.
Local printers vanish as thier connections are disabled, with office 365 and outlook down for so long those caches get flushed, etc.
We had a large percentage of Win10 computers stop working with one or more network printers after the Anniversary update. They could access the affected printers' web management pages, could telnet to the affected printers' IPP ports, but the printer icons had disappeared from the Printers control panel applet and could not be re-added via the Add Printers wizard. We've never solved it, but my suspicion is that GUI settings got trashed in the upgrade and there's still some evidence of the prior printer registrations in the Registry preventing them from appearing again in the Add Printers wizard.
There are still plenty of people in Australia on 512/64kbps ADSL(1) and 56kbps POTS connections. NBN was only meant to cover 95% of the population, that being those in the six major metropolitan centres covering less than 1% of the landmass.
Dayboro, itself only about 30km away from the Brisbane CBD, only has ADSL1 connectivity in its exchange. Drive 5km northwest of that and you have no ADSL, no POTS, no CDMA coverage and no sewerage. Another 2km and you also have to provide your own power and water.
I agree with the "just wipe it" sentiment. Android and iOS devices can back up to the cloud. Just erase the device when going through customs and restore it after coming out the other side.
Customs: "Why hasn't this device been setup yet?"
Traveler: "I just bought it and don't have my Google/Apple-ID details with me."
Do you even need iTunes to deal with an iPhone these days.
Not really, unless you want to do playlist management. iOS devices can back themselves up to the cloud now, perform iOS upgrades and do pretty much everything else without a PC.
I never said there were not easier ways to infiltrate computers. If you actually read what I replied to I was pointing out that the parent put far too much faith in the ability of X.509 certificates and SSL and HTTPS, apparently assuming that they are the cure-all for MITM attacks when, in fact, they most definitely are not. (At least not as currently implemented.)
I think maybe your head is in the sand if you can't see how SNI weakened TLS as a security protocol. SNI was created because Web Hosters and businesses didn't want to keep paying for additional IPv4 address space - prior to that you could only host a single SSL/TLS-enabled web site on any given IPv4's tcp/443. Instead of migrating everybody to IPv6 where every host could have a unique address they pushed for SNI to add HTTP Host-like header capabilities to TLS.
Your premise that SNI is not a huge problem is only valid if, and only if, you can guarantee that every single trusted root certificate (and every single Server Identity capable intermediate certificate signed by them) has never been compromised by an attacker. Show me any US-based Certificate Authorities issuing NSL canaries and the like. Some CAs don't even specify a maximum chain length on their root/intermediate certificates.
If you'd like to see a practical HTTPS man-in-the-middle demonstration on your favorite Windows desktop just install Telerik's Fiddler tool and enable the HTTPS Intercept option. This installs its own certificate into your Trusted Root Certificate store and then re-encrypts all of your HTTPS connections so you can inspect the traffic.
The default settings of SSL/TLS libraries on most operating systems make man-in-the-middle attacks trivial. When an SSL/TLS session is negotiated only the following things are validated:
The origin server certificate trust chain is ultimately signed by a Trusted Root certificate - any trusted root certificate.
The valid-from and valid-to dates on the certificate are current.
The desried host name is in the Subject or SubjectAlt fields, which is a useless check with 0% value.
So, why would I say that the host name check is a useless check with 0% value? Because TLS has been neutered since SNI was introduced (RFC 3546 Transport Layer Security Extensions # Server Name Indication). Before then SSL/TLS was "reasonably secure" but since then it is virtually worthless. Under SNI the connecting client tells the origin server which host name it is connecting to and, thanks to that gaping hole, the origin server (or any man-in-the-middle appliance) has enough information to either generate a fake certificate or pull one out of its cache.
HTTPS will keep a client from pulling updates from the wrong server.
No it doesn't. You put too much faith in HTTPS.
The default HTTPS providers on most operating systems only verify that the provided origin server certificate chain has been signed by a known trusted root and that the valid-from and valid-to dates are current. CRL checks are off by default because they require extra network traffic (which generally occurs over HTTP - go figure).
The above behaviours are required for man-in-the-middle re-encrypting proxy appliances, like those from Blue Coat Systems, Inc., to work correctly in corporate environments.
Any additional checks are up to individual applications, such as confirming that the trusted root is one that you expected (not BCSI), or that the origin certificate thumbprint is what you expected, etc.
I'd be suspecting that their business model depends on short-term investments. i.e.: they receive weekly or fortnightly payments from the recruiting companies and use at least the superannuation portion of that on short-term money markets until they do the deposits into the superannuation accounts at the end of the month. This is much like banks do with cheques while they're "processing payments" for 3-7 days in our modern, instant transfers, electronic payments society.
Slashdot Mirror
I still have a Newton that works, but I only show it to people for comic value.
I've never had problems with the battery compartment. It lasts for quite a long time on a set of AA batteries. Until you put an 802.11 PCMCIA card in it, that is, then you're lucky to get 2 hours out of it.
Well, ... the charities will rot in heaven.
Unlikely. Most charities are scams charging outrageous "administration fees" that get redirected to the accounts of a few select ass-hats. If you actually want to help people out the best thing you can do is assist them directly - donate your time/money/wares in person.
Has anyone conducted an experiment using an artificial 'arm', with a constant pressure pulsing through it? That would be a much better way to determine relative accuracy.
I had wondered the same thing myself. It would seem to be a sane way to have a standardised test for devices. There's probably some degree of difficultly in simulating Korotkoff sounds and other idiosyncrasies that the devices are attempting to measure.
But Intel never had any problems w/ other CPUs like Alpha or MIPS trying to emulate x86, and those chips were far more powerful than ARM. It's bizarre that they'd object to this.
Hardly. By comparison Alpha and MIPS were niche/hobbyist processors very low numbers in the marketplace. ARM is ubiquitous and is a serious threat to Intel sales if it can emulate x86.
Why, certainly that would be because they didn't start soldering RAM in until 2012.
I have a Late 2013 iMac that proves otherwise. Apple couldn't (wouldn't) supply it with 32GB so I bought some Kingston RAM from Umart and upgraded it myself. There's a small door to access the SODIMM slots on the back of the iMac right beside the IEC power socket.
If you feel like getting a pizza cutter out you can also remove the glass display panel from the iMac frame and upgrade the SATA hard disk (or SSD) yourself. iFixit even have upgrade kits for this as Apple does funny business with the temperature sensors (over the SATA connection) on their OEM drives. If you don't get the iFixit temperature sensor dongle then the iMac's fan will go into "safe mode" and run at full speed to protect the system from over-temperature damage.
Siri is certainly better than it was a few years ago but it still does brain dead things like trying to route you to another continent when you ask "How do I drive to ..." where "..." is usually just a suburb or three away.
The amount of background noise seems to be the determining factor: if I don't turn off the radio, wind the windows up and speak with about 1/2 second gaps between my words then I'll have to dictate messages to it three or four times before it gets them correct enough to actually send them.
Microsoft IIS (can't remember whether it was 3 or 4) had a similar bug where after ~49 days it would stop logging web site activity to the W3C format log files. Doesn't look like MSDN still has a KB article for it otherwise I would have linked it.
I'd be saying, "Sure, but we're going to shut down all GovCloud regions. One level of encryption for everybody."
If you read TFA you'd have noticed that Microsoft isn't using Vanilla Git. Using their normal embrace-extend-extinguish mindset they've created their own GVFS (Git Virtual File System) and forks of Git server and client that only work in a GVFS-enabled ecosystem so that they can handle the massive number of files in the Windows source code.
IMO this, right here, is why Imzy didn't survive - lack of exposure.
I can't find any story submissions on /. that refer to Imzy, only this story and the one announcing its existence 13 months ago... Fired Reddit Exec Launches Competing Site.
You could have the greatest thing ever (e.g.: solving poverty, clean power generation and world hunger) but it's never going to make a difference if nobody actually knows about it.
This is absolutely a Windows problem. It's Windows Explorer initiating the connection and it should *not* be doing that for any files that have a Zone.Identifier alternate data stream (i.e.: any file downloaded from the internet that hasn't yet had the Unblock button clicked in its Properties tab).
How does it mean anything? Most (decent) Wi-Fi routers for sale now days support both public and private Wi-Fi networks, usually on both 2.5G and 5G bands.
We had a large percentage of Win10 computers stop working with one or more network printers after the Anniversary update. They could access the affected printers' web management pages, could telnet to the affected printers' IPP ports, but the printer icons had disappeared from the Printers control panel applet and could not be re-added via the Add Printers wizard. We've never solved it, but my suspicion is that GUI settings got trashed in the upgrade and there's still some evidence of the prior printer registrations in the Registry preventing them from appearing again in the Add Printers wizard.
There are still plenty of people in Australia on 512/64kbps ADSL(1) and 56kbps POTS connections. NBN was only meant to cover 95% of the population, that being those in the six major metropolitan centres covering less than 1% of the landmass.
Dayboro, itself only about 30km away from the Brisbane CBD, only has ADSL1 connectivity in its exchange. Drive 5km northwest of that and you have no ADSL, no POTS, no CDMA coverage and no sewerage. Another 2km and you also have to provide your own power and water.
I agree with the "just wipe it" sentiment. Android and iOS devices can back up to the cloud. Just erase the device when going through customs and restore it after coming out the other side. Customs: "Why hasn't this device been setup yet?" Traveler: "I just bought it and don't have my Google/Apple-ID details with me."
Bought a new car in the last decade? How much phone-home telemetry do you think there is in the average Ford infotainment system versus Windows 10?
Oh for the love of mod points...
Not really, unless you want to do playlist management. iOS devices can back themselves up to the cloud now, perform iOS upgrades and do pretty much everything else without a PC.
Will it have a headphone jack?
Yes, this. Obviously marketroids are trying to make us think that suede-like fabrics constructed from petrochemical fibres are somehow... luxury!
I never said there were not easier ways to infiltrate computers. If you actually read what I replied to I was pointing out that the parent put far too much faith in the ability of X.509 certificates and SSL and HTTPS, apparently assuming that they are the cure-all for MITM attacks when, in fact, they most definitely are not. (At least not as currently implemented.)
I think maybe your head is in the sand if you can't see how SNI weakened TLS as a security protocol. SNI was created because Web Hosters and businesses didn't want to keep paying for additional IPv4 address space - prior to that you could only host a single SSL/TLS-enabled web site on any given IPv4's tcp/443. Instead of migrating everybody to IPv6 where every host could have a unique address they pushed for SNI to add HTTP Host-like header capabilities to TLS.
Your premise that SNI is not a huge problem is only valid if, and only if, you can guarantee that every single trusted root certificate (and every single Server Identity capable intermediate certificate signed by them) has never been compromised by an attacker. Show me any US-based Certificate Authorities issuing NSL canaries and the like. Some CAs don't even specify a maximum chain length on their root/intermediate certificates.
If you'd like to see a practical HTTPS man-in-the-middle demonstration on your favorite Windows desktop just install Telerik's Fiddler tool and enable the HTTPS Intercept option. This installs its own certificate into your Trusted Root Certificate store and then re-encrypts all of your HTTPS connections so you can inspect the traffic.
You put far too much faith in HTTPS.
The default settings of SSL/TLS libraries on most operating systems make man-in-the-middle attacks trivial. When an SSL/TLS session is negotiated only the following things are validated:
So, why would I say that the host name check is a useless check with 0% value? Because TLS has been neutered since SNI was introduced (RFC 3546 Transport Layer Security Extensions # Server Name Indication). Before then SSL/TLS was "reasonably secure" but since then it is virtually worthless. Under SNI the connecting client tells the origin server which host name it is connecting to and, thanks to that gaping hole, the origin server (or any man-in-the-middle appliance) has enough information to either generate a fake certificate or pull one out of its cache.
HTTPS will keep a client from pulling updates from the wrong server.
No it doesn't. You put too much faith in HTTPS.
The default HTTPS providers on most operating systems only verify that the provided origin server certificate chain has been signed by a known trusted root and that the valid-from and valid-to dates are current. CRL checks are off by default because they require extra network traffic (which generally occurs over HTTP - go figure).
The above behaviours are required for man-in-the-middle re-encrypting proxy appliances, like those from Blue Coat Systems, Inc., to work correctly in corporate environments.
Any additional checks are up to individual applications, such as confirming that the trusted root is one that you expected (not BCSI), or that the origin certificate thumbprint is what you expected, etc.
I'd be suspecting that their business model depends on short-term investments. i.e.: they receive weekly or fortnightly payments from the recruiting companies and use at least the superannuation portion of that on short-term money markets until they do the deposits into the superannuation accounts at the end of the month. This is much like banks do with cheques while they're "processing payments" for 3-7 days in our modern, instant transfers, electronic payments society.