@Rudy-Trujillo That's interesting. I wonder what needs to be done to allow the Omega to access Gmail on secure mode. Seems that if the desktop clients can do it a script should be able to do it as well.
Hi @Rudy-Trujillo, Here's a quick run down of what you need to do. I will update this into the Wiki tomorrow:
Open up the terminal on your computer, and navigate to .ssh
Turn on your ssh-agent, which is a daemon that manages your ssh keys:
eval `ssh-agent -s`
Generate the Private/Public key pair
ssh-keygen -t rsa -C "firstname.lastname@example.org"
Now just follow the wizard, and it will generate a key for you. If you left everything at the default value, your private key will be saved at id_rsa, and your public key will be saved at id_rsa.pub.
Then, you will be adding your key to your system, so that your computer will know which key to login to servers/omega with:
Finally, you just need to copy the content of your id_rsa.pub and place it on a new line in the authorized_keys file on the remote computer you want to log into. The location of this file is usually in the user's ~/.ssh folder. If you are using this to log into the Omega, the file should be under /etc/dropbear. Note, if you are unable to find this file in the folders mentioned, you simply need to create it.
Hi @ben-petermeier, I apologize for the late response. Unfortunately, we ran into some delays with the App Store, and it will be coming out of private beta in Early March. The reason why it was delayed was because we have been focusing a lot of our development efforts on the Onion Cloud, which will be released this week. There are still a few bugs that still need to be addressed, and we will focus on that once the Cloud is launched.
Thank you very much for your patience, and I look forward to showing it off when it becomes available!
Hi @Rudy-Trujillo, since the Omega can serve an AP and be on a network simultaneously, it might be more secure to do the setup on the AP instead of temporarily enable the intranet connection. The specific workflow still needs to be fine-tuned, but I think generally speaking, keeping IoT devices in an isolated network is probably the best practice.
Cool and I saw those changes in the last update :) Also pleased to say I tested a USB audio device and it works reasonably well. I say reasonably because when playing straight wavs at high bitrate it can stumble andstutter a bit but not all the time. Restart the stream an it will work. Sounds like an USB IRQ /Buffer issue to me. However as madplay works perfectly playing mp3s with no errors and wavs take up so much space who cares?
Really nice Calculator app though. In fact I am loving all the apps so far. Any idea when the App store will go live? Looking forward to seeing what will appear.
Lastly, if I simply wanted to go back to the state of a factory new Open WRT installation and start again, how would I go about that? I ask because I have five new Omegas and intend to brick at least some of them :-)
I think the problem is that apache is running as nobody and the relay-exp is only accessible from root.
Changing apache to run as root is not possible without rebuild...
... Apache has not been designed to serve pages whil running as root. There are known race conditions that will allow any local user to read any file on the system. If you still desire to serve pages as root then add -DBIG_SECURITY_HOLE to the CFLAGS env variable and then rebuild the server.
Is there a solution?
Disabled Categories are greyed out
This topic will be moved to the category
Looks like your connection to Community was lost, please wait while we try to reconnect.