This was an advisory referendum only, with no force of law. The United Kingdom is not obligated to leave the EU.
Yes, a pro-separation change in government will soon take place. However, the more forcefully that the new government pushes for a full departure, the more forcefully Scotland and Northern Ireland will attempt to disentangle themselves from the United Kingdom.
Northern Ireland in particular might see a real increase in sectarian violence if EU separation is not handled with great care, so internal security and continental policy will become even deeper-entwined. These forces will certainly blunt immediate impulses towards separation.
The EU bureaucracy has allowed a large, hostile contingent to form in several European nations. Perhaps now an inward gaze, compelled by credible criticism, can form a more perfect union.
Tinfoil now crashes when you attempt to use messenger, and there is no commentary from the developer if he can/will fix it.
I suggest that you examine the Face Slim client on F-Droid. He has released a recent, new version which solves the messenger problem.
I do need a client that will upload photos on KitKat. If I can find that, then the official Facebook client is history on all of my devices - their code is no longer welcome.
-Xprivacy, a module in the Xposed framework, can be used to deny location access to any application, including Facebook. Your phone must be rooted to install Xposed modules.
-Cyanogenmod PrivacyGuard has a similar feature. You must erase your OEM operating system to install Cyanogenmod.
-3rd-party Facebook clients:
-Face Slim is very current, with patches in the last few days to deal with Facebook's messenger "night of the long knives."
-Tinfoil is the best-known skeleton client, but has been recently silent on the messenger issue. The app currently crashes if you try to use messenger functions.
-Several closed-source Facebook clients can be found in the Play store, who MIGHT respect your privacy.
I'm advising anyone of importance to contact me through other channels. I have Tinfoil forced to desktop mode so I can see anything sent to me.
I had pondered forcibly enabling messenger in the Facebook APK (for Android), but I really don't want to rely on Facebook corporate anymore. I need to move away from their network.
I've never advised anyone to load fb-messenger, and I never will.
I live in an older neighborhood with a brick street. Some sections don't have the best maintenance, and directly in front of my house are substantial uneven sections that nearly buckle.
People who race past my house will loudly smack their undercarriage on the street. I have found car parts from time to time.
- A neighborhood could lobby to have pavement replaced with brick or cobblestone. It lasts longer, and is unfriendly to speeders
- Absent major street work, ask your city council for more stop signs and speed bumps.
The TDMA radio is plain not used, but the UMTS/GSM protocols merely treat voice as another kind of data stream (albeit with QOS), so they can multiplex them in. (That's how I know the TDMA radio isn't used; because Telecom NZ don't have a TDMA/GSM network (only a 3G/UMTS/WCDMA one, now) but still support voice and data simultaneously.)
TDMA was indeed part of the original GSM design, and CDMA was far more efficient - better coverage with fewer towers. Later revisions added CDMA and later technologies to GSM.
Wikipedia: It is important to note that GSM is a second-generation (2G) standard employing Time-Division Multiple-Access (TDMA) spectrum-sharing, issued by the European Telecommunications Standards Institute (ETSI). The GSM standard does not include the 3G UMTS CDMA-based technology nor the 4G LTE OFDMA-based technology standards issued by the 3GPP.
>> It was more carefully planned
Thats just ridiculous. Consider how much effort, (even just in broad brush terms of numbers of engineers, different companies and universities are working on it) hav gone into developing Unix, and are continuously happening on the Linux kernel, compared to NT kernel.
Dave Cutler had previously headed the coding teams for RSX-11 (PDP), and VMS (VAX), before departing DEC with his last team and the PRISM source to build what became NT. Cutler had FAR more experience than any of the architects of free (non-AT&T) UNIX. He easily rivals Ritchie and Thompson in his stature as a father of operating systems.
For a better understanding of DEC, the genesis of NT, and the roles these various people played, I recommend that you read ShowStopper. The planning behind the NT kernel certainly dwarfed the care behind the accretion of Linux.
And yes, the NT kernel appears safer and more secure than Linux, especially as Linus does not focus on security. (I do realize that 119/38 is not 24/26 - but the second figure likely involves userspace, which is not apples-to-apples.
The NT Kernel has far fewer security advisories than does Linux. It was more carefully planned, it is far more successful on the desktop, and the complete code has already leaked for those who really cannot resist seeing the source.
Microsoft's normal pattern is embrace-extend-extinguish. Android's BSD userland is uniquely vulnerable to this, and any action that Microsoft takes will likely improve general OS security, even if the data mining ramps up.
We know that the NT kernel developed by Dave Cutler has a POSIX emulation layer. This kernel runs the Windows app store, and it's perfectly capable of running Dalivk/ART in a variety of configurations - it does so already with Bluestacks and Google's emulators.
Take the NT kernel, and use it to replace Linux, leaving the Android userland as intact as possible.
To this "windroid," add the required javascript execution layers to allow the Windows app store to run on the same platform.
(Re)implement all of the extensions for Dalvik that are provided by Google services.
Reissue Windows phone as a unified Dalvik/Javascript mobile app platform, allowing Play apps to seamlessly move to the Windows store. Maintain enough control over the platform to provide security patches, and "windroid" could fix many update problems that Google seems incapable of addressing.
The NT kernel exists because it was able to mimic ms-dos. It could do so again with Linux.
I'm pretty sure that the BSD that Bill Joy ran on his VAXes could not nspawn a container, so I might interject that the Linux privilege system has changed slightly.
Now, if you don't carefully populate your container, you can easily cause more security problems than you solve.
Carriers and/or OEMs who abandon phones within 5 years of introduction should be compelled to release any signing keys that they used to lock bootloaders.
If Verizon wants to create a walled garden with locked bootloaders, then they have a responsibility to maintain it. Any devices that do not receive quarterly security patches should be forced open, allowing Cyanogenmod (et al) to become an option for security fixes. Novice users can then use third party security support, and power users can wipe Verizon's beloved NFL bloatware with prejudice.
I wish I had an LG with a leaked key, rather than my Samsung that lives in a straightjacket. I would never buy Samsung again. My Samsung will be retired far before the end of the useful life of the hardware.
If we're going to ban Samsung at the borders, let's not do it over rounded corners. Let's do it to control the hardware that we own.
Google says that OpenSSL currently has 437,962 lines of code, while LibreSSL is down to 316,745 as I see by wc -l $(find . -name '*.[ch]') which likely eliminates some bugs.
LibreSSL also removes the unsafe memory management that has been roundly criticised in OpenSSL.
LibreSSL also introduces many new features, and is generally more capable on the platforms where it runs.
Anyone who is seriously interested in FIPS is on the NSS TLS library anyway (from Netscape/Mozilla), as it has far more certifications. OpenSSL's FIPS was actually revoked for reasons of apparent negligence, which is understandable, since it was down to two staffers at one point.
How can encryption have "a profound effect on our ability to collect, particularly against terrorists" when they never found any terrorists to begin with?
You can cite the Privacy and Civil Liberties Oversight Board’s review on section 215, and their specific quotes, this is their words, “We are aware of no instance in which the [mass surveillance] program directly contributed to the discovery of a previously unknown terrorist plot or the disruption of a terrorist attack."
On May 31, 2015, the most controversial aspects of Section 215 of the Patriot Act, which included the collection of phone records (among others) in bulk, expired.
President Obama did not agree with the board's decision, which was announced in January 2014: "I believe it is important that the capability that this program is designed to meet is preserved."
We can only assume that the justification for bulk collection has little to do with terrorism.
I would like a button in Android that disables all Google applications and services, and halts any communication with Google servers.
That would be a wonderful new addition to Android. Sometimes the telemetry is just an uninvited guest.
This would conventionally be done with Cyanogenmod by omitting gapps post-install. There are two problems with that approach: a) fascist carriers with locked bootloaders, and b) a very high technical skillset that is not available to novice users.
A simple button to "cauterize google" would solve the problem nicely.
Europe could very well get such a thing, but I am unlikely to see it as I live in the U.S. where we are still waiting for the "right to be forgotten."
Europe/Russia, by all means, wedge this in. If Google balks, fork AOSP and ban sales of phones that include Google services. That would be quite an interesting fight.
In unprivileged mode, where apps run, security is important but not as much, because that arbitrary code will have no more permissions that the exploited app.
I do not agree with this statement. The Towelroot kernel vulnerability impacts some KitKat and all versions below - any app that is able to download a small binary and run it from a shell can obtain root privilege.
KitKat and below are over 50% of the Android ecosystem at the moment, and app privileges are dangerously weak there.
I would like to see a button in Android that disables all Google functions, applications, and connectivity to Google servers.
The FCC, or perhaps the FTC, would be wise to force this.
I would rather not see the European Union mandate this "forced feature" - the U.S. still lacks the "right to be forgotten" (AFAIK).
There are many who omit gapps when they load Cyanogenmod, but the carriers are making a wipe of/system increasingly difficult.
There are times when I want Google completely off of my devices. I own the device, it's my prerogative, and I would very much like to see a legal entity with appropriate jurisdiction make it happen.
In my printed copy of the Lions Commentary on the kernel for the 6th edition of the UNIX operating system, prominent notices of AT&T copyright are near the title pages. In the PDF online, I see "Circulation of this document is restricted to holders of a license for the UNIX software system from Western Electric."
If an API is subject to copyright, then fork(), wait(), open(), and the rest of the happy family of UNIX system calls is thus owned by Bell Labs -> Lucent -> Alcatel -> Nokia.
Nokia has the power to demand 10x Oracle's judgement if this stands.
Apple can easily solve this problem by forming an independent subsidiary in Germany which will maintain keys and security settings, which is then contracted into the next iOS upgrade. The current keys should be erased at the next upgrade. Then, the German government can approve FBI warrants for the use of the keys.
For real fun, Apple should announce that the iCloud servers for U.S. Government workers are moving to China, starting with all members of congress.
Didn't Firefox eliminate all usage of stagefright in their browser? That might be safer still, especially considering that Google made this mess. Firefox brings along their own h.264 and webm codecs that can actually be updated - how shockingly innovative!
It might be further prudent to purge any browser based on webkit/blink from Android. The "celebrated" fast browsers (maxthon, cmbrowser) have terrible scores at ssllabs.com anyway.
This is Google's problem with Android:
Everyone knows that debugging is twice as hard as writing a program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it? — Brian Kernighan, The Elements of Programming Style, 2nd edition, chapter 2
...it asserts that the extinctions followed the impact.
"The Alvarezes have argued that all 13 species of dinosaurs living in North America at the time of the asteroid's impact suddenly went extinct," Rigby said. "We now have evidence that at least 11 survived the asteroid collision. At the most, two species of dinosaurs went extinct - and we have some doubts about whether even that occurred."
"You seem to think a warmer planet/higher CO2 level is a good thing while completely ignoring the global devastation..."
I will draw your attention to my opening statement:
While this phase has lasted the entirety of human civilization and would have drastic consequences for many species should it end...
I support all reasonable caution for the environment. I also have an interest in climate science, and the causes and conditions of "snowball/icehouse/hothouse" earth. You seem to have less interest in climate metastability as you call it "completely irrelevant" - this is your purview.
Slashdot Mirror
This was an advisory referendum only, with no force of law. The United Kingdom is not obligated to leave the EU.
Yes, a pro-separation change in government will soon take place. However, the more forcefully that the new government pushes for a full departure, the more forcefully Scotland and Northern Ireland will attempt to disentangle themselves from the United Kingdom.
Northern Ireland in particular might see a real increase in sectarian violence if EU separation is not handled with great care, so internal security and continental policy will become even deeper-entwined. These forces will certainly blunt immediate impulses towards separation.
The EU bureaucracy has allowed a large, hostile contingent to form in several European nations. Perhaps now an inward gaze, compelled by credible criticism, can form a more perfect union.
Tinfoil now crashes when you attempt to use messenger, and there is no commentary from the developer if he can/will fix it.
I suggest that you examine the Face Slim client on F-Droid. He has released a recent, new version which solves the messenger problem.
I do need a client that will upload photos on KitKat. If I can find that, then the official Facebook client is history on all of my devices - their code is no longer welcome.
You may want some, or all, of these:
I'm advising anyone of importance to contact me through other channels. I have Tinfoil forced to desktop mode so I can see anything sent to me.
I had pondered forcibly enabling messenger in the Facebook APK (for Android), but I really don't want to rely on Facebook corporate anymore. I need to move away from their network.
I've never advised anyone to load fb-messenger, and I never will.
I live in an older neighborhood with a brick street. Some sections don't have the best maintenance, and directly in front of my house are substantial uneven sections that nearly buckle.
People who race past my house will loudly smack their undercarriage on the street. I have found car parts from time to time.
TDMA was indeed part of the original GSM design, and CDMA was far more efficient - better coverage with fewer towers. Later revisions added CDMA and later technologies to GSM.
Dave Cutler had previously headed the coding teams for RSX-11 (PDP), and VMS (VAX), before departing DEC with his last team and the PRISM source to build what became NT. Cutler had FAR more experience than any of the architects of free (non-AT&T) UNIX. He easily rivals Ritchie and Thompson in his stature as a father of operating systems.
For a better understanding of DEC, the genesis of NT, and the roles these various people played, I recommend that you read ShowStopper. The planning behind the NT kernel certainly dwarfed the care behind the accretion of Linux.
And yes, the NT kernel appears safer and more secure than Linux, especially as Linus does not focus on security. (I do realize that 119/38 is not 24/26 - but the second figure likely involves userspace, which is not apples-to-apples.
The NT Kernel has far fewer security advisories than does Linux. It was more carefully planned, it is far more successful on the desktop, and the complete code has already leaked for those who really cannot resist seeing the source.
Microsoft's normal pattern is embrace-extend-extinguish. Android's BSD userland is uniquely vulnerable to this, and any action that Microsoft takes will likely improve general OS security, even if the data mining ramps up.
We know that the NT kernel developed by Dave Cutler has a POSIX emulation layer. This kernel runs the Windows app store, and it's perfectly capable of running Dalivk/ART in a variety of configurations - it does so already with Bluestacks and Google's emulators.
Take the NT kernel, and use it to replace Linux, leaving the Android userland as intact as possible.
To this "windroid," add the required javascript execution layers to allow the Windows app store to run on the same platform.
(Re)implement all of the extensions for Dalvik that are provided by Google services.
Reissue Windows phone as a unified Dalvik/Javascript mobile app platform, allowing Play apps to seamlessly move to the Windows store. Maintain enough control over the platform to provide security patches, and "windroid" could fix many update problems that Google seems incapable of addressing.
The NT kernel exists because it was able to mimic ms-dos. It could do so again with Linux.
I'm pretty sure that the BSD that Bill Joy ran on his VAXes could not nspawn a container, so I might interject that the Linux privilege system has changed slightly.
Now, if you don't carefully populate your container, you can easily cause more security problems than you solve.
I have one - it got 5.1 Lollipop late last year, and it just got a security update.
Carriers and/or OEMs who abandon phones within 5 years of introduction should be compelled to release any signing keys that they used to lock bootloaders.
If Verizon wants to create a walled garden with locked bootloaders, then they have a responsibility to maintain it. Any devices that do not receive quarterly security patches should be forced open, allowing Cyanogenmod (et al) to become an option for security fixes. Novice users can then use third party security support, and power users can wipe Verizon's beloved NFL bloatware with prejudice.
I wish I had an LG with a leaked key, rather than my Samsung that lives in a straightjacket. I would never buy Samsung again. My Samsung will be retired far before the end of the useful life of the hardware.
If we're going to ban Samsung at the borders, let's not do it over rounded corners. Let's do it to control the hardware that we own.
Google says that OpenSSL currently has 437,962 lines of code, while LibreSSL is down to 316,745 as I see by wc -l $(find . -name '*.[ch]') which likely eliminates some bugs.
LibreSSL also removes the unsafe memory management that has been roundly criticised in OpenSSL.
LibreSSL also introduces many new features, and is generally more capable on the platforms where it runs.
Anyone who is seriously interested in FIPS is on the NSS TLS library anyway (from Netscape/Mozilla), as it has far more certifications. OpenSSL's FIPS was actually revoked for reasons of apparent negligence, which is understandable, since it was down to two staffers at one point.
I assume there will be an update in the near future.
How can encryption have "a profound effect on our ability to collect, particularly against terrorists" when they never found any terrorists to begin with?
We can only assume that the justification for bulk collection has little to do with terrorism.
I would like a button in Android that disables all Google applications and services, and halts any communication with Google servers.
That would be a wonderful new addition to Android. Sometimes the telemetry is just an uninvited guest.
This would conventionally be done with Cyanogenmod by omitting gapps post-install. There are two problems with that approach: a) fascist carriers with locked bootloaders, and b) a very high technical skillset that is not available to novice users.
A simple button to "cauterize google" would solve the problem nicely.
Europe could very well get such a thing, but I am unlikely to see it as I live in the U.S. where we are still waiting for the "right to be forgotten."
Europe/Russia, by all means, wedge this in. If Google balks, fork AOSP and ban sales of phones that include Google services. That would be quite an interesting fight.
I do not agree with this statement. The Towelroot kernel vulnerability impacts some KitKat and all versions below - any app that is able to download a small binary and run it from a shell can obtain root privilege.
KitKat and below are over 50% of the Android ecosystem at the moment, and app privileges are dangerously weak there.
Actually, that would be ALGOL
.
It is very unwise to purchase non-core telecommunications products from Verizon, as they do not last.
Digital and/or software products are an especially risky purchase.
I would like to see a button in Android that disables all Google functions, applications, and connectivity to Google servers.
The FCC, or perhaps the FTC, would be wise to force this.
I would rather not see the European Union mandate this "forced feature" - the U.S. still lacks the "right to be forgotten" (AFAIK).
There are many who omit gapps when they load Cyanogenmod, but the carriers are making a wipe of /system increasingly difficult.
There are times when I want Google completely off of my devices. I own the device, it's my prerogative, and I would very much like to see a legal entity with appropriate jurisdiction make it happen.
In my printed copy of the Lions Commentary on the kernel for the 6th edition of the UNIX operating system, prominent notices of AT&T copyright are near the title pages. In the PDF online, I see "Circulation of this document is restricted to holders of a license for the UNIX software system from Western Electric."
If an API is subject to copyright, then fork(), wait(), open(), and the rest of the happy family of UNIX system calls is thus owned by Bell Labs -> Lucent -> Alcatel -> Nokia.
Nokia has the power to demand 10x Oracle's judgement if this stands.
Apple can easily solve this problem by forming an independent subsidiary in Germany which will maintain keys and security settings, which is then contracted into the next iOS upgrade. The current keys should be erased at the next upgrade. Then, the German government can approve FBI warrants for the use of the keys.
For real fun, Apple should announce that the iCloud servers for U.S. Government workers are moving to China, starting with all members of congress.
Didn't Firefox eliminate all usage of stagefright in their browser? That might be safer still, especially considering that Google made this mess. Firefox brings along their own h.264 and webm codecs that can actually be updated - how shockingly innovative!
It might be further prudent to purge any browser based on webkit/blink from Android. The "celebrated" fast browsers (maxthon, cmbrowser) have terrible scores at ssllabs.com anyway.
This is Google's problem with Android:
...it asserts that the extinctions followed the impact.
I will draw your attention to my opening statement:
I support all reasonable caution for the environment. I also have an interest in climate science, and the causes and conditions of "snowball/icehouse/hothouse" earth. You seem to have less interest in climate metastability as you call it "completely irrelevant" - this is your purview.