alex.mamchenkov.net Report : Visit Site

Technical data of the alex.mamchenkov.net

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host alex.mamchenkov.net. Currently, hosted in United States and its service provider is E.I. du Pont de Nemours and Co. Inc. .

the related websites

alexcartoon.com alexbmodel.co.uk thequiltshow.com marinayoga.com alexbuckinghammotorcycles.com danz.co.uk cartridgesave.co.uk alexnolan.net alexscottcarsguidepost.co.uk dvdstyler.org 

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called nginx/1.10.2 containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

skip to content … mammoth cave … graph database in one of the side projects i am involved into in my free time that helps me learn a bunch of things that are not really in my normal workflow, i faced a problem of working with some big sets of data (millions of rows per table, multiple tables, bunch of relations). trying old ways of improving performance like tuning db engines (mysql, mariadb), optimising code to use low-level queries, multi-row inserts, tweaks on data models, etc, didn’t give the desired results, so i went out googling and discovered graph databases . not something new in general as graph theory is well known, but the use case is pretty interesting. not that i am already deep into it, but feels like i will spend some time looking into the technology. first i got a hint on neo4j somewhere in stackoverflow, but didn’t like something about it and went on further googling of the subj. ended up at top 15 free graph databases i first stopped on orientdb , installed it for the test and played around and while it looks very promising, i have couple of issues with it: java: it is a personal issue of me not being in love with java at all. installing jdk on the server to run db is something i would do only in case it is absolutely required for my complete happiness. not that i had any issue during testing, i still don’t trust it somehow internally poor documentation: you can see pretty extensive documentation on their web-site, but it is a bit hard to navigate and find things around and when you seek google help for what you need, you mostly end-up on 404, so either old version links are in google and are not on the site or something else weird is going on. driver interfaces (outside of java world) are bad documented or/and bad implemented, at least for php. both, official phporient and doctrine odm show only small snippets of usage with no clear overview of what is possible (apart from basic things) while there are cons above, there are obviously some pros, like almost native sql, easy install (even involving java), nice tool-set, etc. after reviewing the list of 15 databases, the second choice was arangodb , which is: written in c++ has very good and solid documentation with lots of examples (even comparisons for people who came from traditional sql background) has lots of pre-build packages for different operating systems and yum repo for redhat followers convincing benchmark comparison of different db engines and scenarios (not gonna state about truth, as benchmarks are always tricky, but who doesn’t like graphs?) still need to put my hands on, but i think this is some nice journey. if you are in the topic, please leave your thoughts and ideas in the comments or send me them via any other possible path of communication to save time and effort :-) author alexander mamchenkov posted on february 14, 2018 categories databases , technology leave a comment on graph database ssh via bastion host with forwardagent while it is pretty common to have an infrastructure behind load-balancers and bastion hosts, there are still many confusion around actual configuration of the ssh client for fast and convenient use of the setup. while i am not going to talk about actual advantages of bastion hosts, i will put here some clarifications on the ssh client setup. assuming you you a bastion.host that you user as a connection gateway to your private.host and you want to work with your default ssh key that is only on your local pc/laptop, you have two possible way. the one and the most commonly used is with ssh agent forwarding, meaning you have to run ssh-agent on you laptop, add the ssh keys to it via ssh-add command (or use ssh-add -l to list all keys in the agent) and then user forwardagent yes in ~/.ssh/config , something like this: host bastion.host user ssh_user hostname bastion.host proxycommand none identityfile ~/.ssh/id_rsa passwordauthentication no forwardagent yes host private.host user ssh_user proxycommand ssh -q -a bastion.host -w %h:%p identityfile ~/.ssh/id_rsa forwardagent yes and while this is all cool from one point of view, this method has few drawbacks: running forwardagent is not a good idea in terms of security, and you can read more about it here . running forwardagent requires you to actually configure and run ssh-agent on you local pc/laptop, which is not a big deal at all, but you will have to remember and check it all the time or you will have all kind of authentication errors and will spend sometime to find out the reason for them (not running/misconfigured agent the second method to achieve the same functionality in terms of bastion host and avoid messing around ssh-agent is to use ssh proxycommand . in this scenario, when configured properly, ssh will first run the proxycommand to establish the connection to bastion.host and then enable the tunnel via this connection to the private.host . this way bastion.host will know nothing about your keys or anything related to authentication, but will just make a tunnel (similar to ssh port forwarding) and keep it for you until you are done. to get this to work, you would adjust the ~/.ssh/config as follows: host bastion.host user ssh_user identityfile ~/.ssh/id_rsa forwardagent no host private.host user ssh_user proxycommand ssh -w %h:%p -q bastion.host identityfile ~/.ssh/id_rsa forwardagent no so now as you have all in place and configured, you can ssh private.host and enjoy the stay on your secure server. while this is all cool, it has a lot of default things and assumptions behind the scene which you are not bothering to learn until you face a slightly different requirements: assume that you need to have the ssh configuration and per-host keys not in your home .ssh directory, but somewhere else. lets say you have some /very/secure/location with separate ssh.conf (with the content from above) and a bastion.id_rsa and a private.id_rsa to use for the connections. to make them work you would assume that you only need to adjust the identityfile configurations to point to the correct keys and then run your ssh as follows: ssh -f /very/secure/location/ssh.conf private.host bad news – it will not work and will give you authentication error. though you still will be able to access bastion.host with the above, you won’t be able to reach you final destination at private.host . good news – thanks to this lovely discussion at stack overflow , a minor adjustments have to be done in your proxycommand : you need to specify the ssh config file to it as well, so now it will look like: proxycommand ssh -f /very/secure/location/ssh.conf -w %h:%p -q bastion.host obviously the reason is that giving -f to initial ssh command, you instruct it to look for a specific configuration file, but when it will run the proxycommand , that instance of ssh client will have no clue whatsoever about your custom config and will look for default one in ~/.ssh/config and system-wide settings. i’ve spent quite some time before i figured out what’s going on and in order not to do so again and hopefully save some of your time, let this post be here for future references author alexander mamchenkov posted on november 10, 2017 categories ssh , technology leave a comment on ssh via bastion host with forwardagent mount and systemd had a task: double the size of a volume on amazon aws ec2 instance. the process is yet manual and it is roughly as follows: create a new volume on aws with double the size of the the old one attach it to the instance create partition and filesystem on the new volume mount the new volume somewhere next to the old volume mount point rsync data from the old volume to the new volume adjust /etc/fstab to point to the new volume for the corresponding mount point unmount both volumes mount the new volume to the old mount point detach the old volume from instance delete the old volume all pretty simple and strait-forward. but! the new volume is not mounting to the old mount point, while mount command is silent ab

URL analysis for alex.mamchenkov.net

http://alex.mamchenkov.net/2014/11/27/vlc-mosaic-multiple-rstp-streams/

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain Name: MAMCHENKOV.NET
Registrar URL: http://www.godaddy.com
Registrant Name: Leonid Mamchenkov
Registrant Organization:
Name Server: NS-553.AWSDNS-05.NET
Name Server: NS-1383.AWSDNS-44.ORG
Name Server: NS-2020.AWSDNS-60.CO.UK
Name Server: NS-161.AWSDNS-20.COM
DNSSEC: unsigned

For complete domain details go to:
http://who.godaddy.com/whoischeck.aspx?domain=MAMCHENKOV.NET

The data contained in GoDaddy.com, LLC's WhoIs database,
while believed by the company to be reliable, is provided "as is"
with no guarantee or warranties regarding its accuracy. This
information is provided for the sole purpose of assisting you
in obtaining information about domain name registration records.
Any use of this data for any other purpose is expressly forbidden without the prior written
permission of GoDaddy.com, LLC. By submitting an inquiry,
you agree to these terms of usage and limitations of warranty. In particular,
you agree not to use this data to allow, enable, or otherwise make possible,
dissemination or collection of this data, in part or in its entirety, for any
purpose, such as the transmission of unsolicited advertising and
and solicitations of any kind, including spam. You further agree
not to use this data to enable high volume, automated or robotic electronic
processes designed to collect or compile this data for any purpose,
including mining this data for your own personal or commercial purposes.

Please note: the registrant of the domain name is specified
in the "registrant" section. In most cases, GoDaddy.com, LLC
is not the registrant of domain names listed in this database.

  REGISTRAR GODADDY.COM, LLC

  REFERRER http://www.godaddy.com

SERVERS

  SERVER net.whois-servers.net

  ARGS domain =mamchenkov.net

  PORT 43

  SERVER whois.godaddy.com

  ARGS mamchenkov.net

  PORT 43

  TYPE domain

DOMAIN

  NAME mamchenkov.net

NSERVER

  NS-1383.AWSDNS-44.ORG 205.251.197.103

  NS-161.AWSDNS-20.COM 205.251.192.161

  NS-2020.AWSDNS-60.CO.UK 205.251.199.228

  NS-553.AWSDNS-05.NET 205.251.194.41

STATUS
clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
clientRenewProhibited https://icann.org/epp#clientRenewProhibited
clientTransferProhibited https://icann.org/epp#clientTransferProhibited
clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited

  CHANGED 2017-04-09

  CREATED 2004-04-14

  EXPIRES 2018-04-14

OWNER

ADMIN

TECH

  REGISTERED yes

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .