Web server – Will a root domain with an A record pointing to a private IP address be publicly visible? (Gitlab)

I have a private Gitlab instance running on a private IP. I would like to host a website with Gitlab pages that are only visible within my network and not accessible from the outside. I also need my private Gitlab instance Not be accessible from the outside.

Gitlab pages can only be used if the following prerequisites are met:

Have an exclusive root domain for serving GitLab Pages. Note that you cannot use a subdomain of your GitLab’s instance domain.
Configure a wildcard DNS record.
(Optional) Have a wildcard certificate for that domain if you decide to serve Pages under HTTPS.
(Optional but recommended) Enable Shared runners so that your users don’t have to bring their own.
(Only for custom domains) Have a secondary IP.

I'd like to configure it that way, but it's only useful to me if my gitlab instance is not open to the public and if my site could be hosted on my network.

Is that possible? Or will it open my server to the public?

Thank you in advance, much appreciated.

Blockchain – Bitcoin I was asked to send money for a private key

Hello, I was asked to send money for funds that are not expendable to get a private key to unlock. He comes from Bitcoin investments. How sure is that because I'm worried I will not get the payment. It's currently in my blockchain wallet account, displaying the credit as ineligible until unlocked with a private key

What are design considerations as API developers / engineers when creating private and public APIs?

In my previous company, I created APIs that were primarily intended for (public) customers. At that time I was new to designing and joined after endpoints were already created, so I could not participate in the discussions.

Are there any differences in the considerations that normally consider developers / engineers / architects / companies / companies when creating private or public APIs? apart from the safety?

[APP][FREE] Jettly: Private Jet Charter

Jettly: Private Jet Charter app is one of the best air travel apps on the market. But do not trust only our word for it. You can examine the following reasons why we claim to be the best on the market:

• It's super fast
• Real-time updates
• 9,500 aircraft
• Over 1,500 servers
• Great prices
• Attractive and reliable user interface

Now you can book a charter flight on your mobile phone in just a few minutes. With a variety of options at stunning prices, Jettly is the king of airplane apps.

Whether you are looking for empty flights or want to compare the prices of several airlines for your business travel. Jettly is the best choice.

Jettly is in a way a game changer. Unlike other apps, where you only have to wait a few minutes to load rates or timings for slow algorithms, all the information is delivered within seconds. That's because at Jettly, we know how precious your time is, and we do not want you to wait.

Travel around the world in just a few clicks with this app. And we believe in complete transparency. That's why you can get all the information about your jet, whether it's the cockpit, floor plan or cabin height.

In addition, our Flight Finder feature is the best of its kind, allowing you to find the best private aircraft available in real time. You no longer have to visit different websites and search for several hours.

We offer everything you need for your travels in a single app to make the process more efficient, faster and more reliable.

Many similar apps have problems with their payment systems, but not with Jettly. With Jettly you can be sure that your payment is secured in cash or by credit card. In addition, the payment process is extremely simple and fast.

Download now:


What does a private Bitcoin flash key look like?

Elliptic Curve Private Keys are only scalar integer values ​​between 1 and n (The Order from G). These can be encoded in any way, but are usually represented only as 256-bit integers, regardless of which endian the platform uses. When interpreted as an array of bytes, it's simply a 32-byte sequence.

Bitcoin's WIF (Wallet Import Format) uses the 32-byte sequence, prepends a version byte, and then generates a checksum with the Double-SHA256. The first 4 bytes of the checksum are appended to the bytes of the version and the private key to form a sequence of 37 bytes in total. This is then Base58Check-encoded to produce the textual representation of the private keys you trust. The reason they all start with 5 is the version byte.

In the Lightning specifications, there is no specification for the storage or import / export format of private keys, and it is up to the implementers to decide how they should be stored or how they should be exported, if at all. If you prefer, you can use the same WIF format because Lightning uses the same curve as Bitcoin for signing and key exchange.

Private keys are used in Lightning for two different purposes. The Lightning node itself has a single fixed private key that is used both to identify the node (based on its public key) and to sign messages that actually prove to be from that node. It is also used to perform an authenticated key exchange when connecting to peers to prevent MitM attacks.

The other private keys used in Lightning are entries of a Bitcoin wallet that is used to sign transactions related to the channel states, which are standard Bitcoin transaction outputs.

However, it is not enough to know the private key for a particular channel to output for that channel, since it is 2 out of 2 multisig issues and both parties must sign off the transaction to output it. You must therefore be aware of a purchase transaction and a signature of the counterparty for this transaction additionally on your own private key for the channel.

Obviously, it's not very useful to export these private keys alone – you need a more detailed format that includes all the parts needed to keep the current state of the channel to a minimum. In practice, you should also record all previous channel conditions so that you can create a Justice transaction if the other party is trying to propagate an expired channel state, unless you have delegated that role to a Watchtower, who should have a file.

Search all features for a private Bitcoin Lightning key using mobile devices, desktops, or cli wallets?

Bitcoin wallets have the "swipe everything" function to transfer all coins from one private key to another. Is there such a feature in a Bitcoin Lightning wallet that you can sweep all the coins from a private Lightning key to another Lightning address?

Encryption – Can private key information be displayed when signing an email?

Therefore, I know that PGP-encrypted emails from a familiar, consistent email footer or greeting ("hello," "sincerely, xxx," etc.) may be vulnerable to a known plaintext attack. However, this also applies to PGP signatures on an e-mail?

If I always sign my emails from PGP and all my emails end with "From, (name)", can one of my secret PGP information be displayed?

postgresql – Postgres replication standby server with certified authentication and passphrase encrypted private key

I configure streaming replication in Postgres 11.5 using passphrase encrypted SSL certificates for standby authentication (authentication type = certificate). Here is my primary server configuration:

hostssl replication replication cert

Here is my standby recovery.conf:

standby_mode = 'on'
    primary_conninfo = 'user=replication host= port=5432 sslmode=require sslcompression=0 sslcert=''/postgre_server_ssl/client.crt'' sslkey=''/postgre_server_ssl/client.key'' sslrootcert=''/postgre_server_ssl/root.crt'' '

and standby postgres.conf:

hot_standby = on
    hot_standby_feedback = on
    ssl_passphrase_command = 'echo mypassword'

The private standby key used to connect to the primary key (/postgre_server_ssl/client.key) is encrypted with a passphrase.

Standby server starts ok, but can not connect to the primary, Replication does not work and I get the message that I can not decrypt the given private key. Here is my protocol:

Enter PEM pass phrase:< 2019-10-10 10:11:28.706 UTC   >LOG:  received fast shutdown request
    < 2019-10-10 10:11:28.709 UTC   >LOG:  aborting any active transactions
    < 2019-10-10 10:11:28.709 UTC   >FATAL:  could not connect to the primary server: could not load private key file "/postgre_server_ssl/client.key": problems getting password

Is there a way to specify the passphrase for the private SSL key for the standby connection to the primary connection? Maybe a callback as ssl_passphrase_command These only work at server startup, but not at replication connections.

RentVPS – dedicated virtual private server [ $5 ONLY ] [ 99.9% Uptime since 2015 ]

RentVPS – dedicated virtual private server
The perfect virtual private server provider with dedicated hardware. Virtual Private Server with high performance, instant scalability, and fast deployment.

Powerful servers with high-end resources that guarantee resource exclusivity with immediate effect $ 5 / month

99.9% operating time since 2015


1 core CPU
1 GB of memory
25 GB hard disk space
10 Gbps uplink
$ 5 / month
Order now


1 core CPU
2 GB of memory
50 GB hard disk space
10 Gbps uplink
$ 10 / month
Order now


2 cores CPU
4 GB of memory
100 GB of hard disk space
10 Gbps uplink
$ 20 / month
Order now


Double handover with private ASN

The data center offers a double handover with a private ASN. Each hand through a / 30. One / 22 IPv4 area is hosted.

If both fibers go into the same switch and make a BGP session with the private ASN, or if each fiber goes into a separate switch, two BGP sessions (one on each switch) are created with the same private ASN (and one iBGP between the ASN) two, as they share the same private shipping notification).

Can some of you please join in and give your feedback on the experience of double handoffs?