A few moments ago I upgraded my Ubuntu 14.04 LTS to Ubuntu 16.04.1 LTS (Xenial Xerus). I waited for the service pack 1 to be released in the end of July, and hence the delay. Everything was smooth, and my dual boot runs perfectly well with Windows and Ubuntu just as before. On the other hand, every time Windows does a minor upgrade (not just the Windows 8 to Windows 10 upgrade), it breaks my grub and makes Windows the default and only option, making Ubuntu unreachable. Luckily I have a Lubuntu-based software, named boot-repair-disk that can fix these boot issues. The current version of the software does not work for Windows 10. However, I have a previous version with me that just works fine.
I am not entirely sure why Windows made each upgrade to break the grub. Is it made intentionally, or is it that hard for the engineers to fix this minor bug (or may I say, feature?). This is so annoying and inconvenient. This makes Windows look like a big bully.
So now I have the latest LTS version, and I will upgrade again in 2018 August with 18.04.1 LTS. I made some interesting observations during the upgrade.
Configuring encfs ├──────────────────────────────────────────────────────────────────────────────────────────┐
│ │
│ Encfs security information │
│ │
│ According to a security audit by Taylor Hornby (Defuse Security), the current implementation of Encfs is vulnerable or potentially vulnerable to multiple types of attacks. For example, an attacker │
│ with read/write access to encrypted data might lower the decryption complexity for subsequently encrypted data without this being noticed by a legitimate user, or might use timing analysis to │
│ deduce information. │
│ │
│ Until these issues are resolved, encfs should not be considered a safe home for sensitive data in scenarios where such attacks are possible. │
│ │
│ │
│
│ │
│ Encfs security information │
│ │
│ According to a security audit by Taylor Hornby (Defuse Security), the current implementation of Encfs is vulnerable or potentially vulnerable to multiple types of attacks. For example, an attacker │
│ with read/write access to encrypted data might lower the decryption complexity for subsequently encrypted data without this being noticed by a legitimate user, or might use timing analysis to │
│ deduce information. │
│ │
│ Until these issues are resolved, encfs should not be considered a safe home for sensitive data in scenarios where such attacks are possible. │
│ │
│
│
So, EncFS is not secure after all.
The other prompt that caught my attention was the below:
Configuring davfs2 ├──────────────────────────────────────────────────────────────────┐
│ │
│ The file /sbin/mount.davfs must have the SUID bit set if you want to allow unprivileged (non-root) users to mount WebDAV resources. │
│ │
│ If you do not choose this option, only root will be allowed to mount WebDAV resources. This can later be changed by running 'dpkg-reconfigure davfs2'. │
│ │
│ Should unprivileged users be allowed to mount WebDAV resources? │
│ │
│
│
As of now, everything seems to work just fine after the upgrade. I will update further when I find out whether something is broken due to the upgrade, later.
No comments:
Post a Comment
You are welcome to provide your opinions in the comments. Spam comments and comments with random links will be deleted.