Hi, I am looking to buy facebook accounts that are aged 1 year or more and have not been used in any advertising campaigns. You either send first or we must use an escrow from the forums. Please post and pm your offers.
I am traveling so I may not respond quickly
|
|
|
I am buying starbucks egift codes at ~20% via btc. You send first or we must use a reputable escrow from the forums. You must guarantee these cards to work for 48hours minimum. Please post and pm your offers.
|
|
|
I am interested in one of these too
|
|
|
Bump. Looking for 200usd or best offer
|
|
|
wow the market for LBC accounts really seem to be picking up! do these accounts really sell for that much??
The spread between the various payment methods makes lbc a nice source of income. The problem is that it is difficult to get established and for a lot of people it is easier to just buy an already established account. This one has no identity or real name attached so it is perfect for that
|
|
|
Bump. Looking for $225 obo
|
|
|
bump. looking for about $250usd
|
|
|
In the third thread you can see that Powerpuff is also selling gmail. But its PVA.
Well I just need accounts,not pva ones The problem is this: Gmail requires phone verification 1 out of 4 times randomly for newly created accounts and guaranteed to want phone verification on the second account created from the same ip. So, even if you switched ip's for every account you create, 25 of them (out of 100) need to be phone verified. the time involved to switch ip's for every account is insane. to start a vm, launch it, and then get to gmail, fill out the form and be done takes about 6 minutes. Add in the phone verification: 8 minutes. I have a ton of gmail accounts and have never had to verify an account with a phone as long as I got the captcha correct the first time
|
|
|
I am looking for 1btc+ and as it stands I have an offer for $150usd
|
|
|
You forgot to mention a key piece of information: what price are you looking for for this account? Also, on a side note, does it matter where the trades are taken place? If your 70+ trades happen in one area, and then the buyer starts trading in a different area, won't it look suspiciously like the account was bought?
I am accepting reasonable offers. The account was initiated in the United States but all trades have been online. I travel a great deal and have accessed my account from the US, Mexico, Panama, and Costa Rica without any issues.
|
|
|
I have an account that is just over 9 months old with 70+ trades(should be hitting 100+ any time), 20+ trusts, 100% feedback and just under 150btc total trade volume. Average seller release times are 0/2min. The identity has not been verified and the real name has not been set so this account is perfect for someone wanting to bypass the initial legwork in getting a good account setup. It shouldn't take long at all for this account to reach protrader status.
Either you send first or we use a reputable escrow from the forums.
Edit Looking for 1btc+ and currently have offers for 150usd.
|
|
|
I have no idea. I thought passkeys (or private keys) were only like 32 digits long. Also, what is with 2 private keys on a wallet? I haven't even heard of this CSI show until now but it seems like they need to hire some actual techies so they don't sound like fools
|
|
|
Here is an awesome ted talk from an accounting professor that offers a different solution. He refers to "money"(where it should be currency) as a "user interface to society". https://www.youtube.com/watch?v=NZBRJU6YLtY
|
|
|
-snip- sudo rm -rf /etc/apache2/sites-enabled/{the weird directory you mentioned}
^ make sure you verify the path. you don't want to accidentally delete the wrong directory. -snip- I highly recommend you to copy all the files in 'sites-enabled' before you try to run the above command. Using -a when running cp command is recommended. if one follows the standards for setting up a vhost in ubuntu there shouldn't be anything in that directory except for symbolic links to config files located in sites-available.
|
|
|
Did you check if there is any typos in site's name in the command?
yes, The ghost file that I found that leads to nowhere did start off 000-www.mysite.conf I tried this aswell but nothing, I cant do anything with this "ghost" file, I cand move/del/edit nothing, I'm stumped. I use filezilla BTW, so I see it as a windows directory would show it, any I run command with putty. That ghost file is a symbolic link to some other file which may or may not exist(im guessing?). Your vhost should be in /etc/apache2/sites-available and the "a2ensite" script simply creates a symbolic link for it in /etc/apache2/sites-enabled. If I were you I would just start over. Here is a step by step command list: remove the current symbolic link sudo unlink /etc/apache2/sites-enabled/{Your old vhost}.conf
or sudo rm -rf /etc/apache2/sites-enabled/{the weird directory you mentioned}
^ make sure you verify the path. you don't want to accidentally delete the wrong directory. copy the default ssl vhost in /etc/apache2/sites-available/default-ssl.conf: sudo cp /etc/apache2/sites-available/default-ssl.conf /etc/apache2/sites-available/001-yourdomain.conf
uncomment/edit the relevant paths in your new 001-yourdomain.conf(DocumentRoot, SSLCertificateFile, SSLCertificateKeyFile, etc) <IfModule mod_ssl.c> <VirtualHost _default_:443> ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
# Available loglevels: trace8, ..., trace1, debug, info, notice, warn, # error, crit, alert, emerg. # It is also possible to configure the loglevel for particular # modules, e.g. #LogLevel info ssl:warn
ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined
# For most configuration files from conf-available/, which are # enabled or disabled at a global level, it is possible to # include a line for only one particular virtual host. For example the # following line enables the CGI configuration for this host only # after it has been globally disabled with "a2disconf". #Include conf-available/serve-cgi-bin.conf
# SSL Engine Switch: # Enable/Disable SSL for this virtual host. SSLEngine on
# A self-signed (snakeoil) certificate can be created by installing # the ssl-cert package. See # /usr/share/doc/apache2/README.Debian.gz for more info. # If both key and certificate are stored in the same file, only the # SSLCertificateFile directive is needed. SSLCertificateFile /etc/ssl/certs/ssl-cert-snakeoil.pem SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key
# Server Certificate Chain: # Point SSLCertificateChainFile at a file containing the # concatenation of PEM encoded CA certificates which form the # certificate chain for the server certificate. Alternatively # the referenced file can be the same as SSLCertificateFile # when the CA certificates are directly appended to the server # certificate for convinience. #SSLCertificateChainFile /etc/apache2/ssl.crt/server-ca.crt
# Certificate Authority (CA): # Set the CA certificate verification path where to find CA # certificates for client authentication or alternatively one # huge file containing all of them (file must be PEM encoded) # Note: Inside SSLCACertificatePath you need hash symlinks # to point to the certificate files. Use the provided # Makefile to update the hash symlinks after changes. #SSLCACertificatePath /etc/ssl/certs/ #SSLCACertificateFile /etc/apache2/ssl.crt/ca-bundle.crt
# Certificate Revocation Lists (CRL): # Set the CA revocation path where to find CA CRLs for client # authentication or alternatively one huge file containing all # of them (file must be PEM encoded) # Note: Inside SSLCARevocationPath you need hash symlinks # to point to the certificate files. Use the provided # Makefile to update the hash symlinks after changes. #SSLCARevocationPath /etc/apache2/ssl.crl/ #SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl
# Client Authentication (Type): # Client certificate verification type and depth. Types are # none, optional, require and optional_no_ca. Depth is a # number which specifies how deeply to verify the certificate # issuer chain before deciding the certificate is not valid. #SSLVerifyClient require #SSLVerifyDepth 10
# SSL Engine Options: # Set various options for the SSL engine. # o FakeBasicAuth: # Translate the client X.509 into a Basic Authorisation. This means that # the standard Auth/DBMAuth methods can be used for access control. The # user name is the `one line' version of the client's X.509 certificate. # Note that no password is obtained from the user. Every entry in the user # file needs this password: `xxj31ZMTZzkVA'. # o ExportCertData: # This exports two additional environment variables: SSL_CLIENT_CERT and # SSL_SERVER_CERT. These contain the PEM-encoded certificates of the # server (always existing) and the client (only existing when client # authentication is used). This can be used to import the certificates # into CGI scripts. # o StdEnvVars: # This exports the standard SSL/TLS related `SSL_*' environment variables. # Per default this exportation is switched off for performance reasons, # because the extraction step is an expensive operation and is usually # useless for serving static content. So one usually enables the # exportation for CGI and SSI requests only. # o OptRenegotiate: # This enables optimized SSL connection renegotiation handling when SSL # directives are used in per-directory context. #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire <FilesMatch "\.(cgi|shtml|phtml|php)$"> SSLOptions +StdEnvVars </FilesMatch> <Directory /usr/lib/cgi-bin> SSLOptions +StdEnvVars </Directory>
# SSL Protocol Adjustments: # The safe and default but still SSL/TLS standard compliant shutdown # approach is that mod_ssl sends the close notify alert but doesn't wait for # the close notify alert from client. When you need a different shutdown # approach you can use one of the following variables: # o ssl-unclean-shutdown: # This forces an unclean shutdown when the connection is closed, i.e. no # SSL close notify alert is send or allowed to received. This violates # the SSL/TLS standard but is needed for some brain-dead browsers. Use # this when you receive I/O errors because of the standard approach where # mod_ssl sends the close notify alert. # o ssl-accurate-shutdown: # This forces an accurate shutdown when the connection is closed, i.e. a # SSL close notify alert is send and mod_ssl waits for the close notify # alert of the client. This is 100% SSL/TLS standard compliant, but in # practice often causes hanging connections with brain-dead browsers. Use # this only for browsers where you know that their SSL implementation # works correctly. # Notice: Most problems of broken clients are also related to the HTTP # keep-alive facility, so you usually additionally want to disable # keep-alive for those clients, too. Use variable "nokeepalive" for this. # Similarly, one has to force some clients to use HTTP/1.0 to workaround # their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and # "force-response-1.0" for this. BrowserMatch "MSIE [2-6]" \ nokeepalive ssl-unclean-shutdown \ downgrade-1.0 force-response-1.0 # MSIE 7 and newer should be able to use keepalive BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown
</VirtualHost> </IfModule>
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
3) enable the domain sudo a2ensite 001-yourdomain.conf
I know this is probably like reading greek(assuming you don't read greek ) right now but ubuntu really makes it a breeze to run a basic lamp setup once you figure it out. editif you would like I can walk you through this on a teamviewer session or something.
|
|
|
1) copy the default vhost in /etc/apache2/sites-available/default-ssl.conf: sudo cp /etc/apache2/sites-available/default-ssl.conf /etc/apache2/sites-available/001-yourdomain.conf
2)make the edits mentioned previously by Bitsky - just edit the relevant paths in your new 001-yourdomain.conf 3) enable the domain sudo a2ensite 001-yourdomain.conf
RE: sudo not found Can you post the output of the following?:
|
|
|
I am selling the domain dollartobitcoin.com for 0.05 or best offer. you send first or we must use a reputable escrow from the forums
|
|
|
bump.
I didn't notice his PM for a couple days and now he hasn't responded for 4 days. I still have both of these codes and will use any reputable escrow from the forums.
|
|
|
|