Puppy Linux Discussion Forum

• Puli homepage with links to mirrors
  Mirror including the proposed additional packages for Puli here.
  Puppy Linux knowledge base
  Puppy forum (huge collection of HOWTOs, ideas, and installable packages)
  32-bit and 64-bit Puppy Linux packages (programs, Nvidia drivers, etc)
  Adobe Flash plugin (See details above in section "For advanced users")
  Extra ffmpeg codecs for chromium flavors such as Slimjet or Vivaldi (Earlier extra ffmpeg codec versions may not work with the latest browser)
  Common CA certificates (You can browse this link for the latest ones - the ca-certificates] associated with the newest Ubuntu versions may be OK for browsers such as Netsurf or Links)
  USB install tools (Some of them are Linux based, others are created for Windows only)

mikeslr wrote: ↑Thu Sep 10, 2020 5:36 pmfailed with the report "puli7.3.sfs could not be found" or words to that effect

oui wrote: ↑Thu Sep 10, 2020 8:40 pm I did download it (but miss some devx system) and did try to try it out a usual frugal install !

without success as login and password where on the way...

above literature were to much for me for that evening (as it is already 22:40 h).

and it is to much to prepare a stick out a running Puppy (Dpup buster with xfce4 32 bit). why no frugal install?

By the way, gjuhasz, although its initial GUI was in English, its menu was in Hungarian. I changed that to en-GB, then back to en-US to obtain a menu in English (American?)

I didn't have LinuxLIve USB-Creator installed. I tried rufus.

why no frugal install?

...without success as login and password where on the way...

mikeslr wrote: ↑Fri Sep 11, 2020 12:05 amI booted into Windows and installed puli7.3 to a USB-Key using LinuxLive USBCreator. That worked as puli booted to desktop on my Laptop. Unfortunately, the kernel (and drivers) it has did not have among them any which recognized either my keyboard or mouse.

mikeslr wrote: ↑Fri Sep 11, 2020 12:05 am I2) I've gotten this far with frugalpup-installer. The boot option will work to install a bootloader but only after copying puli7.3.sfs and renaming it puppy_puli7.3.sfs. In other words, the frugalpup-installer's complaint that it could not find a "puppy" was to be read literally: it only looks for a puppy-version.sfs beginning with the name "puppy". Likely its other modules can be similarly tricked. After the "boot" module writes grub to the USB-Key, the file named puppy_puli7.3.sfs can be deleted.

mikeslr wrote: ↑Sun Sep 27, 2020 2:49 pm Hi, gjuhasz,

This is just a suggestion based on my previous posts. (...) I don't know how complicated it would be to implement.
My thought was that those most likely to discover, use and recommend Puli were those already familiar with other Puppies and debiandogs.
(...)
I suspect that boot-installers other than frugal-installer may have the same difficulty generating a menu.lst/grub.cfg as a result of how the main SFS is named. Rather than having potential Puli users engaged in manually perform the above procedures, I wondered how difficult it might be if in the future Puli's main SFS was named puppy_puliX.X.sfs?

directed toward finding ways to boot into Puli without having to first boot into Windows in order to deploy Puli to a USB-Stick

• 1. Get a 4 ... 32 GB pendrive then use GParted to wipe it and create a new bootable FAT32 partition on it.
  The result is an empty device being registered, let's say, as /dev/sdb1
  2. Open a terminal and enter syslinux -i /dev/sdb1 to put ldlinux.sys over the current bootsector of the pendrive.
  (You may need the mtools package - it is available in the PPM)
  3. Download Puli_install.zip and extract its content to the pendrive.

...and especially to be able to deploy Puli from a running Puppy

Dear Puli users,

I noticed claims that some Linux users have issues with playing DRM protected videos.
Armed with Chrome, Iron, Slimjet, and Firefox smartloaded in Puli 7.3, I visited Netflix and sadly recognized that only Chrome played those videos without any problem.

Finally, I found a workaround and created a small Widevine64p.pet package. Successfully tested with the above listed browsers.
Downloadable from my https://sourceforge.net/projects/puppys ... /packages/ folder.

Please note that this is a Puli specific package. However, it can be easily tailored for other puplets.

Have fun!

Regards,

gjuhasz

@gjuhasz :-

Hallo, mate.

Yeah, that doesn't surprise me one little bit, TBH! Chrome is, by default, the only one that comes with Widevine pre-installed. It's always been one of their selling-points.

Iron, Slimjet, Opera, Vivaldi, Yandex.....even the new Linux build of M$ Edge, all need to "poach" WideVine from somewhere else. They can all make use of it if it's there, but they don't come with it as standard.

NetFlix is something of a pre-requisite for me, so that's why all the portable-browser 'clones' I produce come with it OOTB, as it were. For 64-bit versions, you can simply 'borrow' the Chrome WidevineCDM directory. For 32-bit versions, it's a bit more fiddly.....

What I do is this:-

You download the 32-bit Vivaldi .deb package. Vivaldi is the only one that comes with built-in 'updater' scripts for both WideVine and ffmpeg. I copy the scripts from the /opt/vivaldi directory, and put them in a 'safe' location. Now; if you run them from inside the /vivaldi directory, they update 'in-situ', as it were. But we don't want that; we want to create the items externally, so they can then be copied for other browsers.

I stick these 2 scripts in their own directory in /root. When you click to run them from here, they'll create a /vivaldi directory within /var/opt, and then the updated items will be created within that. Then, you can simply copy them to the required browser's /opt/directory.....or in MY case, the portable-browser directory.

The 'zilla-based browsers, of course, download and automatically install WideVine from their own repo, as & when required, simply by ticking the DRM check-box in Preferences.

Hope that's of some use to you.

Mike.

I thought that I'd try running Puli in a container (see thread). Starting jwm produces the following error:

"iptables v1.6.0: can't initialize iptables table `filter`: table does not exist (do you need to insmod>)
Perhaps iptables or your kernal needs to be upgraded. 

I see two likely possibilities for this error:
1. I need to add the kernal modules to one of the layers of my sandbox or
2. the capability droping is preventing this.

An easy fix would be to either remove the autostart section from .jwmrc or alternatively find out which .desktop item int he autostart folder is trying to call iptables. I'll troubleshot this and report back.

s243a wrote: ↑Tue Jan 26, 2021 12:58 am

I thought that I'd try running Puli in a container (see thread). Starting jwm produces the following error:

Code: Select all

"iptables v1.6.0: can't initialize iptables table `filter`: table does not exist (do you need to insmod>)
Perhaps iptables or your kernal needs to be upgraded. 

I see two likely possibilities for this error:
1. I need to add the kernal modules to one of the layers of my sandbox or
2. the capability droping is preventing this.

An easy fix would be to either remove the autostart section from .jwmrc or alternatively find out which .desktop item int he autostart folder is trying to call iptables. I'll troubleshot this and report back.

Dear s243a,

Thanks for your post and sorry for the late response.

I played with Xephyr on Puli 7.3 as follows:

A) Without rox and jwm

• First, started Xephyr and opened gnumeric inside - both by root. Passed.

• Then opened two Xephyr instances by root with gnumeric (as root) and Firefox (using "run-as-spot"). Gnumeric passed. Firefox: The Shields UP! tool confirms that the Xephyr sandbox works effectively. Good sound in Youtube. Problems with the drop-down bookmark menu. WebGL Water Speedtest is very slow.

• Then issued "su spot" and opened abiword in Xephyr. Passed.

See the below screenshot as an example for the first series of tests:

So, there are no critical issues in this mode yet.

B) With rox and jwm

From a termiinal window, I issued the following commands one by one:

Xephyr -br -ac -noreset -screen 1024x768 :1 &

export DISPLAY=:1

rox -p /root/Choices/ROX-Filer/PuppyPin

jwm & 

sleep 2

echo ready

Please notice that I started rox before jwm. I did not receive error message regarding iptables. However,

• some environmental settings that are based on the common layers, such as hostname, firewall, network, brightness, the installed applications, etc., are the same for the outer and sandboxed inner systems. I think this is normal.

• Some packages (defaultbrowser, mpv etc) cannot run in the outer and inner environment simultaneously as I intentionally configured so in Puli.

• One thing is weird that the sandboxed instance does not inherit the keyboard/language parameters automatically. For me, the outer Puli has been set to hu_HU while the sandboxed one started as en_US. I corrected manually using the (inner) menu.

• A few Xephyr instances can be nested in each other. They work as I described above.

However, I did not dig more deeply into Xephyr, i.e., I played with those instances opened from within X.
Of course, Xephyr does not establish "Puli sandboxed within Puli" but provides a bit more secure environment for some applications.

See the below screenshot that represents the second series of my tests.

See the Xephyr package uploaded to my https://sourceforge.net/projects/puppys ... /packages/ folder.

Have fun!

Regards,

gjuhasz

Hello community Haven't been around too much lately because of a career change. Still using Puppy daily both @Home and work. Just so you know.

I FINALLY got Puli to work (7.2) after SO many attempts. Posting from it right now, 64bit version.

Everything seems to be fine and working almost as flawlessly as my all time favorite Bionic. Only thing that doesn't work is the scroll wheel of my mouse (both keyboard and mouse on the same usb adapter which might be the culprit) and I cannot adjust the volume from the tray icon. I'm sure there will be something somewhere that will resolve this as I haven't figured out all the settings, profiles and what have you yet.

Great distro, awesome job. Happy camper here.

Regards, bullpup.

puppytrue wrote: ↑Wed Jun 09, 2021 3:23 pm

In Puli 32/64 bit first time, what is login and password ?

Login: root
Passwd: root

You can easily change it after the login.

puppytrue wrote: ↑Mon Jun 28, 2021 12:44 pm

After boot from USB profile crazy Firefox and other browser no start, why ?

Dear puppytrue,

Thanks for your posts and the interesting requests.
Unfortunately, I have very limited time due to a huge post-COVID workload nowadays. Thanks for your understanding.
I try to answer you here and in one or more follow-up posts.

First, I will try to reproduce the Firefox issue (you reported it on Sun Jun 27).
You can install Firefox in the Mild profile (simply click the latest Firefox-xx.x.tar.bz2 file or smartload it from the boot device). Then, from the menu, select Settings > Switch to Crazy and check if it works.
FYI: Firefox or Chrome, Iron, Slimjet, etc., won't boot automatically with Puli unless you smartload one or more of them.

Have fun!

Regards,

gjuhasz

“Safely” – well, everything is relative. And I still have my doubts.
This exploration was motivated by the request by puppytrue who inquired about the possibility of running metatrader4 under Puli, viewtopic.php?f=40&t=484&p=30178&hilit=puli#p30178 or EasyPup. [EasyPup and –for the sake of completeness-- EasyOS are discussed here: viewtopic.php?f=33&t=1534&start=10.

The first challenge Web-Facing Windows programs presents is that from Linux they have to be run under Wine and Wine constructions, themselves, do not provide any anti-malware or intrusion detection or prevention facilities. WineHQ cautions about that and notes that it is left up to the various Linux distros to handle those problems. So the best advice remains (a) don’t run Windows programs under Wine; and (b) if you have to make use of Windows Programs run them while not connected to the internet. Obviously, that advice can’t be followed if you need to run a Windows program whose purpose is to access and obtain information from the Internet.

Puppys standard method of protecting its system is isolation. For example, EasyOS can run a subordinate operating system in a container. Additional measures can be taken to protect that subordinate operating system. But even if they fail, malware and hacker’s can’t get beyond the subordinate system to the primary operating system.

Puli can operate from a USB-Key which, after boot-up, can be unplugged. Indeed, it’s designed that way, with the USB-Key only re-plugged when you need to preserve something; and then even such otherwise routine tasks as copying require confirmation. Properly maintained, Puli will be as pristine as the moment you deployed it. Additionally –unique among Puppys-- Puli includes modules which can detect attempted intrusions together with several user selected choices for automatically responding to such attempts.
Puli operates differently than other Puppys, in one way more conveniently, in another far less. The one way is its smartload feature. Puppys can be extended by a User beyond its built in application by installing applications, loading SFSes, starting –even creating links to-- portable-applications and AppImages. If desired making such extensions persistent by writing them –or links to them--to a SaveFile or SaveFolder that will be put to use on boot-up.
Although Puli can SFS-load an Application.SFS, can install a pet or other package and immediately use it, and can start an AppImage or portable-application, it’s smartload feature enables another way to make use of applications. The User can maintain one or more smartload files in the /profiles/common folder on the partition adjacent to Puli’s system files. These are just lists of possible applications. You can edit these lists in a text-editor. See Configuring Puli Screenshot.

On boot-up, the User selects a list by its ending number (otherwise smartload without any number is selected by default) and Puli reads the list and executes routines making the applications noted available. An application NOT beginning with a minus sign will be ‘installed’. Using the displayed smartload as an example, Puli would make the 32bit compatibility sfs files available.

But Puli does not make use of SaveFiles/Folders for preserving system changes. Instead, the User can chose to create smartsaves. Note the plural: several smartsaves –each different-- can b created and the User can choose which to apply. However, unlike a Puppy’s SaveFile/Folder, Puli doesn’t make use of smartsaves immediately on boot-up. Rather, the smartsaves have been written to a backup folder on Puli’s partition. Moments after Puli has completed booting it dismounts that folder. To make use of a smartsave-backup, the User must remount the partition, file-browse into the backup folder and drag a backup onto the ‘restore’ script. See Puli-backup Screenshot.

Puli then writes the contents of the backup into RAM, reconfiguring RAM’s content to include that which was preserved in the backup. All of which (a) requires the User’s manual intervention and (b) takes time.
Could Puli’s mechanisms even be used to make Windows programs available under Puli? Spoiler Alert: Yes, it can and I’ll provide the recipe below. But appreciating the problem and why the recipe takes its form, will help to explain why I think/hope there is a better way.
Puli 7.3 (and 7.2) are 64-bit Linux operating systems. Most ‘useful’ Windows programs --and in particular the one desired by puppytrue-- are 32-bit. Until recently, the ‘recipe’ for running a 32-bit Windows program under 64 bit Puppies was:
1. SFS-Load a 32-bit compatibility SFS (or install a pet)
2. Open a terminal and type the command ‘ldconfig’.
3. Triggered by that command, the 64 system establishes communicating links with the 32-bit a libraries of the application in Step 1. [On recent Puppys, SFS-loading, itself, will trigger that command]. This takes some time. Wait.
4. Install a 32-bit Wine pet (or SFS-load a 32-bit Wine.SFS).
5. Open a terminal and type ‘wine winecfg’. Triggered by that command, communication links are created between the Linux operating system and Wine application layer; and a ‘prefix’/folder is created, to wit: /root/.wine/drive_c/, and other folders --such as .../drive_c/program files/-- which wine will use. Until that happens, Windows programs won’t run nor is there any location into which programs which have to be installed can be installed.
6. Frequently triggered in Step 5, Linux operating system must be configured to recognize that the ‘mime-type’ exe is associated with Wine so that Wine will open a file/program ending with ‘exe’. But that relationship isn’t always established automatically. When it isn’t, the User must manually establish it.
7. Only after the above can the User run a Windows program (portable) or the setup file of an ‘installable’.
Puli’s repo has a 32-bit compatibilty SFS and a Wine.SFS. [But that Wine.SFS is designated ‘64’ and I had doubts that it would be able to run all 32-bit programs. So I opted to use the 32-bit compatibiity SFS and Version2013’s wine 5.22 v.3.1.pet, discussed and linked to in my post on the EasyPup thread.]. Nothing suggests that an exe can be smartloaded. And while both the 32-bit compatibility SFS and some form of Wine can be smartloaded, nothing suggested that the 32-bit compatibility links (Steps 2 & 3) will be created before attempting to smartload Wine; nor that Wine would be configured (Step 5).

[This seems a good place to digress to discuss Wine.AppImages which solves some problems and create others. Recent Wine.AppImages contain both 64-and-32 bit systems and so do not require a previously configured 32-bit system. Puli can smartload a Wine.AppImage [must have some variation of ‘appimage’ in its name]. But doing so does not trigger ‘wine winecfg’ nor associate Wine with the exe mime-type. See this thread, for things you’ll want to do before creating a smartbackup. viewtopic.php?f=142&t=1754. To associate exe under it, after setting up the link per that thread, Right-Click any exe file, Select “Set run action”, check the ‘default for all…’ button, type wine32 in front of "$@”, then click the “Use Command” button.
FWIW, portable-wine can also be use with Puli. However, that would defeat the reason to run Puli as portable-wine can only be run from a mounted partition.].

The ‘orthodox way’ -- Using only Puli’s tools:
1. Download Puli’s 32-bit compatibility SFS and place it in the packages folder. [That folder was missing from some Puli ISOs. If it is, Right-Click an empty space adjacent to Puli’s system files and folder, Select New>Directory, and give it the name packages. Spelling matters].
2. Make certain that “32bit” is on the default smarload file and is not preceded by a dash.
3. Boot into Puli.
4. Download one of Version2013’s Wine pets. Also download his wine_extras-v2.1.pet from https://version2013.yolasite.com/page1.php#wine_menu. [This creates menu entries for ‘Builtin’ Wine programs such as WineFile (+/- Explorer).].
5. Left-Click the Wine pet to install it.
6. Make certain that your internet connection is again working. Open a terminal and type “wine winecfg” without the quotes. Among other things, that command will trigger an attempt to download and install mono and gecko.
7. Left-Click the wine_extras-v2.1.pet to install it. You can use Menu>Setup>Menu Manager to turn off the menu-display of any unwanted program.
8. Optional—Recommended: File-browse into /usr/share/applications; then drag the WineFile.desktop to your desktop. That creates a desktop icon. You can edit-out the “.desktop” by Right-Clicking it and Selecting Edit. Having quick access to WineFiles make life easier. Selecting an ‘exe’ file using it will run that program even if you haven’t otherwise configured Puli to recognize the exe mime-type.
9. Download and install any Windows programs you’ll always want to have available. Recommended Atlantis-lite, and SumatraPDF. (See amethyst’s posts about these posts on the Wine thread). For Windows portable programs (those which don’t/won’t install) select /opt as the location from which they are to be run; bookmark the /opt folder.
10. Create any symbolic-links, book marks, and menu-entries you’ll always want to have available. At the end of this post you’ll find an attached template for creating menu-entries.
11. When you’re finished, click Puli’s desktop “backup” icon or shut-down, selecting ‘backup’. Wait. It takes some time to write the backup (especially a large one) to the USB-Stick.

The Unorthodox Way – noting differences and caveats.

1. Download the 32-bit compatibility SFS as above. But also download nicOS-Utility-Suite, from here, viewtopic.php?p=12983#p12983 and extract it. Place both the 32-bit compatibility sfs and the nicOS-Utility-Suite.sfs in the packages folder.
2. Edit /profiles/common/smartload to include a nicOS line –note, that’s a Capital O, not a 0/zero. Just the word nicOS should suffice. Make sure that these listings are not preceded by a ‘-’. Watch the terminal during bootup to see that nicOS is being smartloaded. After bootup there should be a nicOS listing on Menu>Utilities. If absent, reboot, make changes and try again.
3. Follow the rest of the ‘Orthodox’ recipe except for Step 11. Instead, run Menu>Utilities>NicOS-Utilities Suite. When its GUI appears, Select “4: nicOS-Save2SFS”. Then Select ydrv. If you have a lot of RAM –my guesstimate at least 4 Gbs-- choose the option to create in RAM eliminating the time needed to write to storage media. And perhaps the need to mount a partition. I did it in RAM so am not sure about that.
4. When nicOS-Save2SFS has finished a ydrv_puli7.3.sfs will have been created. Drag/move/relocate that adjacent to the other Puli system files, e.g. zdrv_puli7.3.sfs.
5. Warning: In Steps 1 and 2, Do Not smartload anything you don’t want as a permanent part of your system. Under Puppys, nicOS-Save2sfs excludes ‘additional SFSes --e.g. itself and a 32-bit compatibility sfs-- from what gets written to a ydrv.sfs. But Puli’s smartload feature locates files --even those from an SFS-- in a location where nicOS will write them to the ydrv.sfs.
6. On next bootup, Puli will automatically use ydrv_7.3.sfs. There is no need to smarload anything you preserved in it. It is now as much a part of your operating system as if it had been included in the ISO. [Of course, you can move/delete it]. You should remove the 32-bit compatibility sfs from the /packages folder, and edit the smartload file accordingly.
[I’ve referred above to a ydrv. nicOS-Save2sfs can also create an adrv.sfs. Read the nicOS-Utilities thread for pointers as to their respective uses].
7. Warning: One of the major reasons for choosing Puli rather than a different ‘Puppy’ is Puli’s inclusion of modules to detect attempted hackers and twart their attempts. I don’t think this Unorthodox method will adversely affect that. But, frankly, I don’t know enough about either that module or how nicOS-Save2sfs works to be certain.
My understanding is that gjuhasz based Puli 7.3 (and 7.2) on Bionicpup64. Consequently, it is likely that any application which functions under Bionicpup64 will also function under Puli 7.3. I can confirm that OscarTalks’ vpn-onoff for Bionicpup64 does. You can download it from here: http://smokey01.com/OscarTalks/. Included in your ydrv or smarloaded, you can now enjoy an encrypted network from an operating system which only exists for the moment in your computer’s RAM. The free VPN providers included in vpn-onoff are OK. But, protovpn is more highly regarded, even its free version. Look for the posts about setting it up. And, of course, well-thought-of paid VPNs provide even more security and choices.
Puli can also use tor, LibreWolf, Ungoogled-Chromium, a ‘hardened’ firefox-esr’ or any of the other security-and/or-privacy oriented web-browsers discussed and available on the Forum. Any ‘portable’ published by fredx181 or Mike Walsh can be used by physically locating them in /opt and setting up links and menu entries accordingly. Note again my recommendation to read the posts concerning the use of nicOS-Save2sfs.
Templates

@ puppytrue: metratrader and its two companion programs install into wine's false drive_c...'Program Files'. Included are templates for creating menu entries for them. By the way, while metatrader 5 installed when I used EasyOS, it didn't when I used Puli. So download the metatrader 4 setup file.
@ all. The Templates do not include the actual programs. You'll have to download and install those yourselves. As you'll see when you've unzipped them, there are two Top folders: root and usr. Drilling into usr, you'll eventually come to 'desktop' files in /usr/share/applications which you can copy to the actual /usr/share/applications if you've installed the actual applications. Or use them as Templates for creating desktop files for programs you actually have.
The arguments in all desktop files call both executables (Exec=) and icons (Icon=) from /root/my-applications/bin. Placing icons there just makes it easier (fewer scribner errors, just cut & paste) to write desktop files. Consequently, when you drill down into the 'root' folder you'll find both icons and bash-scripts in /root/my-applications/bin.
On my system, sumatrapdf was unpacked to /opt. All other programs had to be installed to wine's 'Program Files' folder. So the Templates provide examples of both situations. After a program is installed you can check to see if the script will open it by clicking the script or running it in a terminal. If there's a problem, make certain that every file and folder name is properly spelled and capitalized; that there are spaces where spaces belong and none where they don't.
Obviously, you'll want to have functional menus before creating a smartsave or ydrv.sfs.

@ puppytrue, I've only scanned thru your last post and have no intention of attempting to respond to it beyond the following:
Puppys and their variants such as Puli are fan-driven operating systems. Everyone is welcome to use them and any of their components "As-Is". Everyone is entitled to contribute if they want to. Those of us who contribute do so because we enjoy the challenge; enjoy working on puzzles. We are all volunteers. Nothing can compel us to undertake a challenge which doesn't interest us. Certainly not posting the same questions several times. If someone wants to go beyond what has been provided they are expected to first work their way through what has already been provided: to know the system, its tools and available applications so that their next question presents a technical road-block, not just a demonstration of an unwillingness to do the work.

I'd don't know how the Mac or other operating systems attempt to achieve security or privacy. And I'm not inspired to wade through posts about them to find out. Which is the best VPN? That may depend on whose voicing an opinion and how much you're willing to spend. My best guess is that few will be better than the paid version of ProtonVPN which operates out of and provides servers in Switzerland: long known for its protection of private transactions and not subject to either the US's, the EU's, Russia or China's Laws or demands for access as a matter of routine.

If you take up the challenge presented by my recent posts you can boot Puli, unplug the USB-Key it booted from --thus assured of a pristine operating system on next boot-up-- and still run privacy oriented web-browsers such as Ungoogled-Chromium, dissenter-browser, LibreWolf, tor and hardened firefox, and otherwise conduct your current session of web-work via a fully encrypted VPN, and (hopefully ) still having Puli's hacker-tworting systems doing their job.

If you know of any operating system which can achieve more I'd be interested in the details of how they accomplish that. But if you're not sufficiently interested to undertake the work of finding out how they do it and reporting that in detail I'll assume they can't.

puppytrue wrote: ↑Mon Jul 26, 2021 12:28 pm

mikeslr wrote: ↑Sat Jul 24, 2021 8:32 pm

Metatrader-Puli.png

Thanks.
How to do it step by step ?

Possible with ctrader.exe ?
https://ctrader.com/download/

Step by step for Metatrader, open your web-browser to, viewtopic.php?p=32145#p32145. Read the entire post so that you'll know what and why.
For example, you've now mentioned cTrader. You'll want to see if the Windows 7 ctrader-spotware-setup.exe from here, https://ctrader.com/download/ will install under Wine, and works before creating a smartbackup or a ydrv.sfs. If it doesn't, cTrader also offers a link you can bookmark supposedly in any web-browser.

After you've read the entire post, backup to the paragraph with the Heading "The ‘orthodox way’ -- Using only Puli’s tools". It provides a recipe using, as the Heading says, Using only Puli's tools.
Below that is the recipe for creating a ydrv.sfs instead of smartloading. That starts with the Heading "The Unorthodox Way – noting differences and caveats". Basically, it says to follow the previous recipe's instructions until you reach Step 11 and having, in Steps 1 & 2 placed nicOS-Utility-Suite in the packages folder and edited smartload to list it. Then, having completed Step 10 --rather than running smart-backup-- you run nicOS-Utility-Suite, select Save2SFS and create a ydrv. But read the recipe again for details.

I'm not going to try to get cTrader working. That's something only you are interested in doing. As far as I know, cTrader's exe won't run under Wine: https://www.winehq.org/search?q=cTrader. But the results reported are old. If you want to try, than I would suggest after Step 8 of the 'Orthodox' recipe --before installing metatrader-- see if you can install and run cTrader and whether it is fully functional. If it isn't shut-down without saving anything in any manner and start from scratch. You don't want to permanently preserve files which don't work and may interfere with those which otherwise would. And, as aforesaid, cTrader supposedly can be run from any web-browser. Using Palemoon and a Hardened-firefox, its login page displays.
Recommended browsers to try: ungoogled-chromium, librewolf, a hardened-firefox-esr. You'll find threads about them on the Forum.

@ Puppytrue,

This is your project and it is up to you to put in the work to find out whether it is possible to use WireGuard with Puli in their current manifestations. A little research about WireGuard revealed it to offer improved security, and has generally received praise including from LInus Thorvald. But, OOTB it has 'privacy' flaws which nordvpn and some other reputable vpn providers have 'worked around'. https://restoreprivacy.com/vpn/wireguard/

The following are some hints of the possible problems and possible solutions.
allendiggity provided a package and instructions for fossapup64 here, viewtopic.php?p=6974#p6974. I've asked for clarification about kernel-modules on that thread and it is probably wise to wait for aliendiggity's reply.
The problem lies in that both Puli's security profiles and the wireguard package write to /etc. I know little about what happens in /etc.
Like Puppys, it is both possible and easy to swap kernels under Puli. But as I don't know how Puli establishes its Security Profiles, I don't know if swapping kernels will break them. Before posting the question I assumed that fossapup64's zdrv.sfs (renamed zdrv_puli7.3.sfs) was needed. So I swapped aliendiggity's vmlinuz for Puli's, and swapped fossapup64's zdrv.sfs for puli's.
As puli doesn't make use of a SaveFile like Puppys, I had remasterd puli7.3.sfs to include the /lib/modules aliendiggity provided. During boot-up the terminal gave notice that the security profile was broken. But Puli booted to desktop and all other systems appeared operable. I was able to configure wifi. However, both EasyOS and Fossapup64 can already use wireguard, there's really little reason to use it under a broken Puli. I can't be sure that the 'break' might have been a consequence of the remaster.
If I were to explore this problem again, here's how I'd do it:
Earlier in this thread I explained how to create a ydrv_puli7.3.sfs using the Save2SFS module of nicOS's utility Suite. When part of your system that module can also create an adrv or create a new ydrv that will include both its initial contents plus the new ones you have in RAM. Under Puli, once used, it is an application available from your Menu as it has been included in the a/ydrv. So, either boot into puli already using such a/ydrv, or include nicOS-Utility-Suite in /packages with a notation to use in on smartloads.
With aliendiggity's vmlinuz having been swapped in (and such instructions aliendiggity provides about zdrv) having booted into Puli you can follow the rest of the instructions he has already provided. However, one of them requires the installation of resolvconf via Puppy Package Manager. Bionicpup64 PPM didn't have it and probably neither will Pul's PPM. But you can download it from here, http://archive.ubuntu.com/ubuntu/pool/u ... 10_all.deb. Left-Click to install. Then use Menu>Filesystems>Pfind to see if it is where WireGuard expects it to be. If not create a symlink per aliendiggity's instructions
When you're finished create either an adrv or a ydrv using the Save2SFS module.
Will it work? I don't know? Will Puli's Security profiles continue to work? I don't know. But this is your project and I (and perhaps others) concerned about security would be interested to find out (a) exactly what you did; and (b) and whether or not it worked.

When you've posted that information perhaps someone more familiar with the workings of /etc and/or Puli's security profiles may take a sufficient interest to pursue this further.

(Sorry for the long silence.)

Dear Mike,

I really appreciate your efforts in digging into the deep details of Puli. I see that you are the best expert in this area and thanks for all of your posts.
To tell the truth, I cannot advertise such abilities because I have to keep in mind that Puli is (hopefully widely) used in schools and if the students play/operate with the full feature set of Puli (e.g using tor browser or specific protocols, or by challenging hackers, etc) then the headmaster can rule out Puli from the school.

Dear puppytrue,

It seems that you want to use third party .pet .deb .sfs packages in Puli under different security profiles (Rigorous, Crazy).
Please note that the published versions of Puli contain simplified security profiles, which, however, can even be considered as unusual examples of cyber security. They become active only during the use of some supported modules (browsers, etc) that invoke the netchecker or the netkiller scripts, or implement special tricks to hide the environment (in the Lazy profile). Consequently, the rest of the Puli modules, including the Puli-compatible third party packages run under the (still secure) Mild profile by default.
Of course, Puli offers increased defense for them as well: they can run segregated in a secure firejail sandbox, or in a nested x server (xephyr).
I tested then added qTox, a secure peer-to-peer chat module to the supported packages.
I recommend that the advanced Puli users, like you, extend the list of the fortified modules or even create new security features for yourselves. Thanks in advance.

Have fun!

Regards,

gjuhasz

Dear puppytrue,

For Puli 7.3, please use the qTox-v1.17.3.x86_64.AppImage package.

You can download it from my 64-bit repository:

https://sourceforge.net/projects/puppys ... /packages/

If you smartload it during bootup, then you can start it by clicking the Phone desktop icon.
If you decide to load it later, then please put this AppImage to the /opt/AppImages/ folder (a new "..." desktop icon appears).

Which version of Firefox are you using? I suggest you try the latest from the link above.

Have fun!

Regards,

gjuhasz

@puppytrue Questions, questions... and more questions....,can't you do better ?
Have you thought about why almost nobody is replying ? (and if someone replies, you don't answer, see above)
I think because you never, ever, write about what exactly you tried, to accomplish what you want (let alone how with details).
That way you will never get any help, and be... lonely .
Or maybe you want to be lonely? Stop bothering us then, please! Useless!

P.S. and stop cross posting.

EDIT: Sorry, above is a bit too rough, on second thought.