Convert unallocated space to usable on a dual boot system

So I have dual booted my 1 TB hard disk with Windows and Ubuntu.

The disk partition looks as following Disk Partition

As you can see there is 326 GB of unallocated space that is not usable. It is an MBR disk so I am aware that the maximum number of partitions can be 4. Current primary partitions run contain the following:

  • Partition 2 /dev/sda2 Windows Filesystem
  • Partition 5 /dev/sda5 Linux Filesystem
  • Partition 6 /dev/sda6 Linux Swap
  • Partition 7 /dev/sda7 Linux Files

Is it possible to make this space usable?

Please link any previously answered questions if this has already been answered.

The output of sudo fdisk -l is

Disk /dev/loop0: 202.9 MiB, 212713472 bytes, 415456 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/loop1: 320.2 MiB, 335728640 bytes, 655720 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/loop2: 320.2 MiB, 335794176 bytes, 655848 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/loop3: 202.3 MiB, 212099072 bytes, 414256 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/loop4: 181.1 MiB, 189870080 bytes, 370840 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/loop5: 89 MiB, 93327360 bytes, 182280 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/loop6: 8.4 MiB, 8839168 bytes, 17264 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/loop7: 180.2 MiB, 188928000 bytes, 369000 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x6436f9fc  Device     Boot      Start        End   Sectors   Size Id Type /dev/sda1  *          2048    1026047   1024000   500M  7 HPFS/NTFS/exFAT /dev/sda2          1026048  686035516 685009469 326.7G  7 HPFS/NTFS/exFAT /dev/sda3       1323407360 1324374015    966656   472M 27 Hidden NTFS WinRE /dev/sda4       1324378110 1953523711 629145602   300G  5 Extended /dev/sda5       1324378112 1359499263  35121152  16.8G 83 Linux /dev/sda6       1359501312 1375123455  15622144   7.5G 82 Linux swap / Solaris /dev/sda7       1375125504 1953523711 578398208 275.8G 83 Linux  Partition 4 does not start on physical sector boundary.     Disk /dev/loop8: 85 MiB, 89128960 bytes, 174080 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/loop9: 88.7 MiB, 92983296 bytes, 181608 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/loop10: 8.4 MiB, 8835072 bytes, 17256 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/loop11: 8.6 MiB, 9019392 bytes, 17616 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes 

Android exploited – elevated privileges – SE Policy exploit – system as root – dual boot – living in my ramdisk. What now? [on hold]

Ive been chipping away at this for days and going in circles so I need to put this out there – somewhere.

My Samsung s9+ hasnt been acting properly for a long time – but in the past few weeks this thing has become a nightmare. Calls and messages come through sometimes days late or apparently days early as the time is changed routinely. The OS is constantly reverting back to some kind of stock image (android pie it is not) with settings completely reset. Weird errors have forced resetting several times and my photos have all been destroyed in random ways (faces altered, photos smudged, scratched out etc). Daily backups have been ignored.

I will attach some of the snide logs this thing generates as well as the init.rc and build.props (fstab goldfish files etc) – im not sure what is handy so i will wait for a response as i have most system documents. These system files and logs that show that adbd is placed in the privileged position pre init – it then discards any update or change installing instead from a hidden partition (or network – the thing is never offline or properly shut down). There it remaps me to a virtual disk and assumes root control of my operating system. I am not sure if it is timed or if there is someone behind it – but as i get close to removing the files (or think i do) it will pretend to brick for an hour or two and then suddenly leap into recovery mode.

Now im not concerned with the causes or what its doing. In its current condition i cant factory reset or erase with odin as it has positioned itself to respond to exactly this threat. Before the setup screen presents this thing has root access and is busy setting tasks and countdowns – similar behaviour is manifesting itself in my PC but i think this exploit has had longer to stretch out on the phone. Can anyone offer any assistance. Its sending me nuts being trapped fixing the damn thing.

How to execute a command directly on the host system through docker.sock in Docker container?

I’ve been studying Docker security and examining ways of escaping from container to host.

Suppose Docker sock is mounted into the container at /var/run/docker.sock, so that Docker client (client) can send commands to Docker daemon (dockerd).

To execute commands on the host, I could run another container and mount /etc/ into it (read-write) to schedule CRON jobs (is it possible to mount /etc/ into the current container?).

Besides the above, what other methods are there for executing commands on the host through /var/run/docker.sock?

Image Processing (Encryption/Decryption) system using Residue Number System

I’m preparing for my final year project in school and i plan on working on the implementation of Residue Number System in Image Processing. I found this thesis online by Pallab Maji here:

http://ethesis.nitrkl.ac.in/2831/1/Thesis_Final_App_of_RNS_in_Comm__SP.pdf

and i checked on Pages 29 – 41, he explained the algorithm in which i’m not to familiar with some of the concepts:

  • I: Input image and block size m and n.
  • II: Break image into m x n blocks and Zigzag Scan the intermediate blocks.
  • III: Z = m x n x 8 bits. Generate a moduli set P, where P = {p1, p2 … pk} corresponding to Z bits.
  • IV: Convert the intermediate zigzag scanned block into one word and scale to avoid overflow.
  • V: Use the set P to convert the word into RNS.
  • VI: Regroup the RNS number to form a word and further break them into m x n blocks.
  • VII: Map the encrypted block to image.

I would be very grateful if anyone could help put me through.

Usability testing of design system components and patterns

This is my first post here, and what I am searching for have not been found yet, I must be very innovate, joke aside. I have gotten a mission at my current company from the C-level to test through all of the components and patterns of our design system. This is everything from input components, badges, tables, cards, panels etc. Our design system is structured based on atomic design.

I am however not familiar with testing on specific components alone, I have always done it through scenarios and cases where we have whole layouts with components that will support our users in their work. Is there any way of performing smaller usability tests without specific cases?

Here’s what I was thinking:

  1. I could test each component against certain criterias.
  2. I could perform the 5-second test (identify how it is being percieved after 5 seconds)
  3. The break-it-method, where users and test paricipants try to find errors and problems in the functionality and usability
  4. Test participants will compare our components one by one with those of material design or lightning
  5. Evaluate the components through CBUQ (Component-Based Usability Questionnaire)
  6. Have small tasks for each component to see how easy they are to use and navigate, e.g. Task1 – enter data, Task2 – remove entered data, Task3 – Navigate using keyboard etc.

Are any of these ideas good? Are there any others? Please help! Any input in valuable! 🙂

If my computer system is on, but none of my network connections are active, can someone work on hacking into my OS?

I thought I read that if my network connections, both wifi/ethernet, are NOT on, that if someone wanted to try and work on hacking my OS, that they would have to wait until the network connection is active, even if my computer and everything connected to it is powered on (firewall, switch, router, etc).