Env variable for different banks

[diraol]

The link for Banco do Brasil warsaw is different from CEF.

Which make me think that they can be different from each other. Or that they can become different in the future.

So, is it possible to add a 'environment variable' (or CLI arg) to choose between banks? (This would change the warsaw download link, the bank url, etc).

[farribeiro]

The warsaw is personalized for the bank, according the post on BR-Linux[1] a way is on Dockerfile isolated list all URL of warsaw supported banks then build image OR a selector on time of running the container. @lbssousa commented about this selector. But in build image I think isn't possible.

PS: But essencially, warsaw is the same application, on my tests.

[1] http://br-linux.org/2017/01/warsaw-e-banco-do-brasil-no-linux-diebold-nixdorf-envia-esclarecimento-aos-leitores-do-br-linux.html

[danielmenezesbr]

Although Dockerfile installs https://cloud.gastecnologia.com.br/cef/warsaw/install/GBPCEFwr64.deb (Caixa Econômica Federal), currently it's enough to access Banco do Brasil without any additional configuration.

[farribeiro]

@diraol See above the answer of @danielmenezesbr if the one warsaw for all banks, is possible.

[diraol]

@farribeiro ok then, if you want to close this issue be comfortable to do so.

I just want to point out that using the CEF warsaw seems to work ok, at least for now. We cannot be sure if everything really works* not even that it will always work.

• Probably no one have tested all functionalities from other banks than CEF. And I don't even think this would be possible without a high cost.

[farribeiro]

Yes, has a high cost to maintain all warsaw solution updated*, eg. Itau, BB, CEF and others listed on warsaw diagnostic website[1], but also can automated build image for each bank or some engine to select the which bank and respective warsaw, installing and opening the browser.

For using a CEF is for comodity, i copied the @lbssousa logical structure to create this project, basically is a adaptation of his Vagrantfile and no have a preferred bank. This issue will be opened to new suggestions and facility the maintain more banks on the solution.

[1] http://www.dieboldnixdorf.com.br/warsaw

PS: I have no idea to scan new warsaw releases, like a bot, but when Ubuntu update their image (wscef use ubuntu:latest, aka xenial), the dockerhub automatically create a image with the last firefox and warsaw versions.

[farribeiro]

Any more question about the discussion?

If you have any idea for engine, create a pull request for continuing discussion and will close this Issue. I want to maintain the discussion open, but not the Issue the isn't good local for this. On the PR is better.

[farribeiro]

Link to PR #25

[pccarvalho]

Checked with my Ubuntu 16.04 and worked fine. I had to make some adjustments with xhost because it is a corporate desktop and my userid is not 1000. And works for Caixa, BB and Itaú.
At home I have Fedora with Plasma and "su -c" kept asking for password. I had to change Dockerfile to install the sudo package and replace "su -c" to "sudo" in startup.sh. No issues whatsoever after the modifications. Caixa, BB and Itaú ok.

PS: Is it English required here? Since this container is useful only to Brazilian banks shouldn't we be speaking Portuguese?

[farribeiro]

Thanks to contact... By order:

Checked with my Ubuntu 16.04 and worked fine. I had to make some adjustments with xhost because it is a corporate desktop and my userid is not 1000. And works for Caixa, BB and Itaú.

This solution don't use xhost but xauth, as @lbssousa pointed is more secure ... See the PR #1 . And about the you UID, modificate the Dockerfile and regenerate a image.

At home I have Fedora with Plasma and "su -c" kept asking for password. I had to change Dockerfile to install the sudo package and replace "su -c" to "sudo" in startup.sh. No issues whatsoever after the modifications. Caixa, BB and Itaú ok.

I create the solution on Fedora and the solution use the Ubuntu base image, @lbssousa tested on OpenSUSE Tumbleweed with success. In most case, disabling the SELinux OR pointing Z arguments on volumes on docker-compose.yml works, as see on the selinux branch, sorry I deleted this, like this:

- <src>:<dest>:Z or - <src>:<dest>:ro,Z

I not tested if Ubuntu base image have sudo installed and them I choose the su to execute on root in the container. Building this solution, I prompted remove the root password of container.

PS: Is it English required here? Since this container is useful only to Brazilian banks shouldn't we be speaking Portuguese?

I choice English because two reason, training and most opensource projects use this language.

[pccarvalho]

Thanks to contact... By order:

Checked with my Ubuntu 16.04 and worked fine. I had to make some adjustments with xhost because it is a corporate desktop and my userid is not 1000. And works for Caixa, BB and Itaú.

This solution don't use xhost but xauth, as @lbssousa pointed is more secure ... See the PR #1 . And about the you UID, modificate the Dockerfile and regenerate a image.

Changing UID really didn't work for me. At work we authenticate to a corporate AD server using Centrify as client. We are given an ID that is a long number like 1111491098. For some reason, useradd does not like it. It took all my 120GB disk space while regenerating the image and then failed with no disk space left error. Fortunately, the machine has a install user with UID 1000. I simply called "xhost +SI:localuser:installuser" before starting the container. Two benign side effects here: no changes for my co-workers and no changes for me at home.

At home I have Fedora with Plasma and "su -c" kept asking for password. I had to change Dockerfile to install the sudo package and replace "su -c" to "sudo" in startup.sh. No issues whatsoever after the modifications. Caixa, BB and Itaú ok.

I create the solution on Fedora and the solution use the ubuntu base image, @lbssousa tested on OpenSUSE Tumbleweed with success. In most case, disabling the SELinux OR pointing Z arguments on volumes on docker-compose.yml works, as see on the selinux branch, sorry I deleted this, like this:

- <src>:<dest>:Z or - <src>:<dest>:ro,Z

I really didn't want to mess with SELinux configs. I will try the Z arguments approach

I not tested if Ubuntu base image have sudo installed and them I choose the su to execute on root in the container. On build this solution, I prompted remove the root password of container.
It does not. But it is just a matter of including "sudo" in the list of packages to install. I think that using "sudo" is as good as "su -c"

PS: Is it English required here? Since this container is useful only to Brazilian banks shouldn't we be speaking Portuguese?

I choice English because two reason, training and most opensource projects is this language.

No problem here. And congratulations for the good work!