Skip to content
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

ssh keys are not working in this image #9

Open
nicopace opened this issue Aug 1, 2017 · 8 comments
Open

ssh keys are not working in this image #9

nicopace opened this issue Aug 1, 2017 · 8 comments

Comments

@nicopace
Copy link
Member

nicopace commented Aug 1, 2017

https://github.com/libremesh/network-profiles/tree/master/wunderkammer/common
@panosnethood created a lime_zero image like this:
./cooker -c ar71xx/generic -p tl-mr3020-v1 --flavor=lime_zero --community=wunderkammer/common

Neither him or me can access the image through ssh

@p4u
Copy link
Member

p4u commented Aug 1, 2017

-p option does not exist, what you want is --profile=tl-mr3020-v1 I supose

@p4u
Copy link
Member

p4u commented Aug 1, 2017

Also, your profile includes a file of 297kb (https://github.com/libremesh/network-profiles/blob/master/wunderkammer/common/usr/bin/sha1sum). That cannot fit inside a 4MB router, it is just impossible (only less than 100kb are available for user configuration files and jffs2 filesystem).

@p4u
Copy link
Member

p4u commented Aug 1, 2017

About the SSH problem, I supose there is some issue with the authorized_keys included in your profile, not sure what is wrong.

@nicopace
Copy link
Member Author

nicopace commented Aug 1, 2017

oh, thanks pau... haven't seen that file there (just copied it form quintanalibre i guess... ).
the -p/-c was a typo from me.
I'm checking the authorized_keys issue.

@nicopace
Copy link
Member Author

nicopace commented Aug 1, 2017

The situation with SSH is the following:
When I use the libremesh build without any network profile, as my ssh key is part of the default keys, I can access the router.
When I create an image using the network profile of wunderkammer, it doesn't work.
the authorized_keys of that network profile is similar in nature as the one used in quintanalibre: same permissions, same name, same newline at the end of the file. Only difference, the keys included.
Now we got to add a script added by @openspacex in his network profile: https://github.com/libremesh/network-profiles/blob/master/openNET.io/1144-W2PA-LIME-XXXX/etc/uci-defaults/95_add-sshkeys
It still doesn't work.

any idea?

@nicopace
Copy link
Member Author

nicopace commented Aug 1, 2017

The script did't worked...
I tried with an empty community, and it works (but it messes up everything for some reason).
I will do more tests.
This also happened with the wdr-4300-v1.
Will do a clean setup and check again... it is a little odd.

@aparcar
Copy link
Member

aparcar commented Mar 20, 2018

Why don't you directly include the ssh keys and use this script?

.
└── etc
    ├── config
    │   ├── dropbear
    │   └── lime-defaults
    └── dropbear
        └── authorized_keys

@aparcar
Copy link
Member

aparcar commented Dec 11, 2018

@nicopace is this issue still a thing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants