browservice, enables browsing the modern web on historical browsers

[Amiwell]

For me it is an emergency solution, but some users complained because they could not access some sites

[Amiwell]

Does this suggest that aros hosted could use the same host for browserservice? Perhaps irrelevant but curious

Good question. I'm curious about the answer.

But if you are running AROS hosted you have access to the browsers on the host system already.

Maybe even Host Bridge could launch them from AROS.

In Full Screen Mode you cannot use Linux applications you would need a dedicated X server, you can only have Icaros in the window but there is a problem with the De di Linux decorations if you can remove then you will have the illusion of having Icaros in full screen

[magorium]

@salvo:
Congratulations on your progress.. It should be able to solve most (if not all) browser related issues.

Do note the remarks on github about the insecurity though.... you have to be careful from where the proxy can be reached (that can be from the outside world wide /mean/ internet).

Also note the remarks on cookies and password saving etc. (cleanup on exit by default but you are allowed to change it). Note that according to the documentation each individual client uses the same browserservice (and its settings). I would consider that a (security) flaw.



@Glinx:

Does this suggest that aros hosted could use the same host for browserservice? Perhaps irrelevant but curious

I fail to see why that would not be able to work. I am assuming the git site mentioning the requirement for using a separate machine have a few pro's in comparison to running it native.
- CEF is a beast, requires quite some cpu cycles. Combine it with the proxy and more or less constant image sending and you are using even more cycles.
- Using it as standalone allows you to use the service from different clients (seems to be a common use-case). Again cpu cycles and also memory hogging.
- using the service as standalone allows you to take some security measure that would be bothersome to do when located on the same host.. Separating client from service adds an additional layer of security and should be easier to maintain.

Running the service form a docker should be able to take care of most security issues (when properly setup) though.

Still no practical experience with this particular service but I do have some experience with using CEF for complete other goals. That more or less works in a similar fashion and is perfectly (cap)able to run on the same host.

[Amiwell]

yes magorium on the site there is this annotation for connecting the client on proxy server

"Only the proxy server needs an Internet connection; the client only needs to be able to connect to the proxy server. It is advisable not to expose the client directly to the Internet. One possible network setup is to have two interfaces on the proxy server: one for Internet and another for the local connection to the client"

So you have to connect Aros to the Host computer directly but in this case how network preferences must be configured?

[Amiwell]

Now I'm not using the service but I usually connect via the internet locally

[Amiwell]

There have been fixes of this service now the implementation with Odyssey has improved

[Amiwell]

There are no energy consumption problems using this method, currently as host I have an old laptop and aros I use it with the Acer Aspire One