Forte ita factum est ut per professionem me administratorem systematum computatrorum et reticulorum (brevi: systematis administratoris), et prof. paulo plus quam 10 annos narrandi facultatem habui. operationes variae systematum, in iis quae securitatem mensuras exigunt. Accidit etiam ut dudum eam interesting dev
sic ego transirem). Sed de progressu non loquor, dico de ambitu tuto et efficiente applicationum.
Technology financial (fintech) Ad securitatem notitia iuxta (InfoSec) et prima potest sine secunda operari, sed non diu. Quam ob rem cupio experientiam meam communicare et instrumentorum instrumentorum, quibus utor, in quo utrumque includit fintechautem InfoSecet simul et pro ampliore vel omnino alio proposito adhiberi potest. In hoc articulo tibi non tam de BitCoin, sed de infrastructura exemplar narrabo pro evolutione et operatione nummariae (et non solum) officia - verbo, officia ubi "B" refert. Hoc pertinet tam ad permutationem BitCoin quam ad corporatum proprium saepti ferarum servitiorum parvi societas nullo modo cum Bitcoino coniuncta.
Notare velim me esse fautorem principiorum "stultum simplex custodiret" ΠΈ "minor plus est"ergo et articulus et quae in eo descripta sunt, habent proprietates de his principiis.
Missionem imaginariam: Intueamur omnia utentes exemplo bitcoin commutatoris. Commutationem rublorum, dollariorum, nummorum nummorum et dorsum referre decrevimus, et solutionem laboratam iam habemus, sed pro aliis nummis digitalibus sicut qiwi et web pecunia, i.e. Omnes quaestiones legales clausimus, applicationem promptam habemus quae portae solutionis pro rublis, dollariis et nummis et aliis systematibus solvendis inservit. Coniungitur rationibus nostris argentariis et API quasdam applicationes ad finem nostrum habet. Applicationem interretialem habemus, quae uti commutator pro usoribus agit, bene, sicut ratio typica qiwi vel monetae web - rationem creare, schedulam addere, et sic porro. Communicat cum applicatione portae nostrae, licet per CAETERA API in loci area. Et ideo placuit bitcollis coniungere et simul infrastructuram upgrade, quia... Initio, omnia festinantia virtualis capsulae in officio sub mensa ponebantur... situs adhiberi coepit, et de ultimis et agendis solliciti esse coepimus.
ΠΡΠ°ΠΊ, Π½Π°ΡΠ½ΡΠΌ Ρ ΠΎΡΠ½ΠΎΠ²Π½ΠΎΠ³ΠΎ β Π²ΡΠ±ΠΎΡ ΡΠ΅ΡΠ²Π΅ΡΠ°. Π’.ΠΊ. Π±ΠΈΠ·Π½Π΅Ρ Π² Π½Π°ΡΠ΅ΠΌ ΠΏΡΠΈΠΌΠ΅ΡΠ΅ ΠΌΠ°Π»Π΅Π½ΡΠΊΠΈΠΉ ΠΈ ΠΌΡ Π΄ΠΎΠ²Π΅ΡΡΠ΅ΠΌ Ρ
ΠΎΡΡΠ΅ΡΡ (OVH) ΠΌΡ Π²ΡΠ±Π΅ΡΠ΅ΠΌ
Servo institutionem
Omnia hic simplicia sunt. Eligamus odio quae necessitatibus nostrum decet. Tunc eligere FreeBSD imaginem. Bene, vel coniungimus (in alio hoste et nostro ferramento) per IPMI vel cum monitore et pasce imaginem .iso FreeBSD in download. Nam orchestrae setup utar
Systematis institutio modo normae occurrit, in hoc non moror, tantum notabo, antequam operatio proficiscatur, operae pretium est animadvertere. cæcitas options quod offert bsdinstaller
in fine institutionis (si ratio te ipsum install)
Sunt
Fieri etiam potest ut praedictos parametros in systemate iam inaugurato efficere possit. Ad hoc efficiendum, limam bootloader emendare debes et parametri nucleos da. *ee est editor sic in BSD
# ee /etc/rc.conf
...
#sec hard
clear_tmp_enable="YES"
syslogd_flags="-ss"
sendmail_enable="NONE"
# ee /etc/sysctl.conf
...
#sec hard
security.bsd.see_other_uids=0
security.bsd.see_other_gids=0
security.bsd.unprivileged_read_msgbuf=0
security.bsd.unprivileged_proc_debug=0
kern.randompid=$(jot -r 1 9999)
security.bsd.stack_guard_page=1
Fac etiam ut novissimam versionem systematis inauguratam habere debeas, et
Deinde configurare aide
vigilantia status imaginum systematis conformationis. Plura legere potes in detail
pkg install aide
et nostram crontab edit
crontab -e
06 01 * * 0-6 /root/chkaide.sh
#! /bin/sh
#chkaide.sh
MYDATE=`date +%Y-%m-%d`
MYFILENAME="Aide-"$MYDATE.txt
/bin/echo "Aide check !! `date`" > /tmp/$MYFILENAME
/usr/local/bin/aide --check > /tmp/myAide.txt
/bin/cat /tmp/myAide.txt|/usr/bin/grep -v failed >> /tmp/$MYFILENAME
/bin/echo "**************************************" >> /tmp/$MYFILENAME
/usr/bin/tail -20 /tmp/myAide.txt >> /tmp/$MYFILENAME
/bin/echo "****************DONE******************" >> /tmp/$MYFILENAME
includuntur
sysrc auditd_enable=YES
# service auditd start
Quomodo hanc rem administrare perfecte describitur
Nunc reboot et ad programmatum in calculonis pro- gredimur. Quisque server hypervisor pro vasis vel machinis virtualibus plenus est. Ideo interest ut processus VT-x et EPT sustineat si plenam virtualizationem uti cogitamus.
Ad administrare vasa et virtualis machinis utar
Vasa? Quidve iterum Docker?
Sed non. cbsd
haec continentia orchestrate, quae cellae vocantur.
Cavea est maxime efficax solutio ad infrastructuras aedificandas propter varios fines, ubi tandem singulorum officiorum vel processuum solitudo requiritur. Essentialiter clone ratio exercitus est, sed hardware plenam virtualizationem non requirit. Et propter hoc, "hospes OS" non impendit facultates, sed tantum in opere faciendo. Cum cellulae pro necessitatibus internis adhibentur, haec solutio valde opportuna est ad usum resource optimalis - fasciculum cellularum in uno servo ferrario, si opus est, singulatim singulatim totam subsidiis server uti possunt. Considerantes plerumque alia servitia additamenta egere. facultates diversis temporibus, maximam observantiam ab uno servo colligere potes si cellas inter ministrantium apte disponas et aequivales. Si opus est, cellulae etiam restrictiones dari possunt in subsidiis adhibitis.
Quid de plena virtualizatione?
Ut, sicut usque scio, cbsd
sustinet opus bhyve
et hypervisores XEN. Numquam secundo usus sum, sed primus est relative novus bhyve
infra in gr.
Installing et configurans Hostiam Opera
Utimur FS *
gpart add -t freebsd-zfs /dev/ada0
/dev/ada0p4 added!
addere disco partitione reliquae spatium
geli init /dev/ada0p4
intrare encryption ignoro
geli attach /dev/ada0p4
Tesseram iterum intramus et machinam /dev/ada0p4.eli habemus - hoc est spatium encrypted nostrum. Idem repetimus pro /dev/ada1 et reliquo orbe in apparatu. Et novum creare
zpool create vms mirror /dev/ada0p4.eli /dev/ada1p4.eli /dev/ada3p4.eli
- Bene nos habemus ornamentum pugnae minimum paratum. Ordinata orbis specularis si unus e tribus deficit.
Creando dataset in novum "stagnum"
zfs create vms/jails
pkg install cbsd
- turmas demisimus et administrationem cellis nostris constituimus.
Post cbsd
inauguratus, indiget initialized;
# env workdir="/vms/jails" /usr/local/cbsd/sudoexec/initenv
Bene respondemus fasciculum quaestionum, maxime cum defectibus responsionibus.
*Si encryption uteris, interest daemonem cbsdd
non statim incipiet donec manually vel automatice orbes minutos (in exemplo nostro zabbix hoc fit)
** Ego quoque non utor a NAT cbsd
et me ipsum configurare pf
.
# sysrc pf_enable=YES
# ee /etc/pf.conf
IF_PUBLIC="em0"
IP_PUBLIC="1.23.34.56"
JAIL_IP_POOL="192.168.0.0/24"
#WHITE_CL="{ 127.0.0.1 }"
icmp_types="echoreq"
set limit { states 20000, frags 20000, src-nodes 20000 }
set skip on lo0
scrub in all
#NAT for jails
nat pass on $IF_PUBLIC from $JAIL_IP_POOL to any -> $IP_PUBLIC
## Bitcoin network port forward
IP_JAIL="192.168.0.1"
PORT_JAIL="{8333}"
rdr pass on $IF_PUBLIC proto tcp from any to $IP_PUBLIC port $PORT_JAIL -> $IP_JAIL
# service pf start
# pfctl -f /etc/pf.conf
Agnimenta firewall erigendi etiam locus separatus est, ideo ego non penitus in omnium consiliorum impedimentum constituendo ac album album constituendo, id legendo facere potes.
Bene
cbsd jconstruct-tui
Hic videmus cellulam creationem alternis. Postquam omnia bona posita sunt, amet!
Cum primum cellam tuam creando, elige quid ad cellulas basi utatur. Distributio ex FreeBSD eligo cum imperio reposito repo
. Haec electio solum efficitur, cum primam cellulam certae versionis creans (cellulas cuiuslibet versionis hospitari potes quam versionis exercitus maior).
Postquam omnia installantur, caveam deducimus!
# cbsd jstart bitcoind
Sed luctus in velit eget tincidunt.
# jls
JID IP Address Hostname Path
1 192.168.0.1 bitcoind.space.com /zroot/jails/jails/bitcoind
jexec bitcoind
ut in cellula consolatorium
et iam intra cellam instituimus programmatum cum suis clientibus (ratio hospes noster mundus manet)
bitcoind:/@[15:25] # pkg install bitcoin-daemon bitcoin-utils
bitcoind:/@[15:30] # sysrc bitcoind_enable=YES
bitcoind:/@[15:30] # service bitcoind start
BitCoin in cavea est, sed anonymiam egere debemus quia cum aliquibus caveis per TOP retis coniungi volumus. In universum consilium maxime cellas cum programmate suspecto solum per procuratorem currere disponimus. Gratias pf
NAT inactivandi potes propter quandam extensionem IP inscriptionum in retis localis, et tantum nostris TOR nodi permitte NAT. Etiamsi malware cellam ingreditur, verisimile non communicabit cum extra, et si facit, IP servitoris nostri non patefaciet. Ideo cellam aliam ad "proferre" operas ".onion" operas creamus et procuratorem ad Internet accessum ad singulas cellas.
# cbsd jsconstruct-tui
# cbsd jstart tor
# jexec tor
tor:/@[15:38] # pkg install tor
tor:/@[15:38] # sysrc tor_enable=YES
tor:/@[15:38] # ee /usr/local/etc/tor/torrc
Pone audire ad inscriptionem localem (praesto omnibus cellulis)
SOCKSPort 192.168.0.2:9050
Quid aliud opus est ad plenam felicitatem? Etiam in telae nostrae servitio indigemus, fortasse pluribus. Nginx demus, quae ut procuratorem agat et curet renovandae Encrypt libellorum.
# cbsd jsconstruct-tui
# cbsd jstart nginx-rev
# jexec nginx-rev
nginx-rev:/@[15:47] # pkg install nginx py36-certbot
Itaque 150 MB clientum in cavea posuimus. et adhuc mundus est hospes.
Redeamus ad ngincem constituendum, duas plures cellulas erigere nobis necesse est ut portae solutionis in nodejs et aerugine et telarum applicatione, quae aliqua de causa in Apache et PHP est, et haec etiam in database MySQL requirit.
# cbsd jsconstruct-tui
# cbsd jstart paygw
# jexec paygw
paygw:/@[15:55] # pkg install git node npm
paygw:/@[15:55] # curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
...et alius 380 MB fasciculorum semotus
Deinde, applicationes nostras cum git et deprimimus.
# cbsd jsconstruct-tui
# cbsd jstart webapp
# jexec webapp
webapp:/@[16:02] # pkg install mariadb104-server apache24 php74 mod_php74 php74-pdo_mysql
450 MB packages. in cavea.
hic elit aditum per SSH directe ad cellam damus, ipsi omnia ibi facient;
webapp:/@[16:02] # ee /etc/ssh/sshd_config
Port 2267
- SSH portum cellae ad aliquem arbitrarium
webapp:/@[16:02] # sysrc sshd_enable=YES
webapp:/@[16:02] # service sshd start
Bene, servitus currit, omne quod superest regulam addere est pf
Firewall
Videamus quid IP cellae nostrae habeant et quid area nostra "loci" plerumque similis sit.
# jls
JID IP Address Hostname Path
1 192.168.0.1 bitcoind.space.com /zroot/jails/jails/bitcoind
2 192.168.0.2 tor.space.com /zroot/jails/jails/tor
3 192.168.0.3 nginx-rev.space.com /zroot/jails/jails/nginx-rev
4 192.168.0.4 paygw.space.com /zroot/jails/jails/paygw
5 192.168.0.5 webapp.my.domain /zroot/jails/jails/webapp
et adde regulae
# ee /etc/pf.conf
## SSH for web-Devs
IP_JAIL="192.168.0.5"
PORT_JAIL="{ 2267 }"
rdr pass on $IF_PUBLIC proto tcp from any to $IP_PUBLIC port $PORT_JAIL -> $IP_JAIL
Bene, quia hic sumus, regulam quoque adiciamus in contrarium procuratoris:
## web-ports for nginx-rev
IP_JAIL="192.168.0.3"
PORT_JAIL="{ 80, 443 }"
rdr pass on $IF_PUBLIC proto tcp from any to $IP_PUBLIC port $PORT_JAIL -> $IP_JAIL
# pfctl -f /etc/pf.conf
Age, nunc pauca de bitcoins
Quod habemus, habemus applicationem interretialem quae extrinsecus exposita est et localiter ad solutionem portae loquitur. Nunc opus est ambitum praeparare ad se mutuo retis BitCoin - nodi bitcoind
iustus daemon est, qui loci exemplum impedimenti servat usque ad modernum. Hic daemon RPC et manticae functionis est, sed commodius "involucris" ad applicationem evolutionis habet. Incipere, constituimus electrum
eft pera cli.
laptop. Nunc enim Electrum cum ministris publicis utemur, et postea in alia cellula excitabimus
# cbsd jsconstruct-tui
# cbsd jstart electrum
# jexec electrum
electrum:/@[8:45] # pkg install py36-electrum
alius DCC MB of software in cavea nostra
electrum:/@[8:53] # adduser
Username: wallet
Full name:
Uid (Leave empty for default):
Login group [wallet]:
Login group is wallet. Invite wallet into other groups? []:
Login class [default]:
Shell (sh csh tcsh nologin) [sh]: tcsh
Home directory [/home/wallet]:
Home directory permissions (Leave empty for default):
Use password-based authentication? [yes]: no
Lock out the account after creation? [no]:
Username : wallet
Password : <disabled>
Full Name :
Uid : 1001
Class :
Groups : wallet
Home : /home/wallet
Home Mode :
Shell : /bin/tcsh
Locked : no
OK? (yes/no): yes
adduser: INFO: Successfully added (wallet) to the user database.
Add another user? (yes/no): no
Goodbye!
electrum:/@[8:53] # su wallet
electrum:/@[8:53] # su wallet
wallet@electrum:/ % electrum-3.6 create
{
"msg": "Please keep your seed in a safe place; if you lose it, you will not be able to restore your wallet.",
"path": "/usr/home/wallet/.electrum/wallets/default_wallet",
"seed": "jealous win pig material ribbon young punch visual okay cactus random bird"
}
vidulum nunc creatum habemus.
wallet@electrum:/ % electrum-3.6 listaddresses
[
"18WEhbjvMLGRMfwudzUrUd25U5C7uZYkzE",
"14XHSejhxsZNDRtk4eFbqAX3L8rftzwQQU",
"1KQXaN8RXiCN1ne9iYngUWAr6KJ6d4pPas",
...
"1KeVcAwEYhk29qEyAfPwcBgF5mMMoy4qjw",
"18VaUuSeBr6T2GwpSHYF3XyNgLyLCt1SWk"
]
wallet@electrum:/ % electrum-3.6 help
Ad nostrum in catena, Tantum paucitas hominum ad peram posthac coniungere poterit. Ne aditus cellae huic ab extra pateat, nexus per SSH per TOP occurrent (versio decentra facta VPN). SSH in cellam demittimus, sed nostram pf.conf in hospitio non tangimus.
electrum:/@[9:00] # sysrc sshd_enable=YES
electrum:/@[9:00] # service sshd start
Nunc cellam agamus cum accessu interreti viduli. Demus ei electronicam IP ex alia subnet spatii non NATed. Primum mutationem /etc/pf.conf
in exercitum
# ee /etc/pf.conf
JAIL_IP_POOL="192.168.0.0/24"
lets mutare eam JAIL_IP_POOL="192.168.0.0/25"
, ita omnes inscriptiones 192.168.0.126-255 ad Internet accessum directum non habebunt. Genus programmatis "air-gap" ornatum. Regula autem NAT, sicut erat, manet
nat pass on $IF_PUBLIC from $JAIL_IP_POOL to any -> $IP_PUBLIC
Nocent praecepta
# pfctl -f /etc/pf.conf
Nunc sumamus cellulam nostram
# cbsd jconfig jname=electrum
jset mode=quiet jname=electrum ip4_addr="192.168.0.200"
Remove old IP: /sbin/ifconfig em0 inet 192.168.0.6 -alias
Setup new IP: /sbin/ifconfig em0 inet 192.168.0.200 alias
ip4_addr: 192.168.0.200
Hmm, sed iam ratio ipsa nos ab opere cessabit. Sed procuratorem systematis definire possumus. Sed aliud est, in TOR SOCKS5 procuratorem esse, ac commoditatis HTTP procuratorem etiam volumus.
# cbsd jsconstruct-tui
# cbsd jstart polipo
# jexec polipo
polipo:/@[9:28] # pkg install polipo
polipo:/@[9:28] # ee /usr/local/etc/polipo/config
socksParentProxy = "192.168.0.2:9050"
socksProxyType = socks5
polipo:/@[9:42] # sysrc polipo_enable=YES
polipo:/@[9:43] # service polipo start
Bene, nunc duo procuratores in nostro systemate sunt, et utrumque output per TOR: socks5://192.168.0.2:9050 et
Nunc configurare possumus nostrum crumenam environment
# jexec electrum
electrum:/@[9:45] # su wallet
wallet@electrum:/ % ee ~/.cshrc
#in the end of file proxy config
setenv http_proxy http://192.168.0.6:8123
setenv https_proxy http://192.168.0.6:8123
Age, iam testudo sub procuratore operabitur. Si velimus fasciculos instituere, tum adiciendum est /usr/local/etc/pkg.conf
de sub radix cavea
pkg_env: {
http_proxy: "http://my_proxy_ip:8123",
}
Bene, nunc tempus est servitutem occultam TOR addere sicut inscriptio nostri SSH muneris in pera cavea.
# jexec tor
tor:/@[9:59] # ee /usr/local/etc/tor/torrc
HiddenServiceDir /var/db/tor/electrum/
HiddenServicePort 22 192.168.0.200:22
tor:/@[10:01] # mkdir /var/db/tor/electrum
tor:/@[10:01] # chown -R _tor:_tor /var/db/tor/electrum
tor:/@[10:01] # chmod 700 /var/db/tor/electrum
tor:/@[10:03] # service tor restart
tor:/@[10:04] # cat /var/db/tor/electrum/hostname
mdjus4gmduhofwcso57b3zl3ufoitguh2knitjco5cmgrokpreuxumad.onion
Haec nostra connexio inscriptio est. Sit scriptor machina loci reprehendo. Sed primum necesse est ut SSH clavem nostram addamus:
wallet@electrum:/ % mkdir ~/.ssh
wallet@electrum:/ % ee ~/.ssh/authorized_keys
ecdsa-sha2-nistp521 AAAAE2VjZHNhLXNoYTItbmlzdHA1MjEAAAAIbmlzdHA1MjEAAACFBAG9Fk2Lqi4GQ8EXZrsH3EgSrVIQPQaAlS38MmJLBabihv9KHIDGXH7r018hxqLNNGbaJWO/wrWk7sG4T0yLHAbdQAFsMYof9kjoyuG56z0XZ8qaD/X/AjrhLMsIoBbUNj0AzxjKNlPJL4NbHsFwbmxGulKS0PdAD5oLcTQi/VnNdU7iFw== user@local
Bene, ex machina clientis Linux
user@local ~$ nano ~/.ssh/config
#remote electrum wallet
Host remotebtc
User wallet
Port 22
Hostname mdjus4gmduhofwcso57b3zl3ufoitguh2knitjco5cmgrokpreuxumad.onion
ProxyCommand /bin/ncat --proxy localhost:9050 --proxy-type socks5 %h %p
in obturaculum (Ad hoc laborandum, loci TOR daemonis qui in 9050 audit) debes.
user@local ~$ ssh remotebtc
The authenticity of host 'mdjus4gmduhofwcso57b3zl3ufoitguh2knitjco5cmgrokpreuxumad.onion (<no hostip for proxy command>)' can't be established.
ECDSA key fingerprint is SHA256:iW8FKjhVF4yyOZB1z4sBkzyvCM+evQ9cCL/EuWm0Du4.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added 'mdjus4gmduhofwcso57b3zl3ufoitguh2knitjco5cmgrokpreuxumad.onion' (ECDSA) to the list of known hosts.
FreeBSD 12.1-RELEASE-p1 GENERIC
To save disk space in your home directory, compress files you rarely
use with "gzip filename".
-- Dru <[email protected]>
wallet@electrum:~ % logout
Prosperitas!
Ad instantiam et parvarum solutionum laborandum, nodo etiam opus est c-lightning
requisiti muneris bitcoind
sed sic.
*Variae sunt exsecutiones protocolli fulguris Network in diversis linguis. Eorum, quae probavimus, fulmen maxime firmum videbatur et efficax
# cbsd jsconstruct-tui
# cbsd jstart cln
# jexec cln
lightning:/@[10:23] # adduser
Username: lightning
...
lightning:/@[10:24] # pkg install git
lightning:/@[10:23] # su lightning
cd ~ && git clone https://github.com/ElementsProject/lightning
lightning@lightning:~ % exit
lightning:/@[10:30] # cd /home/lightning/lightning/
lightning:/home/lightning/lightning@[10:31] # pkg install autoconf automake gettext git gmp gmake libtool python python3 sqlite3 libsodium py36-mako bash bitcoin-utils
lightning:/home/lightning/lightning@[10:34] # ./configure && gmake && gmake install
Dum omnia necessaria sunt compilata et inaugurata, RPC usorem creemus lightningd
Π² bitcoind
# jexec bitcoind
bitcoind:/@[10:36] # ee /usr/local/etc/bitcoin.conf
rpcbind=192.168.0.1
rpcuser=test
rpcpassword=test
#allow only c-lightning
rpcallowip=192.168.0.7/32
bitcoind:/@[10:39] # service bitcoind restart
Mea tenebrarum commutatio inter cellulas non ita evadit tenebrarum si utilitatem notas tmux
quae permittit ut multiplices sessiones sub-terminales intra unam sessionem crees. Analogia: screen
Ita, realem IP nostri nodi revelare noluimus, et omnes res oeconomicas per TOP gerere volumus. Ergo alia .onion non indiget.
# jexec tor
tor:/@[9:59] # ee /usr/local/etc/tor/torrc
HiddenServiceDir /var/db/tor/cln/
HiddenServicePort 9735 192.168.0.7:9735
tor:/@[10:01] # mkdir /var/db/tor/cln
tor:/@[10:01] # chown -R _tor:_tor /var/db/tor/cln
tor:/@[10:01] # chmod 700 /var/db/tor/cln
tor:/@[10:03] # service tor restart
tor:/@[10:04] # cat /var/db/tor/cln/hostname
en5wbkavnytti334jc5uzaudkansypfs6aguv6kech4hbzpcz2ove3yd.onion
Nunc faciamus aboutconfig pro c fulgure
lightning:/home/lightning/lightning@[10:31] # su lightning
lightning@lightning:~ % mkdir .lightning
lightning@lightning:~ % ee .lightning/config
alias=My-LN-Node
bind-addr=192.168.0.7:9735
rgb=ff0000
announce-addr=en5wbkavnytti334jc5uzaudkansypfs6aguv6kech4hbzpcz2ove3yd.onion:9735
network=bitcoin
log-level=info
fee-base=0
fee-per-satoshi=1
proxy=192.168.0.2:9050
log-file=/home/lightning/.lightning/c-lightning.log
min-capacity-sat=200000
# sparko plugin
# https://github.com/fiatjaf/lightningd-gjson-rpc/tree/master/cmd/sparko
sparko-host=192.168.0.7
sparko-port=9737
sparko-tls-path=sparko-tls
#sparko-login=mywalletusername:mywalletpassword
#sparko-keys=masterkey;secretread:+listchannels,+listnodes;secretwrite:+invoice,+listinvoices,+delinvoice,+decodepay,+waitpay,+waitinvoice
sparko-keys=masterkey;secretread:+listchannels,+listnodes;ultrawrite:+invoice,+listinvoices,+delinvoice,+decodepay,+waitpay,+waitinvoice
# for the example above the initialization logs (mixed with lightningd logs) should print something like
lightning@lightning:~ % mkdir .lightning/plugins
lightning@lightning:~ % cd .lightning/plugins/
lightning@lightning:~/.lightning/plugins:% fetch https://github.com/fiatjaf/sparko/releases/download/v0.2.1/sparko_full_freebsd_amd64
lightning@lightning:~/.lightning/plugins % mkdir ~/.lightning/sparko-tls
lightning@lightning:~/.lightning/sparko-tls % cd ~/.lightning/sparko-tls
lightning@lightning:~/.lightning/sparko-tls % openssl genrsa -out key.pem 2048
lightning@lightning:~/.lightning/sparko-tls % openssl req -new -x509 -sha256 -key key.pem -out cert.pem -days 3650
lightning@lightning:~/.lightning/plugins % chmod +x sparko_full_freebsd_amd64
lightning@lightning:~/.lightning/plugins % mv sparko_full_freebsd_amd64 sparko
lightning@lightning:~/.lightning/plugins % cd ~
etiam debes creare limam configurationem pro bitcoin-cli, utilitatem communicantem cum bitcoind
lightning@lightning:~ % mkdir .bitcoin
lightning@lightning:~ % ee .bitcoin/bitcoin.conf
rpcconnect=192.168.0.1
rpcuser=test
rpcpassword=test
reprehendo
lightning@lightning:~ % bitcoin-cli echo "test"
[
"test"
]
launch lightningd
lightning@lightning:~ % lightningd --daemon
ipsum lightningd
utilitatem control potes lightning-cli
For example:
lightning-cli newaddr
ut oratio ad novam mercedem advenientis
{
"address": "bc1q2n2ffq3lplhme8jufcxahfrnfhruwjgx3c78pv",
"bech32": "bc1q2n2ffq3lplhme8jufcxahfrnfhruwjgx3c78pv"
}
lightning-cli withdraw bc1jufcxahfrnfhruwjgx3cq2n2ffq3lplhme878pv all
Pecuniam omnem in scrip electronica (all on- catena oratio)
Mandat etiam pro off-cathena operationum lightning-cli invoice
, lightning-cli listinvoices
, lightning-cli pay
etc.
Bene, ad communicationem cum applicatione habemus requiem Api .
curl -k https://192.168.0.7:9737/rpc -d '{"method": "pay", "params": ["lnbc..."]}' -H 'X-Access masterkey'
Summatim
# jls
JID IP Address Hostname Path
1 192.168.0.1 bitcoind.space.com /zroot/jails/jails/bitcoind
2 192.168.0.2 tor.space.com /zroot/jails/jails/tor
3 192.168.0.3 nginx-rev.space.com /zroot/jails/jails/nginx-rev
4 192.168.0.4 paygw.space.com /zroot/jails/jails/paygw
5 192.168.0.5 webapp.my.domain /zroot/jails/jails/webapp
7 192.168.0.200 electrum.space.com /zroot/jails/jails/electrum
8 192.168.0.6 polipo.space.com /zroot/jails/jails/polipo
9 192.168.0.7 lightning.space.com /zroot/jails/jails/cln
Vasa statuta habemus, cum suo quaeque gradu accessus tam ab eo quam ad loci network.
# zfs list
NAME USED AVAIL REFER MOUNTPOINT
zroot 279G 1.48T 88K /zroot
zroot/ROOT 1.89G 1.48T 88K none
zroot/ROOT/default 1.89G 17.6G 1.89G /
zroot/home 88K 1.48T 88K /home
zroot/jails 277G 1.48T 404M /zroot/jails
zroot/jails/bitcoind 190G 1.48T 190G /zroot/jails/jails-data/bitcoind-data
zroot/jails/cln 653M 1.48T 653M /zroot/jails/jails-data/cln-data
zroot/jails/electrum 703M 1.48T 703M /zroot/jails/jails-data/electrum-data
zroot/jails/nginx-rev 190M 1.48T 190M /zroot/jails/jails-data/nginx-rev-data
zroot/jails/paygw 82.4G 1.48T 82.4G /zroot/jails/jails-data/paygw-data
zroot/jails/polipo 57.6M 1.48T 57.6M /zroot/jails/jails-data/polipo-data
zroot/jails/tor 81.5M 1.48T 81.5M /zroot/jails/jails-data/tor-data
zroot/jails/webapp 360M 1.48T 360M /zroot/jails/jails-data/webapp-data
Ut videre potes, bitcoind omnia 190 GB spatii occupat. Quid si alio nodo ad probationem indigemus? Ubi ZFS in promptu venit. Cum auxilio cbsd jclone old=bitcoind new=bitcoind-clone host_hostname=clonedbtc.space.com
potes creare snapshot et novam cellulam huic snapshot. Nova cellula suum spatium habebit, sed sola differentia inter statum hodiernum et originalem ratio in tabella ratiocinabitur (saltem 190 GB servabimus)
Quaelibet cellula est propria ZFS dataset separata, et hoc perquam opportunum est.
Notatu dignum est etiam necessitatem remotae magnae militiae, ad haec proposita
B - salus
Ad securitatem, a principiis cardinis in contextu infrastructure incipiamus:
et secreto - Instrumenta sacra unix systemata similia huius principii exsecutionem procurant. Aditum logice separamus unicuique elementi systematis logice separato - cellae. Accessus praebetur per normas usoris authenticas utendi claves personales usorum. Omnis communicatio inter et ad finem cellulas in forma encryptata occurrit. Gratias orbis encryption, non debemus solliciti esse de salute notitiarum cum reponens disco vel migrando alteri servo. Solus accessus criticus ad systematis militiae accessum est, quia talis accessus plerumque aditus ad notitias intra vasa praebet.
integritas Β« Exsecutio huius principii in pluribus diversis gradibus occurrit. Primo, interest notare quod in ferramentis, ECC memoria, ZFS iam "ex arca" diligentiam notitiarum integritatis in gradu informationum frena curat. Instant snapshots permittunt te tergum facere aliquando in musca. Commoda cellula export/importorum instrumenta faciunt replicationem cellulam simplicem.
disponibilitate - Hoc iam libitum est. Ex gradu famae tuae et quod osores habes. In exemplo nostro prospiciebamus vidulum solum e summo reticulo adiri fuisse. Si opus est, omnia in foco claudere potes et accessum ad solum per cuniculos servo permittere (TOR vel VPN alia res est). Ita ab exterioribus quam maxime cultor abscindetur, et soli nos ipsi promptitudinem influere poterimus.
Impossibilitas recusationis - Et hoc pendet ab ulteriore operatione et obsequio rectae agendi rationes ad iura, accessum, etc. Sed recta accessione, omnes actiones usoris audiuntur, et ob solutiones cryptographicas sine ambiguitate cognosci potest qui actiones quasdam et quando.
Utique, descriptum schematismum non est absolutum exemplum quomodo semper sit, potius unum exemplum est quomodo fieri potest, servata admodum flexibili scalarum et cssmorum facultatibus.
Quid de plena virtualizatione?
De plena virtualizatione uti cbsd potes bhyve
Vos postulo ut bene nucleo aliquo.
# cat /etc/rc.conf
...
kld_list="vmm if_tap if_bridge nmdm"
...
# cat /boot/loader.conf
...
vmm_load="YES"
...
Si ergo subito opus est ut docke incipias, tunc aliquid debian institue et vade!
Id est omnia
Coniecto quod omnia volui communicare. Si articulum probaverunt, tunc me mittere potes bitcoins -
Source: www.habr.com