Pure-FTPd

220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
220-You are user number 1 of 5 allowed.
220-Local time is now 19:10. Server port: 21.
220-This is a private system - No anonymous login
220-IPv6 connections are also welcome on this server.
220 You will be disconnected after 15 minutes of inactivity.
530 Login authentication failed
214-The following SITE commands are recognized
 ALIAS
 CHMOD
 IDLE
 UTIME
214 Pure-FTPd - http://pureftpd.org/
211-Extensions supported:
 EPRT
 IDLE
 MDTM
 SIZE
 MFMT
 REST STREAM
 MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;
 MLSD
 AUTH TLS
 PBSZ
 PROT
 UTF8
 TVFS
 ESTA
 PASV
 EPSV
 SPSV
211 End.

OpenSSH8.9p1 Ubuntu 3ubuntu0.10

SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.10
Key type: ecdsa-sha2-nistp256
Key: AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBIm4vnIlbslFy4Xzbkr7J7mR
ovitA7hnIBGtIpzyp2JpqxfZcr3Mh1JqSmELerThqutBAlgy51kgN13INbmTMX8=
Fingerprint: 9b:83:e7:9c:f5:66:ce:cf:b1:f1:cf:d6:16:fa:d3:ed

Kex Algorithms:
	curve25519-sha256
	curve25519-sha256@libssh.org
	ecdh-sha2-nistp256
	ecdh-sha2-nistp384
	ecdh-sha2-nistp521
	sntrup761x25519-sha512@openssh.com
	diffie-hellman-group-exchange-sha256
	diffie-hellman-group16-sha512
	diffie-hellman-group18-sha512
	diffie-hellman-group14-sha256
	kex-strict-s-v00@openssh.com

Server Host Key Algorithms:
	rsa-sha2-512
	rsa-sha2-256
	ecdsa-sha2-nistp256
	ssh-ed25519

Encryption Algorithms:
	chacha20-poly1305@openssh.com
	aes128-ctr
	aes192-ctr
	aes256-ctr
	aes128-gcm@openssh.com
	aes256-gcm@openssh.com

MAC Algorithms:
	umac-64-etm@openssh.com
	umac-128-etm@openssh.com
	hmac-sha2-256-etm@openssh.com
	hmac-sha2-512-etm@openssh.com
	hmac-sha1-etm@openssh.com
	umac-64@openssh.com
	umac-128@openssh.com
	hmac-sha2-256
	hmac-sha2-512
	hmac-sha1

Compression Algorithms:
	none
	zlib@openssh.com

Kong Gateway2.8.1

HTTP/1.1 404 Not Found
Date: Fri, 21 Feb 2025 05:15:46 GMT
Content-Type: application/json; charset=utf-8
Connection: keep-alive
Content-Length: 48
X-Kong-Response-Latency: 1
Server: kong/2.8.1

Kong Gateway2.8.1

HTTP/1.1 404 Not Found
Date: Thu, 20 Feb 2025 08:34:01 GMT
Content-Type: application/json; charset=utf-8
Connection: keep-alive
Content-Length: 48
X-Kong-Response-Latency: 0
Server: kong/2.8.1

Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            12:87:d3:d8:12:59:fa:e3:5a:05:55:d1:7c:43:ad:d3
        Signature Algorithm: ecdsa-with-SHA256
        Issuer: C=US, ST=California, L=San Francisco, O=Kong, OU=IT Department, CN=localhost
        Validity
            Not Before: Jul 25 04:00:23 2022 GMT
            Not After : Jan 19 03:14:08 2038 GMT
        Subject: C=US, ST=California, L=San Francisco, O=Kong, OU=IT Department, CN=localhost
        Subject Public Key Info:
            Public Key Algorithm: id-ecPublicKey
                Public-Key: (256 bit)
                pub:
                    04:fe:12:cc:52:e5:cb:df:a0:19:2f:98:4c:3d:2f:
                    12:80:0f:cc:31:ee:2c:bc:80:45:4a:a8:8f:d3:98:
                    5a:ba:4d:d5:da:10:48:99:09:88:a6:ce:d0:ef:40:
                    cd:e0:0f:1c:f0:d5:00:87:cd:2d:5e:c4:ad:bc:7b:
                    1d:0a:93:77:90
                ASN1 OID: prime256v1
                NIST CURVE: P-256
        X509v3 extensions:
            X509v3 Basic Constraints: critical
                CA:FALSE
            X509v3 Extended Key Usage: 
                TLS Web Server Authentication, TLS Web Client Authentication
            X509v3 Subject Key Identifier: 
                D2:92:09:1B:5C:D0:33:F0:22:B5:47:BE:C5:C4:F0:E4:AA:D9:FF:3F
    Signature Algorithm: ecdsa-with-SHA256
    Signature Value:
        30:44:02:20:55:6e:f1:ac:a1:e8:79:77:5a:1f:f6:4f:a5:4f:
        85:5f:d0:eb:59:3f:07:43:11:0a:4c:e8:0c:82:af:f3:83:ee:
        02:20:1f:36:23:b1:5d:bf:1b:15:b3:6c:78:a6:47:88:a3:e7:
        01:7e:ff:f6:43:12:0a:22:ff:48:0d:ac:56:1e:66:93

HTTP/1.1 200 OK
X-Powered-By: Sails <sailsjs.org>
Content-Type: text/html; charset=utf-8
Content-Length: 6522
ETag: W/"197a-JWWS89uYeXw0FmYwstO+DA"
Vary: Accept-Encoding
Date: Sun, 09 Feb 2025 16:58:10 GMT
Connection: keep-alive

<!DOCTYPE html>
<html id="konga">
<head>
    <title>Konga</title>

    <base href="">

    <!-- Viewport mobile tag for sensible mobile support -->
    <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">

    <!--
        Stylesheets and Preprocessors
        ==============================

        You can always bring in CSS files manually with `<link>` tags, or asynchronously
        using a solution like AMD (RequireJS).  Or, if you like, you can take advantage
        of Sails' conventional asset pipeline (boilerplate Gruntfile).

        By default, stylesheets from your `assets/styles` folder are included
        here automatically (between STYLES and STYLES END). Both CSS (.css) and LESS (.less)
        are supported. In production, your styles will be minified and concatenated into
        a single file.

        To customize any part of the built-in behavior, just edit `tasks/pipeline.js`.
        For example, here are a few things you could do:

            + Change the order of your CSS files
            + Import stylesheets from other directories
            + Use a different or additional preprocessor, like SASS, SCSS or Stylus
    -->

    <!--<link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet">-->

    <!--STYLES-->
    <link rel="stylesheet" href="min/production.min.css?r=0.14.9">
    <!--STYLES END-->
</head>

<body class="body">
<div ng-controller="MainController" data-ng-cloak class="ng-cloak">
    <div data-ui-view="sidenav" ng-if="$state.name.indexOf('auth') < 0 && $state.name.indexOf('error') < 0"></div>
    <div class="main-container-wrapper" ng-class="{'full-width no-margin clear-left':$state.name.indexOf('auth') > -1}">
        <div data-ui-view="header"></div>
        <div class="alert alert-fixed-top alert-success alert-dismissible" ng-if="$stateParams.activated">
            <button type="button" class="close" data-dismiss="alert" aria-label="Close"><span
                        aria-hidden="true">&times;</span></button>
            <strong>Neat!</strong> Your account is activated.
        </div>
        <div class="main-container-wrapper-static">
            <div class="container-fluid">

                <div class="main-container container">
                    <div ng-if="isAuthenticated() && $state.name != 'admin' && $state.name != 'dashboard'"
                         class="page-head">
                        <h3 class="page-title">
                            <!--<span ng-bind-html="$state.data.prefix" class="page-title-prefix"></span>-->
                            <span ng-bind-html="$state.data.pageName"></span>&nbsp;
                            <div ng-show="loading" id="spinner" data-spinner='{"radius": 15,"strokeWidth":3}'
                                 style="display: inline-block;"></div>
                        </h3>
                        <p ng-if="$state.data.pageDescription" class="help-block"
                           ng-bind-html="$state.data.pageDescription"></p>
                        <ui-breadcrumbs ng-if="$state.data.displayName" displayname-property="data.displayName"
                                        template-url="js/app/core/layout/partials/uiBreadcrumbs.tpl.html">
                        </ui-breadcrumbs>
                    </div>
                    <br><br>
                    <div data-ui-view="content" class="main-container-inner"></div>
                </div>
            </div>

        </div>
        <div data-ui-view="footer"></div>
    </div>
</div>

<script>
  window.enableLogs = false;
  window.konga_version = "0.14.9";
  window.no_auth = false;
  window.initAngular = true;
</script>
<!--
    Client-side Templates
    ========================

    HTML templates are important prerequisites of modern, rich client applications.
    To work their magic, frameworks like Backbone, Angular, Ember, and Knockout require
    that you load these templates client-side.

    By default, your Gruntfile is configured to automatically load and precompile
    client-side JST templates in your `assets/templates` folder, then
    include them here automatically (between TEMPLATES and TEMPLATES END).

    To customize this behavior to fit your needs, just edit `tasks/pipeline.js`.
    For example, here are a few things you could do:

        + Import templates from other directories
        + Use a different template engine (handlebars, jade, dust, etc.)
        + Internationalize your client-side templates using a server-side
          stringfile before they're served.
-->

<!--TEMPLATES-->

<!--TEMPLATES END-->


<!--

  Client-side Javascript
  ========================

  You can always bring in JS files manually with `script` tags, or asynchronously
  on the client using a solution like AMD (RequireJS).  Or, if you like, you can
  take advantage of Sails' conve

PostgreSQL9.6.24

PostgreSQL
fe_sendauth: no password supplied

HTTP/1.1 200 OK
Date: Sun, 23 Feb 2025 02:08:07 GMT
Content-Type: application/json; charset=utf-8
Connection: keep-alive
Access-Control-Allow-Origin: *
Content-Length: 11040
X-Kong-Admin-Latency: 3
Server: kong/2.8.1