-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues while installing TinyCheck on a fresh Ubuntu 20.04. live usb #146
Comments
I managed to get up until connecting to the ephemeral network. When it gets created my internet connection disappears and my WIFI icon turns green. When I scan the QR code after some time my computer gets back online, the connected phone stays offline. One time the program even started the analysis, but then the phone went offline. I think the problem is that the program is reading my inbuilt router s the wireless interface and my usb adapter as the internet interface and it may need to be the other way around, because the inbuilt router doesn't support AP, while as it turns out it does support master mode. @EvgenyAblesov, you have been active here recently, so if I may ask, perhaps you know how to change the devices? Or what the issue might be here? (Backend doesn't allow me to choose anything else for the WiFi interface than my inbuilt router). |
Hi!
I have read all your messages and that's what I have to say about it.
Unfortunately, you are not using TinyCheck in the way that it was designed and designed for.
TinyCheck never had Ubuntu compatibility in general and designed to run only on Raspbian 32bit.
So, is a huge job that you have already done!
And I really can't help you just because I don't have the same equipment as you do.
Also my network settings will be significantly different from yours.
However, here's what I'll do in this weekend. I will install Ubuntu on a virtual machine and connect Wi-Fi router to it. Please notice, that my model of Wi-Fi router can be significally differs from yours. But this one is the only one that I have available. I will also set up the network as it is customary in my region and fits to my provider requrements.
Then I will try to solve all the compatibility problems and make a list of such problem-solutions for you. Maybe, somehow some points from this list will suit you. If I find any common solutions between Ubuntu and Raspbian, I will make a new pull request on GitHub and mention it in my next reply to you.
I plan to do this this weekend, is it ok to get an answer next week for you?
Will you be satisfied with the lack of a solution in the end?
Спасибо!
Office: +7 495 797 87 00 x1659 | Mobile: +7 926 245 11 20 | ***@***.******@***.***>
39A/3, Leningradskoe Shosse, Moscow, 125212, Russia | www.kaspersky.com<http://www.kaspersky.com>
blog.kaspersky.com<http://blog.kaspersky.com/> | business.kaspersky.com<http://business.kaspersky.com/> | securelist.com<http://securelist.com/> | threatpost.com<http://www.threatpost.com/>
From: reetuh797 ***@***.***>
Sent: Friday, December 15, 2023 9:44 AM
To: KasperskyLab/TinyCheck ***@***.***>
Cc: Evgeny Ablesov ***@***.***>; Mention ***@***.***>
Subject: Re: [KasperskyLab/TinyCheck] Issues while installing TinyCheck on a fresh Ubuntu 20.04. live usb (Issue #146)
Caution: This is an external email. Be cautious while opening links or attachments.
I managed to get up until connecting to the ephemeral network. When it gets created my internet connection disappears and my WIFI icon turns green. When I scan the QR code after some time my computer gets back online, the connected phone stays offline. One time the program even started the analysis, but then the phone went offline.
I think the problem is that the program is reading my inbuilt router s the wireless interface and my usb adapter as the internet interface and it may need to be the other way around, because the inbuilt router doesn't support AP, while as it turns out it does support master mode.
@EvgenyAblesov<https://github.com/EvgenyAblesov>, you have been active here recently, so if I may ask, perhaps you know how to change the devices? Or what the issue might be here? (Backend doesn't allow me to choose anything else for the WiFi interface than my inbuilt router).
Sorry to be bothersome. I really need help.
—
Reply to this email directly, view it on GitHub<#146 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A74S57W6BDL3GFBWVJJMJMLYJPWR3AVCNFSM6AAAAABAOOXSXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGM3DANRQGU>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
@EvgenyAblesov It is only thanks to the answers here and in the ubuntu community, I only had to struggle through pasting the code and hoping for the best. Best regards, |
Hello,
I have a couple of issues. Please help. If you can answer in detail, that would be helpful, as I'am not experienced with terminal or IT in general.
I'm using:
a mobile hotspot,
a laptop PC with an inbuilt router, that doesn't support AP mode,
and a TPLink N 300 adapter, which does support Soft-AP as the main source of internet.
Context:
After finally managing to install TinyCheck, I couldn't connect nor to the frontend nor to the backend. I tried to reinstall - I uninstalled TinyCheck, found this answer and installed by myself nodejs, and then tried reinstalling TinyCheck hoping to find instructions and follow the aforementioned advice, but now I see that a the moment the installation is building in the right directories ... I hadn't checked that before, so installing nodejs beforehand wasn't necessary as I understand now.
Anyways, I now get the following two issues A and B:
A. Deprecation warnings, before the installation proceeds. I don't remember, if I had them pop up the last time, maybe not, because nodejs was being installed properly as a part of the TinyCheck installation process.
The Warnings:
1)
"```
DEPRECATION WARNING
Node.js 14.x is no longer actively supported!You will not receive security or critical stability updates for this version.You should migrate to a supported version of Node.js as soon as possible.Use the installation script that corresponds to the version of Node.js youwish to install. e.g.* https://deb.nodesource.com/setup_16.x — Node.js 16 "Gallium"* https://deb.nodesource.com/setup_18.x — Node.js 18 LTS "Hydrogen" (recommended)* https://deb.nodesource.com/setup_19.x — Node.js 19 "Nineteen"* https://deb.nodesource.com/setup_20.x — Node.js 20 "Iron" (current)Please see https://github.com/nodejs/Release for details about whichversion may be appropriate for you.The NodeSource Node.js distributions repository containsinformation both about supported versions of Node.js and supported Linuxdistributions. To learn more about usage, see the repository:https://github.com/nodesource/distributions
"
[...]
The same npm warnings are displayed while building the frontend.
Here, I also think that the outdated npm is due to me installing nodejs by myself, so that's on me, but I suspect that the connection problem might e related to the issues detected during npm audit. Might that be true?
(Sorry if I'm writing non-sense).
Current state:
Otherwise all of the boxes were checked green during the installation. And the system reboots.
I will update.
UPDATE:
http://tinycheck.local and https://tinycheck.local as well as IP are still unable to connect. (The last time I had at least goten to entering my username and password for the backend...)
Tried updating, got:
Tried stpping/starting frontend, got:
Tried stopping/starting backend, got notifications about conflict of flask dependencies.
Had to reinstall in the following order:
Then the backend connected, it offered it's own IP address, not the ones mentioned in the wiki, but based on my hotspot's device's IP.
Then I stopped/started the frontend in a second terminal, it gave out an error message, but also offered a server IP and connected.
Error:
`/bin/sh: 1: nft: not found
/bin/sh: 1: nft: not found
/bin/sh: 1: nft: not found
/bin/sh: 1: nft: not found
/bin/sh: 1: nft: not found
WARNING: This is a development server. Do not use it in a production deployment.
Use a production WSGI server instead.
`
The text was updated successfully, but these errors were encountered: