Is there any document where they describe how their focus on security shapes pureOS? I'm seeing stuff like bundling some add-ons for the browser, and kernel patches.
In my mind, securing users in 2018 means to have a decent password manager with an up-to-date browser, make sure that apps are sandboxed and prohibit the browser from accessing all my user's files. Do they tackle this?
No it's the other way round; with 61 MSPS sampling rate, the theoretical maximum bandwidth is 61 MHz, so they stay below.
[edit]
If you're missing the factor two, as in "sampling frequency must be twice the maximum signal frequency", the keyword is complex sampling. With complex signals, the sampling theorem is "sampling frequency must be greater than the maximum signal frequency".
[edit2]
I don't want to make anybody read about sampling. So we have a real signal - we're in the real world - and suddenly there's a complex signal? You basically fork the signal, and delay one signal path by half the clock period. You can then sample both signals at the same time, and collect the data you would get when sampling with the double frequency. Because we sample two signals, we store two samples at a time. One we call the real signal, one the imaginary -- and there we got our complex signal.
You cannot accept unknown SIM cards due to mutual authentication -- the provider must know the shared secret that is burned into the SIM.
You can achieve network separation APNs, so there is no need for such a hack.
The question I have in mind is: Does your office advertise it's own PLMN with WiFi-like equipment, or do you outsource your office wireless network to an established operator which handles authentication and provides a virtual, separate network?
Yes you need to burn a SIM card, but that's it basically. srsLTE and other "homebrew" eNodeB software is standards-compliant and your smartphone will most likely connect.
In practice, you need to worry about legal restrictions -- you're not allowed to transmit on common LTE bands.
Not sure how this will actually look in the future. Is the office mobile network physically separated, or do you use the public network with special SIM cards that connect to a virtually separated mobile network?
KDE offers the integration that I expect from a desktop. Plasma was way ahead of others, when it came to management of
* audio, including Bluetooth
* network
* display
Unfortunately, little care is taken on security.
KDE Wallet simply offers an API to all your passwords, without any separation. Users cannot tell which application just accessed the "wallet". Certificate warnings randomly pop up, asking for "yes" or "no" without any explaination. Plasma "integration" will ask you for full access to your Google account, but it is unclear what for. The calendar integration will require separate authentication -- to the calendar only.
I think Linux desktops were ahead of others, some years ago, but right now I struggle to recommend it to anyone.
In my mind, securing users in 2018 means to have a decent password manager with an up-to-date browser, make sure that apps are sandboxed and prohibit the browser from accessing all my user's files. Do they tackle this?