I created a self-signed certificate and a client certificate using this tutorial and the makecert.exe tool:
http://msdn.microsoft.com/en-us/library/ff647171.aspx
However, when I go to MMC and try to import the certificate in the Trusted Root Certificate Authorities, I have no clue where to locate the .cer file.
Where does the makecert.exe tool save the certificates it creates?
If you did what I did and just left the command prompt in c:\windows\system32 (using the x64 Cross Tools Command Prompt) you will be surprised that the file is not in c:\windows\system32 (as evidenced by doing a simple dir *.cer).
Fortunately it will be found sitting in c:\windows\SysWOW64.
Step 1, point 1
Open a Visual Studio command prompt and browse to the location where
you want to save the certificate files
Is it therefore not the location you went to, upon opening the Visual Studio command prompt?
Related
I had created a Google compute engine (virtual machine) instance with RStudio Server being unaware that RStudio Server is a licensed software. Now, my trial license for RStudio has expired, and I cannot login to my R sessions anymore.
However, I had written some code which I need to recover. How do I download the files?
I have SSH-ed into my virtual machine but cannot find the relevant files or a way to download them.
I had a similar issue and I was able to recover the files by performing the following steps:
SSH to the virtual machine
Once you are in the virtual machine run the following command: cd ../rstudio-user/
Now ls there you will see the file structure you used to see in the RStudio Server interface}
Navigate using cd and ls between the folders to get to the desired file
Once you are in the desired location (where with an ls you can see the files you want to recover) run the following command: pwd
Click on the Engine and go to download file
Enter the full path of the file you want to download, it will be something like: /home/rstudio-user/FILENAME.R
Click on Download
You can do this for each of the files you want to recover.
In case you want to recover a full folder its easier to compress to a zip file and then to download it.
I'm an undergraduate research assistant working on a Linux server without root privilege. I'm trying to install the Rstudio server but the Rstudio website only provides the installation method for sudoers. Is it possible to install it without root access? I'm asking because I'm really not sure if I could get access from the manager. Any help will be appreciated!
No, you can't install it without root access. But there are a couple of things you could do to piece together a solution. Here are two options:
Extract the server and run it directly
You have to be root to install packages, so you can't install the .deb/.rpm file yourself. However, you could extract the contents of the file to a directory inside your home directory and run RStudio Server from there, by executing the rserver program in a regular shell.
Note that this will probably require an afternoon of editing the rserver.conf file to tell it where to find the rest of the files in the installation (since it presumes they are installed in /usr/lib by default). You can get some inspiration for how to do this here: https://github.com/rstudio/rstudio/blob/master/src/cpp/conf/rserver-dev.conf
Run the desktop version and forward the graphics
The other route is to run RStudio Desktop on the server; we make several builds of RStudio Desktop that are installer-less and can just be unpacked into your home directory. Then run an X11 server on your own computer and an X11 client on the RStudio server, so that the RStudio Desktop instance appears on your computer instead of the server.
Yes, you can run rserver without root priveliges.
For RStudio 1.4 I patched the following line into src/cpp/core/LogOptions.cpp
const FilePath kDefaultLogPath = core::system::xdg::userDataDir().completePath("log");
Then you need to set the system environment variables to some location read-writeable for the user, like
RSTUDIO_CONFIG_DIR=$HOME/.config/rstudio
RSTUDIO_CONFIG_HOME=$HOME/.config/rstudio
RSTUDIO_DATA_HOME=$HOME/.local/share/rstudio
And start rserver with the option
--server-data-dir={directory writeable for user}
--server-pid-file={file-path creatable for user}
--database-config-file={config-file}
With these adjustments it runs for me when I start it as a simple user (no root privileges) with
rserver --auth-none=1 --www-frame-origin=same --www-port={port} --www-verify-user-agent=0 --server-data-dir={my-tmp-path} --server-pid-file={my-tmp-path}/rstudio.pid --database-config-file={my-tmp-path}/db.conf}
ATTENTION:
But be aware, that anyone who can reach your system and the specified port from the network has access to the running RStudio in his browser and therefore can run any command in the name of the user on your system now.
Atom Package install issue.png
Hello,
I am using Atom to develop nodejs code for the very first time, problem with accessing the packages tab of the settings. Whenever I search for something, I get this error come up:
self signed certificate in certificate chain
I have tried uninstalling Atom and reinstalling it, and the same problem comes up.
Is this an Atom problem, or more likely something to do with my machine, and if so, what?
Am using win10 and my atom version is Atom 1.33.0x64
Any help would be most appreciated, since I don't seem to be able to add extensions any more.
Many thanks,
Sathiya
From the Atom FAQ:
I’m getting an error about a “self-signed certificate”. What do I do?
This means that there is a proxy between you and our servers where someone (typically your employer) has installed a “self-signed” security certificate in the proxy. A self-signed certificate is one that isn’t trusted by anyone but the person who created the certificate. Most security certificates are backed by known, trusted and certified companies. So Atom is warning you that your connection to our servers can be snooped and even hacked by whoever created the self-signed certificate. Since it is self-signed, Atom has no way of knowing who that is.
If you decide that unsecured connections to our servers is acceptable to you, you can use the following instructions.
apm config set strict-ssl false
https://www.juev.org/2018/07/27/atom-ssl/
Because of a poor software architecture decision early in the NPM project, there is an env var that that will reject self-signed certificates, even if you have strict-ssl set to none. The solution is to set NODE_TLS_REJECT_UNAUTHORIZED=0 in your init.coffee (you can test it by running NODE_TLS_REJECT_UNAUTHORIZED=0 atom . and then trying to install a package.
# $EDITOR $ATOM_HOME/init.coffee or ~/.atom/init.coffee
# Disable TLS Verification.
process.env.NODE_TLS_REJECT_UNAUTHORIZED = 0
Below instructions useful you are behind corporate proxy and
using Atom zip download.
If you are on windows, Locate you apm.cmd file.
mostly at -> cd 'C:\Atom\atom-x64-windows\Atom x64\resources\app\apm\bin\'
Execute below command at your windows power shell:
.\apm.cmd config set strict-ssl false
After this in your Atom,
File -> Settings -> init.coffee
ssl=false
process.env.NODE_TLS_REJECT_UNAUTHORIZED = 0
proxy = "http://your.proxy:8080"
Restart your Atom, at try to install
File -> Settings -> Install -> (for eg. minimap)
Restart your Atom.exe
I also had same issue in Window 10 with atom IDE .
Reason is the proxy server which was blocking the connection to install the packages I was looking for .
So to address this I downloaded the package using apm command from the command line instance .
I was looking for go-plus package so used command as apm install go-plus
On Mac, just setting strict-ssl to false might not work.
You may have to set proxy for this.
apm config set proxy http://*****.****.***:<<port>>
apm config set https_proxy http://****.****.****:<<port>>
If you can get a copy of the self-signed certificate, you may point NODE_EXTRA_CA_CERTS to the self-signed certificate, instead of apm config set strict-ssl false. Here are the steps:
Export the self-signed root CA certificate in PEM format (or Base-64 Encoded X.509 (.CER) on Windows). Sorry, I cannot upload images to illustrate the process. But you may easily find some references by searching "export certificate pem chrome".
Set environment varialble NODE_EXTRA_CA_CERTS:
# Windows
set NODE_EXTRA_CA_CERTS=<absolute-path-to-the-self-signed-root-ca>
# Linux
export NODE_EXTRA_CA_CERTS=<absolute-path-to-the-self-signed-root-ca>
Install the desired Atom plugin:
apm install <plugin-name>
I need to copy a file from a windows share directory to AIX box.
I am not able to get into windows share directory when i have connected to AIX box.
Can someone please help as which unix commands to use to use to login into windows share directory so that i can copy the file and paste to AIX box
You can copy by using nfsshare. Open nfsshare in windows and mount it in aix.
smbclient (if installed):
$ smbclient //host/share
Enter password
smb: \> help
I have a cygwin console running on my windows box, and vim installed and working fine. But when I do an rloging to a server (rlogin server.at.com running unix) my vim command is launching the vi on my remote box. Is there a way to tell cygwin to "tunnel" the text file that I try to open in the rlogin session to a local vim session just as it does with a local file (applies also to my nedit which I dont have in the remote machine but I do in the local one)?
Thanks!
I'm not sure how or if it would work with rlogin but bcvi is SSH-based and allows you to do $ vim filename on the server and open a GVim window on your local machine.
You can also use Vim's default plugin netrw which lets you manage and edit remote files using, among other protocols, rcp:
" manage files
:e rcp://[username#]machinename/path/to/directory/
" edit file
:e rcp://[username#]machinename/path/to/directory/filename
But… is there a reason for using rlogin instead of ssh?