armadito / deprecated-web-ui Goto Github PK

Proto Recv-Q Send-Q Adresse locale          Adresse distante        Etat       PID/Program name
tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      -               
tcp        0      0 127.0.1.1:53            0.0.0.0:*               LISTEN      -               
tcp        0      0 127.0.0.1:8888          0.0.0.0:*               LISTEN      -               
tcp        0      0 127.0.0.1:36980         127.0.0.1:8888          FIN_WAIT2   -               
tcp      377      0 127.0.0.1:8888          127.0.0.1:37004         ESTABLISHED -               
tcp        0      0 127.0.0.1:36996         127.0.0.1:8888          ESTABLISHED -               
tcp      419      0 127.0.0.1:8888          127.0.0.1:36976         CLOSE_WAIT  -               
tcp        0      0 172.28.219.59:40546     192.30.253.124:443      ESTABLISHED 6786/firefox    
tcp        1      0 127.0.0.1:8888          127.0.0.1:36970         CLOSE_WAIT  -               
tcp        0      0 172.28.219.59:57580     151.101.60.133:443      ESTABLISHED 6786/firefox    
tcp      462      0 127.0.0.1:8888          127.0.0.1:36972         CLOSE_WAIT  -               
tcp        1      0 127.0.0.1:8888          127.0.0.1:37006         CLOSE_WAIT  -               
tcp        0      0 127.0.0.1:36984         127.0.0.1:8888          FIN_WAIT2   -               
tcp        0      0 127.0.0.1:36990         127.0.0.1:8888          ESTABLISHED -               
tcp        0      0 172.28.219.59:42476     64.233.184.95:443       ESTABLISHED 6786/firefox    
tcp        0      0 127.0.0.1:36978         127.0.0.1:8888          FIN_WAIT2   -               
tcp        0      0 172.28.219.59:57566     151.101.60.133:443      ESTABLISHED 6786/firefox    
tcp        0      0 127.0.0.1:36992         127.0.0.1:8888          FIN_WAIT2   -               
tcp        1      0 127.0.0.1:8888          127.0.0.1:36978         CLOSE_WAIT  -               
tcp        0      0 172.28.219.59:57572     151.101.60.133:443      ESTABLISHED 6786/firefox    
tcp        1      0 127.0.0.1:8888          127.0.0.1:36984         CLOSE_WAIT  -               
tcp        0      0 172.28.219.59:40480     185.10.252.142:5223     ESTABLISHED 5108/pidgin     
tcp        0      0 127.0.0.1:36976         127.0.0.1:8888          FIN_WAIT2   -               
tcp        0      0 127.0.0.1:36982         127.0.0.1:8888          FIN_WAIT2   -               
tcp        0      0 172.28.219.59:38250     52.21.198.138:443       TIME_WAIT   -               
tcp      192      0 127.0.0.1:8888          127.0.0.1:37002         ESTABLISHED -               
tcp        0      0 127.0.0.1:37004         127.0.0.1:8888          ESTABLISHED 6786/firefox    
tcp      419      0 127.0.0.1:8888          127.0.0.1:36982         CLOSE_WAIT  -               
tcp        0      0 172.28.219.59:57568     151.101.60.133:443      ESTABLISHED 6786/firefox    
tcp      192      0 127.0.0.1:8888          127.0.0.1:36996         ESTABLISHED -               
tcp      192      0 127.0.0.1:8888          127.0.0.1:36990         ESTABLISHED -               
tcp        0      0 127.0.0.1:36974         127.0.0.1:8888          FIN_WAIT2   -               
tcp        0      0 172.28.219.59:57878     151.101.60.133:443      ESTABLISHED 6786/firefox    
tcp        0      0 127.0.0.1:36998         127.0.0.1:8888          FIN_WAIT2   -               
tcp        0      0 127.0.0.1:37002         127.0.0.1:8888          ESTABLISHED -               
tcp        0      0 127.0.0.1:37006         127.0.0.1:8888          FIN_WAIT2   -               
tcp        0      0 172.28.219.59:32848     185.10.252.153:443      ESTABLISHED 6786/firefox    
tcp      378      0 127.0.0.1:8888          127.0.0.1:36998         CLOSE_WAIT  -               
tcp        0      0 172.28.219.59:57564     151.101.60.133:443      ESTABLISHED 6786/firefox    
tcp        0      0 172.28.219.59:57876     151.101.60.133:443      ESTABLISHED 6786/firefox    
tcp        0      0 172.28.219.59:44416     172.217.16.78:443       ESTABLISHED 6786/firefox    
tcp      404      0 127.0.0.1:8888          127.0.0.1:36992         CLOSE_WAIT  -               
tcp        1      0 127.0.0.1:8888          127.0.0.1:36980         CLOSE_WAIT  -               
tcp        0      0 172.28.219.59:57562     151.101.60.133:443      ESTABLISHED 6786/firefox    
tcp      404      0 127.0.0.1:8888          127.0.0.1:36974         CLOSE_WAIT  -               
tcp6       0      0 :::80                   :::*                    LISTEN      -             

• using REST API
• real-time update or refresh button?

Bug re-introduced with web version of the GUI
See issue 6 in armadito/armadito-av (armadito/armadito-av#6)

After a scan is started, you can switch between tabs but tabs are not updated immediately. For example, while coming back on scan tab while Armadito is scanning a really big file shows 0/0/0 on scanned/found/suspect numbers until the current file is scanned. Also the last threat found text is removed even if the found count is right after such a switch.

I expect at least to see the same stuffs I had before the tab switch. I guess the last known tab state should be saved between switchs.

https://www.owasp.org/index.php/XSS_%28Cross_Site_Scripting%29_Prevention_Cheat_Sheet

• put in autostart a .desktop file that just launches the systray
• put in /usr/share/application another .desktop file that opens main window

Windows client 0.10.0 installed on windows 7:

• wanting to see notification icon all the time: looks to change state using standard icon tray feature and it appears to be named nwjs

I'm trying to get this up and running as a POC.

I've installed the software on the latest version of Ubuntu following the Compile on linux docs.

I'm getting the httpd daemon started, and when I got to localhost:8888/app/index.html, I see all the GET requests in the debug console window, but when it is done loading, all I get is a white page. No content whatsoever.

I've tried it in Firefox that ships with Ubuntu as well as Chrome 56 from .deb. Both yield the same results. I can see all the code in Developer Tools, and everything looks like I should be seeing stuff....but I just have a white screen. Have I missed something? Is something broken?

I used git clone https://github.com/armadito/armadito-web-ui.git -b DEV as the branch to clone from, as per the docs.

tcp 0 0 127.0.0.1:8888 127.0.0.1:47282 TIME_WAIT -
tcp 0 0 127.0.0.1:8888 127.0.0.1:47462 TIME_WAIT -
tcp 0 0 127.0.0.1:8888 127.0.0.1:47578 TIME_WAIT -
tcp 0 0 127.0.0.1:8888 127.0.0.1:47640 TIME_WAIT -
tcp 0 0 127.0.0.1:8888 127.0.0.1:47428 TIME_WAIT -
tcp 0 0 127.0.0.1:8888 127.0.0.1:47686 TIME_WAIT -
tcp 0 0 127.0.0.1:8888 127.0.0.1:47372 TIME_WAIT -
tcp 0 0 127.0.0.1:8888 127.0.0.1:47432 TIME_WAIT -
tcp 0 0 127.0.0.1:8888 127.0.0.1:47242 TIME_WAIT -
tcp 0 0 127.0.0.1:8888 127.0.0.1:47606 TIME_WAIT -
tcp 0 0 127.0.0.1:8888 127.0.0.1:47554 TIME_WAIT -
tcp 0 0 127.0.0.1:8888 127.0.0.1:47560 TIME_WAIT -
tcp 0 0 127.0.0.1:8888 127.0.0.1:47410 TIME_WAIT -
tcp 0 0 127.0.0.1:8888 127.0.0.1:47716 TIME_WAIT -
tcp 0 0 127.0.0.1:8888 127.0.0.1:47628 TIME_WAIT -
tcp 0 0 127.0.0.1:8888 127.0.0.1:47642 TIME_WAIT -
tcp 0 0 127.0.0.1:8888 127.0.0.1:47436 TIME_WAIT -
tcp 0 0 127.0.0.1:8888 127.0.0.1:47342 TIME_WAIT -
tcp 0 0 127.0.0.1:8888 127.0.0.1:47518 TIME_WAIT -
tcp 0 0 127.0.0.1:8888 127.0.0.1:47664 TIME_WAIT -
tcp 0 0 127.0.0.1:8888 127.0.0.1:47358 TIME_WAIT -
tcp 0 0 127.0.0.1:8888 127.0.0.1:47304 TIME_WAIT -
...

Why?

• NW.js is a too young technology
• To reduce memory footprint drastically
• To be able to provide better packaging on Linux and Windows.

Furthermore,

• Armadito AV will provide a same REST API for web ui and for Armadito Agent.

• Multiple events
• Scrollbar in scan tab
• Factory for persistent scan data (#10)
• others

https://www.binpress.com/tutorial/speeding-up-angular-js-with-simple-optimizations/135

• update list from AV

Why?

Because CSS need to be easier to maintain during dev phase at least, read the following to learn about pro/cons :
http://stackoverflow.com/questions/2336302/single-huge-css-file-vs-multiple-smaller-specific-css-files

• using JRPC + REST API

https://launchpadlibrarian.net/303973291/buildlog_ubuntu-xenial-amd64.armadito-web-ui_0.12.8.1-0ubuntu1-283~ubuntu16.04.1_BUILDING.txt.gz

make[1]: Entering directory '/<>'
installing bower & other stuff
npm ERR! Linux 4.4.0-59-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "--no-color" "--no-spin" "--production" "bower"
npm ERR! node v4.2.6
npm ERR! npm v3.5.2
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR! syscall getaddrinfo

npm ERR! network getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'

• application has a desktop notification area icon (aka systray)
• icon has a menu
• icon shows important notifications
• application uses the REST API

Update all dependencies librairies and deprecated librairies

npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: lodash@<3.0.0 is no longer maintained. Upgrade to lodash@^4.0.0.
npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
loadDep:punycode → 200    ▀ ╢██████████████████████████████████████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╟
npm WARN deprecated [email protected]: this package has been reintegrated into npm and is now out of date with respect to npm
npm WARN prefer global [email protected] should be installed with -g

• to be discussed? should it be in user interface?

structure of JSON objects have changed since introduction of JSON-RPC

Web UI javascript code must be updated w.r.t these changes

• remove now deprecated code in services/antivirus-*.js
• use REST API as demonstrated in small example https://github.com/armadito/armadito-av/blob/exp/microhttpd/core/tests/web/index.html

the look of the web GUI must be updated w.r.t. the fact that it now runs inside a browser tab with no control on window size