infjarchninja

File permissions change when transfering between external drives and laptop

I noticed a few years ago that when I transfer files back and forth between my laptop and my external drive all the files that I have transfered have changed permissions.

I format all my external drives as exFAT so I can use larger files.

Why does this happen?

Is there a better way to keep the file permissions intact when transfering files back and forth between external drives?

The test file: Fantastic Fungi (2019).mkv

+++++++++++++++++++++++++++++++++++++++++++++++++++

This is what the file permssions looks like before I transfer it to my external hard drive

ls -l

-rw-r--r-- 1 user user 577761580 May 2 2024 'Fantastic Fungi (2019).mkv'

+++++++++++++++++++++++++++++++++++++++++++++++++++

This is what the file permssions looks like after I transfer it back to my laptop

ls -l

-rwxr-xr-x 1 user user 577761580 May 2 2024 'Fantastic Fungi (2019).mkv'

When I right click file permissions dialogue box. The "Allow this file to run as a program" is ticked.

+++++++++++++++++++++++++++++++++++++++++++++++++++

The way have overcome this is to run a simple one liner to reset the permissions for directories and files.

Open a terminal in the directory of the folders and files you want to change

All directories will be 775. All files will be 664

find . -type d -exec chmod 0755 {} ;

find . -type f -exec chmod 0644 {} ;

Directory permission 0755 is similar to “drwxr-xr-x”

File permission 0644 is equal to “-rw-r–-r–-“.

-type d = directories

-type f = files

+++++++++++++++++++++++++++++++++++++++++++++++++++

How to access signal's db.sqlite,

I uploaded this to kingofras@lemmy.world "Look at the silent countries" post

I though it would be useful to know how to access what information signal stores.

So those privacy conscious individuals can check for themselves.

this is the basic difference between Molly and signal.

In Molly you can password protect db.sqlite, Signal removed this option a while ago.

On linux you can access your Signal messages in db.sqlite.

once you delete a message from signal, either through disappearing messages or manually, all those messages are deleted from the db.sqlite.

They are stored in an encrypted db.sqlite here:

/home/user/.config/Signal/sql/db.sqlite

you can also extract it from you phone:

only the messages that you can see when you open the Signal app are visible there.

to access the messages:

install:

signal-backup-tools-git

https://github.com/bepaald/signalbackup-tools

and

DB browser for sqlite

https://sqlitebrowser.org/

++++++++++++++++++++++++++++++

The most straight forward way is to create an output file to html.

copy the db.sqlite to a new directory

signalbackup-tools --exportdesktophtml signal.html

this will create folders of all your contacts and messages and media.

easily acessible. open the signal.html files in your browser

=+++++++++++++++++++++++++++++++++++++++

To open db.sqlite as a Sqlite database;

first you need to get the key:

copy the db.sqlite to a new directory

then run in terminal:

signalbackup-tools db.sqlite --showdesktopkey

OpenSSL 3.3.2 3 Sep 2024)

Signal Desktop key (hex):

58bfa167bb66b2b13b2ca6eadc33f4bf7275c254006d17ae5e3de5356c60f0b7

copy the key to a text editor

+++++++++++++++++++++++++++++++++++++++

you must now add 0x to the beginning of that line:

0x58bfa167bb66b2b13b2ca6eadc33f4bf7275c254006d17ae5e3de5356c60f0b7

then open db.sqlite with the sqlitebrowser

right click db.sqlite, select open with DB Browser for sqlite

select RAW from the dropdown menu

input the passphrase from above. make sure you added the 0x to the beginning.

The entire database opens.

you can view all the information that signal collects. phone numbers, messages, images, media etc

+++++++++++++++++++++++++++++++++++++++

I booted into my Manjaro gaming rig this morning for its weekly update check and got this error message.

Error: Symbol 'grub_is_using_legacy_shim_lock_protocol' Not found

seems like grub is not installed.

I noticed the warning after the last update a week ago regarding grub.

A single line in the pacman terminal output is not really good enough. I did nothing at the time

I dont use btrfs only ext4.

FIXED:

inserted a manjaro live usb

selected efi-usb

booted into the live manjaro distro

opened terminal

input two commands

manjaro-chroot -a

install-grub

++++++++++++++++++++++++++++++++++++++++

[manjaro /]# manjaro-chroot -a  ✔ grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map. grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map. ==> Mounting (ManjaroLinux) [/dev/sda2] --> mount: [/mnt] --> mount: [/mnt/boot/efi]

[manjaro /]# install-grub Grub will be installed on: EFI Installing for x86_64-efi platform. Installation finished. No error reported. Update UEFI Fallback file: /boot/efi/EFI/Manjaro/grubx64.efi Generating grub configuration file ... Found theme: /usr/share/grub/themes/manjaro/theme.txt Found linux image: /boot/vmlinuz-6.15-x86_64 Found initrd image: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-6.15-x86_64.img Found initrd fallback image: /boot/initramfs-6.15-x86_64-fallback.img Found linux image: /boot/vmlinuz-6.12-x86_64 Found initrd image: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-6.12-x86_64.img Found initrd fallback image: /boot/initramfs-6.12-x86_64-fallback.img Warning: os-prober will be executed to detect other bootable partitions. Its output will be used to detect bootable binaries on them and create new boot entries. ERROR: mkdir /var/lock/dmraid grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map. grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map. Adding boot menu entry for UEFI Firmware Settings ... Root filesystem isn't btrfs If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs" Found memtest86+ image: /boot/memtest86+/memtest.bin Found memtest86+ EFI image: /boot/memtest86+/memtest.efi done Warning: GRUB bootloader at '/boot/efi/EFI/Manjaro' was updated. Your booted entry '' is not the same as 'Manjaro'. This may be a rescue ISO, but if not check your EFI boot priority.

REBOOT

that is the sound of inevitability

https://proton.me/blog/ai-browsers-perplexity-chrome-privacy

imagemagick Montage:

I can only create a montage if all the exif data is cleared.

As a new user on Lemmy, going through the learning curve, I had issues uploading images.

Simple, I turned to imagemagick to reduce the size of the images and create a montage, rather than uploading 20 images for a simple bread recipe.

!bready@lemmy.world

========================================

I transfered my recipe images from my phone to my laptop and set about using Montage.

The images on the phone, and in the directory on my laptop, were clearly orientated in Portrait and not landscape.

========================================

Problem:

I ran montage to create a simple 4 image montage:

montage 1.jpg 2.jpg 3.jpg 4.jpg -geometry +2+2 1-montage-image.jpg

I checked the output file, the images were in the right order but had changed from portrait to Landscape. They looked terrible

I then tried some different images.

These came out as expected, in portrait and in order

=======================================

I compared the images,

identify -verbose 1.jpg

the ones I transfered from my phone still had all the exif data intact and the other ones had no exif data

========================================

So I cleared the exif data for the files.

exiftool worked perfectly:

exiftool -all= *.jpg

created an "original-images" directory, then moved the originals to "original-images" directory

mv *.jpg_original original-images

when I cleared the exif data all the images in the directory reverted to landscape

========================================

so I set them back to portrait:

One liner to change orientation by 90 degrees

find . -maxdepth 1 -type f -name "*.jpg" -exec convert {} -rotate 90 {} ;

or mogrify:

mogrify -rotate -90 *.jpg

or

mogrify -rotate +90 *.jpg

========================================

created the montage image:

montage 1.jpg 2.jpg 3.jpg 4.jpg -geometry +2+2 1-montage.jpg

========================================

Now I reduced the size so I could upload them

create an "images" directory if you do not want mogrify to overwrite the originals.

mogrify -resize 50% -quality 80 -path "/path/to/reduced/images/" *.jpg

or

mogrify -resize 50% -quality 80 -path "images" *.jpg

job done

========================================

A lot of messing about to upload an image