Metformin Hydrochloride is the hydrochloride salt of the biguanide metformin with antihyperglycemic and potential antineoplastic activities. Metformin inhibits complex I (NADPH:ubiquinone oxidoreductase) of the mitochondrial respiratory chain, thereby increasing the cellular AMP to ATP ratio and leading to activation of AMP-activated protein kinase (AMPK) and regulating AMPK-mediated transcription of target genes. This eventually prevents hepatic gluconeogenesis, enhances insulin sensitivity and fatty acid oxidation and ultimately leads to a decrease in glucose levels. Metformin may exert antineoplastic effects through AMPK-mediated or AMPK-independent inhibition of mammalian target of rapamycin (mTOR), which is up-regulated in many cancer tissues. Furthermore, this agent also inhibits tumor cell migration and invasion by inhibiting matrix metalloproteinase-9 (MMP-9) expression which is mediated through the suppression of transcription activator protein-1 (AP-1) activation.
Monday, October 2, 2017
Ufff...its a complex issue, the anti copy features. they might just place a fake tumbler on the key (Abloy is worldest company selling the locks for banking trucks) that's one part of the question; the other part of the question which is (in my opinion) more accuared, is the cutting system of the key, which is exclusiv...now there's only two companies selling this cutters...what am I talking about ??' I'm taking that cuts are made on two different radius. and 2. it has a 100% chances that if the combination is not accuared the lock blocks the discks, and it going futher after 90.º degrees turn
welcome back to war! I imagine all of us on this particulary high security business know about this amazing tool
SARGENT & GREENLEAF U11 Safe-4 Wheel Combination Lock Change Key-S&G-FREE POST!
http://www.ebay.com/itm/SARGENT-GREENLEAF-U11-Safe-4-Wheel-Combination-Lock-Change-Key-S-G-FREE-POST-/131837362490
hey guys....Moscow East side...lol...do you know what this (coming from Israel?) foil impressing spacer tool for our....favourite locks...ahahahah "Next thing you do is put the foil over a special blank that already has the profile of your target lock. The clever thing about this tool is that the ‘U shaped foil tube’ is wrapped around some sort of needle, and the foil can not be pushed in when entering the lock! Once the key is inserted, the needle is taken out from the back of the tool, and the pins are now resting on the foil. Because of the cuts in the foil, each pin will stand on it’s own ‘island’ of foil, and when it is pushed in will not disturb the neighboring pin"
get this keso 1000 impressing key
Sunday, October 1, 2017
Ok, everybody! first rule (CIA techniques) 1. trow soap in water plastic bags under the police car wheels. 2 trow wet tissues to police windows cars, and air exits trucks,and their spray mounted towers on the trucks. 3 take a picture with a cop that joint the movement!!!!!! fuck if its fake, Use it!
Saturday, September 30, 2017
How to get DNS information with dig ? How to get the IP of a server ?
How to know the Name servers authoritative on a zone ?
Command :
dig +short +answer NS akamai.com
Output :
a1-66.akam.net.a8-66.akam.net.a12-66.akam.net.a7-66.akam.net.a5-66.akam.net.a9-66.akam.net.a3-66.akam.net.a16-66.akam.net.a13-66.akam.net.a28-66.akam.net.a20-66.akam.net.a11-66.akam.net.a2-66.akam.net.
What happens behind ? :
Your computer asks your recursive name server what are the NS for akamai.com.
Your DNS resolver, will ask the Root Server who is in charge of .com.
The Root Servers will provide the authoritative Name Servers of .com.
Your DNS resolver will ask the list of authoritative NS of .com who is in charge of akamai.com.
One of the authoritative NS of .com will give your resolver the answer of who is in charge of akamai.com.
Your recursive name server will reply to your computer who is in charge of akamai.com and will keep it in memory in case you ask him the same question later on.
How to know the path describe above ?
Command :
dig +trace akamai.com
Output :
; <<>> DiG 9.8.1-P1 <<>> +trace akamai.com;; global options: +cmd. 24196 IN NS m.root-servers.net.. 24196 IN NS g.root-servers.net.. 24196 IN NS a.root-servers.net.. 24196 IN NS d.root-servers.net.. 24196 IN NS h.root-servers.net.. 24196 IN NS i.root-servers.net.. 24196 IN NS f.root-servers.net.. 24196 IN NS l.root-servers.net.. 24196 IN NS b.root-servers.net.. 24196 IN NS k.root-servers.net.. 24196 IN NS e.root-servers.net.. 24196 IN NS c.root-servers.net.. 24196 IN NS j.root-servers.net.;; Received 496 bytes from 127.0.0.1#53(127.0.0.1) in 7 mscom. 172800 IN NS a.gtld-servers.net.com. 172800 IN NS b.gtld-servers.net.com. 172800 IN NS c.gtld-servers.net.com. 172800 IN NS d.gtld-servers.net.com. 172800 IN NS e.gtld-servers.net.com. 172800 IN NS f.gtld-servers.net.com. 172800 IN NS g.gtld-servers.net.com. 172800 IN NS h.gtld-servers.net.com. 172800 IN NS i.gtld-servers.net.com. 172800 IN NS j.gtld-servers.net.com. 172800 IN NS k.gtld-servers.net.com. 172800 IN NS l.gtld-servers.net.com. 172800 IN NS m.gtld-servers.net.;; Received 488 bytes from 2001:7fd::1#53(2001:7fd::1) in 85 msakamai.com. 172800 IN NS a5-66.akam.net.akamai.com. 172800 IN NS a11-66.akam.net.akamai.com. 172800 IN NS a13-66.akam.net.akamai.com. 172800 IN NS a28-66.akam.net.akamai.com. 172800 IN NS a16-66.akam.net.akamai.com. 172800 IN NS a7-66.akam.net.akamai.com. 172800 IN NS a9-66.akam.net.akamai.com. 172800 IN NS a3-66.akam.net.akamai.com. 172800 IN NS a12-66.akam.net.akamai.com. 172800 IN NS a1-66.akam.net.akamai.com. 172800 IN NS a2-66.akam.net.akamai.com. 172800 IN NS a20-66.akam.net.akamai.com. 172800 IN NS a8-66.akam.net.;; Received 506 bytes from 192.48.79.30#53(192.48.79.30) in 215 msakamai.com. 20 IN A 23.59.205.239;; Received 44 bytes from 2.22.230.66#53(2.22.230.66) in 41 ms
How to get what is in a recursive name server memory (or cache) ?
You can specify a specific name server using the "@" option, it will request this specific name server. For the example I use the well known Google DNS 8.8.8.8
Command :
dig @8.8.8.8 akamai.com
Output :
; <<>> DiG 9.8.1-P1 <<>> @8.8.8.8 akamai.com; (1 server found);; global options: +cmd;; Got answer:;; ->>HEADER<<- 61926="" b="" id:="" noerror="" opcode:="" query="" status:="">;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0;; QUESTION SECTION:;akamai.com. IN A;; ANSWER SECTION:akamai.com. 19 IN A 23.66.134.36;; Query time: 20 msec;; SERVER: 8.8.8.8#53(8.8.8.8);; WHEN: Mon Feb 8 14:28:42 2016;; MSG SIZE rcvd: 44
What is behind ? :
In the answer section, you can see that we have the IP 23.66.134.36 in memory for 19 seconds left. If you go back to the section where we ran the dig +trace on akamai.com, you can see that the TTL is 20 seconds.
akamai.com. 20 IN A 23.59.205.239;; Received 44 bytes from 2.22.230.66#53(2.22.230.66) in 41 ms
Which means that every 20 seconds, if the zone is updated, we will have this information updated.
How to check if all the NS of a zone are synchronized ?
Your zone DNS i.e : akamai.com has generally multiple NS records. We saw before that for akamai.com we have 13 different ones.
When a zone is modified, the SOA record must be edited and the SOA serial incremented, one easy and fast way to check the version of zone on a NS is to check this value.
Command : (replace ns with the name of the name server you identified previously)
dig +answer +short @a5-66.akam.net. soa akamai.comdig +answer +short @a11-66.akam.net. soa akamai.com[...]
Output
ns1-2.akam.net. hostmaster.akamai.com. 2016020801 7200 3600 1209600 300ns1-2.akam.net. hostmaster.akamai.com. 2016020801 7200 3600 1209600 300
What is behind ? :
We ask the NS following the "@" sign, what is the value of the SOA record.
In the SOA record, the 3rd field is the SOA serial.
We see that the SOA serial on both NS is the same, meaning the zone should be the same.
Another method :
The use of the +nssearch option : "When this option is set, dig attempts to find the authoritative name servers for the zone containing the name being looked up and display the SOA record that each name server has for the zone"
Command :
dig akamai.com +nssearch
Output :
SOA ns1-2.akam.net. hostmaster.akamai.com. 2016020801 7200 3600 1209600 300 from server 172.22.186.6 in 0 ms.SOA ns1-2.akam.net. hostmaster.akamai.com. 2016020801 7200 3600 1209600 300 from server 172.27.2.20 in 40 ms.SOA ns1-2.akam.net. hostmaster.akamai.com. 2016020801 7200 3600 1209600 300 from server 172.17.0.10 in 78 ms.[...]
https://community.akamai.com/community/web-performance/blog/2016/02/08/how-to-troubleshoot-dns-issues-with-dig
Check the SOA Serial Number on NS Servers
If you manage a DNS master, and push zones to several slaves / secondaries, you may have found that over time — as configuration files and firewall rules change — one or more slaves may have lost its ability to update its zone files. Perhaps the slave is no longer being notified, or it may have lost the necessary zone transfer permissions from the master. In a large distributed environment where DNS changes are frequent, checking the SOA serial number for all the NS servers in a zone can be quite helpful — a quick way to eliminate the DNS as a possible source of a problem. Here is a perl script I wrote a few years back to retrieve the SOA serial number for a given domain.
1
2
3
4
5
6
7
8
|
$ ./check_soa.pl surniaulula.com
ns8.surniaulula.com has serial number 2014021905
ns9.surniaulula.com has serial number 2014021905
ns3.surniaulula.com has serial number 2014021905
ns4.surniaulula.com has serial number 2014021905
ns5.surniaulula.com has serial number 2014021905
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
|
#!/usr/bin/perl -w
use Net::DNS;
# Get the domain from the command line.
#
die "Usage: $0 {domainname}\n" unless @ARGV == 1;
$domain = $ARGV[0];
# Find all the nameservers for the domain.
#
$res = new Net::DNS::Resolver;
$res->defnames(0);
$res->retry(2);
$ns_req = $res->query($domain, "NS");
die "No nameservers found for $domain: ", $res->errorstring, "\n"
unless defined($ns_req) and ($ns_req->header->ancount > 0);
@nameservers = grep { $_->type eq "NS" } $ns_req->answer;
# Check the SOA record on each nameserver.
#
$| = 1;
$res->recurse(0);
foreach $nsrr (@nameservers) {
# Set the resolver to query this nameserver.
#
$ns = $nsrr->nsdname;
print "$ns ";
unless ($res->nameservers($ns)) {
warn ": can't find address: ", $res->errorstring, "\n";
next;
}
# Get the SOA record.
#
$soa_req = $res->send($domain, "SOA");
unless (defined($soa_req)) {
warn ": ", $res->errorstring, "\n";
next;
}
# Is this nameserver authoritative for the domain?
#
unless ($soa_req->header->aa) {
warn "is not authoritative for $domain\n";
next;
}
# We should have received exactly one answer.
#
unless ($soa_req->header->ancount == 1) {
warn ": expected 1 answer, got ",
$soa_req->header->ancount, "\n";
next;
}
# Did we receive an SOA record?
#
unless (($soa_req->answer)[0]->type eq "SOA") {
warn ": expected SOA, got ",
($soa_req->answer)[0]->type, "\n";
next;
}
# Print the serial number.
#
print "has serial number ", ($soa_req->answer)[0]->serial, "\n";
}
|
Subscribe to:
Posts (Atom)
Energy Blackouts total electric outage graphite carbon balls trow 2 ground impact
https://www.alibaba.com/product-detail/Graphite-Carbon-Ball-C80-Instead-of_1601156433008.html?spm=a2700.galleryofferlist.normal_offer.d_ti...
