access via SSH?
-
- Posts: 16
- Joined: Sun Jun 12, 2016 4:51 pm
Re: access via SSH?
thank you friends, now when webrepl works, I'll use it with some SSH port forwarding for my tinkering...
Re: access via SSH?
Please don't forget to post how-to here on the forum.thank you friends, now when webrepl works, I'll use it with some SSH port forwarding for my tinkering...
Awesome MicroPython list
Pycopy - A better MicroPython https://github.com/pfalcon/micropython
MicroPython standard library for all ports and forks - https://github.com/pfalcon/micropython-lib
More up to date docs - http://pycopy.readthedocs.io/
Pycopy - A better MicroPython https://github.com/pfalcon/micropython
MicroPython standard library for all ports and forks - https://github.com/pfalcon/micropython-lib
More up to date docs - http://pycopy.readthedocs.io/
Re: access via SSH?
To get around this I setup a proxy and (an attempt at) an MQTT bridge on some old Raspberry Pi's. The idea is that internally my IoT's connect to my raspberry MQTT bridge without ssl, the MQTT bridge sync's to my main server (a simple VPS) via SSL instead of directly without SSL. A simpler solution for secure connections are (of course) welcome!pfalcon wrote:These are golden words and exactly mirror outlook of the maintainers (well, mine for sure). SSL/TLS is pretty tricky thing, and even big boxes have problems with it, remember or Heartbleed, or at my dayjob, we had intermittent TLS failures for last 2 months and suspected everything up to hardware failure (somewhere at the cloud provider, as customary nowadays). Turned out it's a software issue reported some 5 years ago and marked as "Wontfix": https://bugs.launchpad.net/ubuntu/+sour ... bug/795355 . So again, if "big iron" has problems with it, just imagine what problems small embedded systems have. We provide basic SSL support which works for basic things. I'm ready to go as far as possible beyond that, up to developing own TLS implementation. But before going that deep (can easily take half a year), we're going to make many useful things to be available which should work pretty well in your local network, protected by WPA.jms wrote:
In fact the same could be said of TLS/SSL and using external cloud services. It's much easier to talk to something on the local network without it.
Jon
NodeMCU v0.9 / V1 / V2 / V3
WeMos D1 Mini
WeMos Lolin32 v1.0.0
WeMos Lolin D32 Pro V2
WeMos D1 Mini
WeMos Lolin32 v1.0.0
WeMos Lolin D32 Pro V2
-
- Posts: 16
- Joined: Sun Jun 12, 2016 4:51 pm
Re: access via SSH?
any idea how to autostart webrepl easy?
Re: access via SSH?
load it in the main.py (or boot.py)
Code: Select all
import webrepl
webrepl.start()
NodeMCU v0.9 / V1 / V2 / V3
WeMos D1 Mini
WeMos Lolin32 v1.0.0
WeMos Lolin D32 Pro V2
WeMos D1 Mini
WeMos Lolin32 v1.0.0
WeMos Lolin D32 Pro V2
-
- Posts: 16
- Joined: Sun Jun 12, 2016 4:51 pm
Re: access via SSH?
what do you use to edit boot.py?
esptool can overwrite it?
tried to do that way but it doesn't autostart...will invetigate it more....
esptool can overwrite it?
tried to do that way but it doesn't autostart...will invetigate it more....
Re: access via SSH?
boot.py may also be placed in the source directory under esp8266/scripts. If it exists there, any changes in the local file system of the esp8266 are ignored. You may change/create it in the sources and rebuild the image.
You can also transfer files to esp8266 with the webrepl_cli tool https://github.com/micropython/webrepl
You can also transfer files to esp8266 with the webrepl_cli tool https://github.com/micropython/webrepl
-
- Posts: 16
- Joined: Sun Jun 12, 2016 4:51 pm
Re: access via SSH?
Thnx for the tip... I have just reactivated (removed #) before webrepl lines in inisetup.py and then recompiled micropython, erase_flash and write_flash... webrepl started
Re: access via SSH?
Sorry to revive an old thread, but it is the most relevant one I could find on the internet.
It is a work in progress, but the source code is available here: https://github.com/LarsH/larssh
The SSH protocol is actually quite lean. I just implemented a working micropython server in ~850 lines of python. It runs fine on a Raspberry Pico W. I have not tested it on an ESP yet, but it should hopefully work there as well.jms wrote: ↑Fri Jun 17, 2016 11:35 amThe SSH protocol is incredibly heavyweight, an order of magnitude more than what you would want to try running on this board.
It would be better to use a VPN to get onto the network then good old telnet.
In fact the same could be said of TLS/SSL and using external cloud services. It's much easier to talk to something on the local network without it.
Jon
It is a work in progress, but the source code is available here: https://github.com/LarsH/larssh