Notes: ssh- servers and clients.

Notes: ssh- servers and clients.


This post is tagged with notes, such posts will be documentations of stuff that I learned or think that can be saved as notes. Also, they can be shared and is open for comments/opinions.
Concept inspiration: one of my seniors sayan.

I remember the uncertainty of concepts I had when I initially started working with the interactions between local machines and remote machines.
I figured out am not alone, so I thought documenting the same would be a good idea, err… maybe.

A step-to-step guide of the commands can be easily found. So, if you are here, you ain’t sure about the concepts or how ssh works.
One such guide that I liked.  Come back here after you have read the guide. 😉

It becomes tedious when someone is experimenting with remote machines, VMs, etc, and has to login to his machines with a password every time.

SSH login?

After having created the public and private ssh-keys using ssh-keygen, using ssh-copy-id one can copy the public key to remote-host.


It copies the public key to the remote-host(server).

remote-host? remote-machine? server? client?

client-machine: client machine can be your local machine and has openssh-clients package already installed (well, most of the times).

server-machine:  server machines can be the Virtual machines that you created on your local machine or the remote hosts. Server machines need to have openssh-server( sshd) package installed and enabled(active/running state).
Some distros do not have it by default.

check the status of the sshd service:
$ systemctl status sshd

enable the service:
$ systemctl enable sshd

start the service:
$ systemctl start sshd

Cooked this up: A pictorial explanation.

There is another situation when the same machine acts as both a client and the server, as obvious it may sound, ssh service needs to be running on the client as well.

that’s all fellas! Thanks for reading.

Fedora-Hubs : Getting Started

Fedora-Hubs : Getting Started

The definition for fedora-hubs has changed over the months !
Hubs has come a long way from when it was initially started. From new milestones, to new goals, new road-maps.


There have been new contributors willing to contribute to hubs, but facing issues while setting it up locally. Thus an initiative to help out new contributors hack their way into the project. Few common terms and words, not so common to the non-hubs world 😛

To begin with: We have taken efforts in keeping the README file updated. You might want to keep looking back to this file while setting it up locally.
Below, I have explained a tiny bit more in detail about a few things that might be confusing or where one can face issues, also how these files happen to be inter-related.
After having installed all the dependencies and cloned the project, you need to configure the project to authenticate against Ipsilon, fedora’s multi-protocol Identity Provider service.

oidc-register --debug http://localhost:5000

If one faces an error regarding verification of certificate, the following command will replace httplib2’s ca cert file, else you’ll be thrown back since you don’t have the http setting.

cp /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem ~/.virtualenvs/hubs/lib/python2.7/site-packages/httplib2/cacerts.txt

You also might want to keep clearing/refreshing your cookies. After having created the local configuration file as mentioned in the README, one needs to create the database.
Further which one can finish running the app by starting the devel server with their local config file.

Few not-so-common terminologies:
Hub: A hub can be associated with a page displaying the info that concerns the hub.
Widget: The various sized rectangular cards on a hub-page are termed as widgets.
One can find the various widgets under the widgets/ dir in the source-code.
Every widget has a respective html file under the widgets/templates dir.
User-Hub page: The hub page of a fas (fedora account system) user that lists down the                                          widgets he/she has configured and wishes to display on his/her page.
While hacking on the project, you might want to navigate to localhost:5000/ to view the widget on a user-hub page.
Group-Hub page: The hub page of the various teams such as Infrastructure, Design-team,                                    Commops, Marketing, i18n.
Similarly, while hacking on a widgets relevant to groups, you need to navigate to localhost:5000/ to view the respective widget on the group-hub page.

Again, when hacking on a new widget, according to the hub page you wish to display, one might want to add it either to the hubs/ file or to the file. One can look into it under the “Stubbing out a new widget” section of the README file.

You might see something similar to this on your localhost :

Screenshot from 2015-12-08 19-23-41

So, this is a group-hub page, Group:Infrastructure here, listing down the widgets with respect to the infrastructure group. Widgets are listed in the same order as added with their index values, in the file under the Infrastructure team.

This is a user-hub page:

Screenshot from 2016-03-17 03-28-52

fas_username: devyani7, listing down the widgets configured in the hubs/ file. Here, this user-hub page can be configured as the user wishes his/her page to appear to the visitors.

One channel where you can drop/lurk for further queries: #fedora-hubs on freenode.
We have weekly-meetings every Tuesday at 14:00 UTC 🙂
We also have a mailing-list:

Who am I ?!

Who am I ?!

Finally, a warm hello to the world of blogging !! Ya, i would accept, was lazy enough to not start blogging earlier ! Anyways, am here now, thought of finally executing the first thing on my new-year resolutions list.

Will begin with a short introduction :

Myself, Devyani 🙂 I love the internet, reading books and contributing to open source software. Girl-geek, in her pre-final year, pursuing B-Tech in CSE(Computer Science and engineering) in Durgapur, spending most of her time coding in Python and C, and contributing to upstream open-source projects.

Uploads her code on Github, listens to music on spotify, tweets on Twitter,
and chats on google+.

When ain’t coding, you can find me playing guitar, or eating lots of food !!

This blog mainly will constitute my endeavours and my journey into open-source and about the projects i’d be working on. 🙂

So, stay tuned for more crazy & interesting blog-posts !! Happy hacking 😉