From: nospam@needed.invalid   
      
   On Mon, 12/30/2024 9:41 AM, Edmund wrote:   
   > On 12/30/24 12:35, Joerg Walther wrote:   
   >> Edmund wrote:   
   >>   
   >>> Waydroid anyone?   
   >>   
   >> Yep, got it running here, on 22.04 LTS.   
   >>   
   >>> Hello, I am new here comming from Linux-Mint.   
   >>> Wanted to use "waydroid" but that seems to be impossible on Mint.   
   >>   
   >> It doesn't work on Mint because Mint still uses the X server for   
   >> graphics, Ubuntu by default has Wayland.   
   >>   
   >>> 4. curl https://repo.waydro.id | sudo bash   
   >>   
   >> The only thing I can see is that you are missing an argument in the   
   >> above command:   
   >> curl -s https://repo.waydro.id | sudo bash   
   >   
   > Well that list of commands was copied from one of the youtubers.   
   > Anyway I actually used :   
   > "curl -s https://repo.waydro.id | sudo bash"   
   >   
   > Which first asked me the sudo password for "ed" ( default user )   
   > After that :   
   > "Warning: Failed to open the file /usr/share/keyrings/waydroid.gpg : read   
   only   
   >  Warning : file system   
   > $$$$$$$$$$$100.Oncurl: (23) Failure writing output to destination   
   >   
   >   
   > What is important is that I created the empty file "waydroid.gpg" myself in   
   an attempt the make it work   
   > Before I created that file the message was the same ( i think ).   
   >   
   >>   
   >> (https://docs.waydro.id/usage/install-on-desktops)   
   >>   
   >> If it still doesn't work, the exact error message would be helpful.   
   >>   
   >> -jw-   
   >   
      
   First of all, that pattern is a security nightmare.   
   You NEVER pipe an unknown script, into an elevated shell.   
      
   You can use an ordinary browser to examine the script.   
      
      firefox https://repo.waydro.id/   
      
   and the result is just text. You can read the text, see what   
   the code is doing. And check the permissions and existence of /u   
   r/share/keyrings/ .   
   It's possible the distro you are on, puts the keyrings somewhere else.   
      
   I'm not exactly a security type, and I recognize about 1% of   
   potential threats. But I wouldn't do that, pipe stuff into an   
   elevated shell. I want to look at the code first, even code   
   that isn't elevated. Remember, when you were younger, people   
   used to put "rm -Rf * " into scripts as a kind of joke. This   
   is why we examine scripts, even scripts that came out of a repo.   
      
   People put "rm -Rf * " into scripts, to teach you about security.   
   And to teach you about backups.   
      
      Paul   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)