Hi,

since I haven't found a tutorial on how to use a usb smartcard (like f.e. Nitrokey/Librem Keys) to unlock the Luks encrypted volume on a Pinephone, I had a look at it myself and found a way to do it (at least on Mobian).
If someone else wants to try this, I've modified the Luks gpg fde configuration script from Purism (https://source.puri.sm/pureos/packages/s...d-key-luks) to automate the configuration on the PinePhone with Mobian.

Feel free to have a look: https://github.com/sam-m7/smartcard-luks-osk

It works by using a modified version of the gnupg-sc keyscript (/usr/lib/cryptsetup/scripts/decrypt_gnupg-sc). The modified version uses the on-screen keyboard (osk-sdl that is also used for normal fde) and forwards the output to gpg (PIN). After 90 seconds there is a fallback and the keyboard pops up, also if no smartcard was detected. You can then type in a passphrase from a different keyslot (without gpg being called). But there is no feedback (at least not on the screen, a little bit on the serial console).

The recognition of the USB Device sometimes takes long. As far as I would say there is a problem with the anx7688 kernel module, because if it doesn't work, this is printed in the serial console (UART adapter) all the time (not only in the initramfs stage):

Now that we have working LAN, we can link this image here

https://github.com/manjaro-arm/quartz64-...s/releases

The image is updated weekly.

With

• LAN
  
• PCIe
  
• USB2
  

• USB3
  
• SATA-Port
  
• HDMI
  

Quote:If there is no battery plugged into the board, the jumper labelled "ON/OFF_BATT" must be in place. If this is set wrong, stability issues such as failures to boot will occur.

I'm just at the beginning of my testings. But I can confirm that it is possible to hear at least the OS itself sounds from pinephone, when I'm using mumble and doing volume up volume down one a pinephone it is possible to hear those volume adjustment beeps on the other end while mic is supposedly switched off by hardware switch.

KDE Manjaro CE

I am having trouble with the Twinkle SIP application.

I am able to use Zoiper on my laptop, but Zoiper won't run in PinePhone. (If I am wrong, please send me a link so I can install.)

For the Zoiper app, I use the following information:

username (123456)
password (135790)
and the SIP server sip.companyname.abc

I put these in Twinkle and when I try to connect, I get an error:

Failed to create a UDP socket (SIP) on port 5060

strerror_r is not available: 98

I am also not sure where I should be putting the information I have into Twinkle in order to log in correctly. Twinkle has many, many options and I did my best, but it just won't seem to connect.

Does anyone know what to do?

hello, I need a beginners help or a tutorial, to learn sxmo's user scripts, please

1) I am too stupid to be able to ssh to my pinephone (from OSX)
2) installed Thunar and found my empty unserscripts folder
3) would like to locate userscripts and copy them to my userscropts folder
4) on edit userscripts and ../ I get a list of contacts.tsv, hooks/, userscripts/, xinit of course, none of these menus does anything, probably because my userscripts folder is empty.

Now if I could locate some scripts in the internet, download them, and copy them into the userscripts folder (with firefox and thunar), I imagine that might be a first step. Later do the same via ssh. Are there any helpful links for shell scripting and sxmo scripts?

On https://git.sr.ht/~mil/ I see much about scripting but very few that I can understand ;(
There seems to exist a script to sleep the phone after a while. I would like to install it and see what it does.

Has anyone gotten "Librewolf Browser  to work on their PBP? If so let us know.

Does anyone know how to get Linux (Debian, Manjaro, etc.) to cooperate with a NetBSD NIS server?

The only thing that doesn't work is user passwords.  Linux clients recognise NIS users but will not authenticate them.  I do not have this problem with NetBSD or Solaris clients.  Nobody else seems to run into this.

I can’t be the only n00b PinePhone-owner who’s not too excited about how my ordinary user can sudo with the PinePhone’s lockscreen PIN-code? This is the case in both Manjaro and Mobian. If one should be the victim of a brute force password attack, even a 16-20 digit numerical password is cracked before you can blink, and the attacker can log in as root with it. Numerical password is also a lot easier to see (few, big buttons) and memorize in a «over the shoulder password attack» than be an alphanumerical one with upprcase, lowercase and special characters.

I have actual enemies skilled in «pentesting» (cracking) who have subjected every aspect of my digital life to targeted attacks, often successfully, so my need for device security probably exceeds the average internet surfer, but even the typical average user with no personal enemies could get hurt by crackers who have the knowledge of this numerical password issue on Mobian and Manjaro. 

I’ve tried several guides found online, for setting privileges and demanding root passwd for sudo, but there aren’t as many n00bs posting these stupid questions about Mobian or ManjaroARM as there are people answering these questions about desktop Ubuntu. Please help! How to fix this on different distros respectively? Removing sudo privileges will permanently lock you out of root on Mobian because the only way to log in as root is sudo -i with the lockscreen PIN code, while on ManjaroARM that might be a solution. Please help!

New PinePhone user who is also relatively new to Linux as well.

I picked up a 512GB Samsung EVO Select SD and used Rufus in Win10 to restore the mobian-pinephone-phosh-20210517.img I downloaded from https://images.mobian-project.org/pinephone/ (parent of the "installer" folder).

The phone booted to the Mobius splash screen right away; which was a good sign... and indicated it was expanding the disk on first boot.

At some point (maybe after 15 minutes), the screen blanked (transitioned from the splash disk expansion screen)... you could still see the backlight was on... just no more messages echoed to the screen.

In case it was still busy, I left the phone alone to do its thing for about an hour... then powered it down.

I took the SD out of the phone and installed it back into my USB/SD card reader on my PC, brought up the disk manager, and confirmed the partitions had been expanded out to consume the entire disk... 8MB Unallocated, 504 MB Active Primary Partition, and a 476.41 GB Primary partition.

So as far as I can tell, the phone booted the SD image and expanded the disk like it said it was going to, and then went completely silent/blank... was I not patient enough waiting an hour for something to show on the screen, did I pickup an SD that was too big, should I have used the installer image, or is there a known issue here that I can take an action on to yield a successful boot?

In the mean time I also want to test this new SD... so I've used the Win10 Disk Manager to delete the two allocated partitions, created one large NTFS partition, and am in the process of copying a single 368GB (nvme backup) file to it... Windows suggested it was going to take ~80 minutes to copy the file @ 80 MB/s.... at the time of this writing 28% of the file has been written (~103GB) with a 55min ETA.

Hopefully the SD proves to be good... I post again (or maybe just update this post) with those results, and look forward to everyone's feedback and help.

EDIT: I think the SD is good...  The 368GB file copied successfully at a sustained 80GB/s second average (bounced between 79.6 and 80.6), I even mounted the backup image, browsed the folder structure, and opened a few random files to confirm their contents were read correctly.  I don't think my issue is that the SD is bad.

Hello,

 Since owning my rock64 (4GB version)  I had always problems compiling larger projects on the device itself.

I tried many things like an other ac-adapter, different micro-sdcards, compiling on USB, different host-images, compiling only on two cores than
one core, gcc-5, 6, 7, swap on,  nothing helped.

The compiler always runs in errors like "illegal instruction" or "memory fault" that were temporal as they disappeared at the next
try.

After playing around with the rockchip boot flow on the rockpro64 I got the idea to check the driver for the external memory interface.
All host-images I tried on the rock64 use the same driverfile "rk3328_ddr_786MHz_v1.13.bin", so I gave the rock64 an other try with
rk3328_ddr_333MHz_v1.13.bin at offset 0x8800 on the boot device.

After reboot I compiled the ayufan-kernel on the device itself with 4 cores on internal sdcard. Worked, no error like before.

Yesterday I took an external USB-HD with the source of palemoon compiled from USB, wrote the objectfiles to the internal sdcard, 4 cores, swap on. It took the whole night, but the build completed successfully. No error like before.

Can someone tell me the negative implications when using the 333MHz-version of this driver?
______________________
First Motion Products