About
Contact
Geekgirl's Plain English Computing
Home
Win 7
pre-7 Windows
Databases
Office Apps
The Net
Networking
Beginners
Bit Bucket
Bose Goes Under
Renaming files and file extensions
Tools and techniques, Windows, Windows 7
It’s easier to change filenames in Vista and Windows 7 than in previous
versions of Windows. All you do is:
Click the file to select it, then click once more. Windows automatically
selects the filename so that anything you type will replace the existing name.
Type the new filename and press Enter. You’re done.
It’s a small change from the previous method, where you had to manually
select the filename before editing, but it saves a lot of time.
To change a whole batch of files at once:
Select each of the files. You can select a group of contiguous files by
click the first one and then Shift+clicking the last one; you can select any
number of files by Ctrl+clicking each file; or to select all files in a
folder, press Ctrl+A.
Press F2. The filename of the last file you clicked will be selected.
Type a new name and press Enter.
Each of the files will be renamed, with sequential numbering used to
distinguish one file from another.
So, for example, if you select three .jpg image files and rename the first
one Dad’s Birthday, you’ll end up with files named
Dad’s Birthday (1).jpg
Dad’s Birthday (2).jpg
Dad’s Birthday (3).jpg
TIP: If you make a mistake when renaming one or more files, simply press
Ctrl+Z while you’re still in the file folder and before you take any other
actions in that folder. Ctrl+Z undoes whatever you did last within a folder.
Unfortunately, this new file renaming method has one drawback: although the
new method makes changing filenames easy, it makes it harder to change the
file extension. The problem is exacerbated by Microsoft’s determination to
hide those file extensions from view.
About filenames
Filenames in Windows consist of two parts, a filename and an extension,
separated by a full stop (a period). The filename is a descriptive label; the
extension indicates the type of file you’re dealing with – JPG for an
image, MP3 for an audio file, DOC or DOCX for Word documents, PDF for an
Adobe Reader file, and so on. You’re free to change filenames as you need,
but you should exercise caution when changing file extensions because Windows
uses the extension to figure out which program should be used to open a file.
First, display file extensions
Microsoft has been hiding file extensions from users in version after version
of Windows. This supposedly makes things less confusing; in fact, it’s a
piece of paternalistic boneheadedness. Being able to see file extensions is a
good thing.
Those extensions tell you the type of file you’re dealing with and which
type of program you’ll need in order to view or edit the file.
The extensions help you distinguish between similarly named files. For
example, if you have an Excel spreadsheet named 4th Quarter Budget and a
PowerPoint presentation also called 4th Quarter Budget, seeing the .xls
extension on the spreadsheet and the .ppt extension on the presentation helps
you see which is which at a glance. Yes, the little file icons help, too, but
those icons aren’t always easily identifiable.
The extensions also help you spot files which may be dangerous to open. A
.vbs extension tells you you’re about to open a Visual Basic script which
will run commands on your computer – one way that malware can strike.
Similarly, seeing the .exe extensions lets you know you’re dealing with a
program. If you receive an attachment in your email and see the .exe
extension, you almost always want to avoid opening it, once again to avoid
malware.
The file extensions can also help you figure out why you can’t view or
edit a file. Not everyone uses the same software nor the same operating
system. If someone sends you a document they created using Pages on an Apple
Mac, there’s a good chance you won’t be able to open that document on your
Windows system; if you can’t see the file’s extension, there’s no way of
knowing it’s a Pages document and thus it’s hard to figure out why you’re
having problems. On the other hand, if you see the .pages file extension you’
ll know immediately you’re dealing with some strange, other worldly animal.
You can then ask your correspondent to save the file in Word or some other
format and resend it.
The file extensions help you recognise which version of a Microsoft
Office document you’re dealing with. Office 2010 saves Word documents as
.docx files, Excel documents as .xlsx files, an so on. In earlier versions of
Office, those extensions were .doc and .xls. The new formats are incompatible
with the old, so if someone sends you a .docx document and all you have is
Word 2003, you won’t be able to open or edit the file. Being able to see the
extension will help you troubleshoot why you’re running into this problem.
With all those reasons why displaying file extensions is a good thing, let’s
look at why hiding them is a good thing:
It makes for less clutter on the screen.
Really, that’s it. Microsoft may think it makes for less confusion, but the
reverse is true.
It’s pretty clear by now that Microsoft is unlikely to see the light and
display file extensions by default in any version of Windows. That doesn’t
matter because you can take charge of the situation yourself and turn
extension display on:
Open any folder window.
Press Alt+T+O (that’s the letter O, not a zero) to open the Folder
Options dialog box.
Click the View tab.
Remove the tick (checkmark) beside ‘Hide extensions for known file types
’ and click OK.
Why change a file extension?
If Windows uses a file’s extension to determine how to open that file, why
would you ever want to change an extension? Wouldn’t that simply confuse
Windows and prevent it from opening the file?
In many cases, that’s true. Most of the time, you’ll want to leave
extensions alone. But there are times when it’s useful to be able to change
those extensions. If you use a text editor to create a web page, you may want
to keep the .txt extension while editing the code but then change the
extension to .html to be able to view the page in a web browser.
Occasionally, you may receive a file which has the wrong extension: a .jpg
image which someone has accidentally named as a .bmp file, for example. If
you try to load a .jpg file into your graphics program and you get an “
invalid file format” or similar message, try changing the extension to .bmp
or .png or .tif or another common graphics file extension, and see if your
graphics editor recognises it.
You may also want to change the case of an extension. Many cameras save image
files with a capitalised extension, such as .JPG. Windows is case-blind when
it comes to filenames, so it doesn’t matter to the operating system whether
a file is called MAGNOLIA.JPG or magnolia.jpg, but it may matter to humans;
after all, using ALL CAPS is the digital equivalent of shouting at someone,
and a folder littered with .JPG images does just that.
How to change a file extension
In Windows 7, to change a file extension, first, make sure file extensions
are visible using the steps above, then:
Click the file to select it, then click once more. Windows automatically
selects the filename so that anything you type will replace the existing name.
Click and drag over the extension, type the new extension and press Enter.
It sounds simple enough, but it turns out to be pretty clumsy, especially if
you’re changing extensions on a bunch of files.
Things get even worse if you want to change capitalised extensions on a group
of files: Windows 7 refuses to do it. For example, if you have three files
named 1.JPG, 2.JPG and 3.JPG, if you select all the files and rename the
first one platypus.jpg, you’ll end up with platypus (1).JPG, platypus
(2).JPG and platypus (3).JPG. The extension pigheadedly maintains its
uppercase lettering. If you want to change those extensions, you have to
rename each file one by one.
Using Bulk Rename Utility to change file extensionsA better way to change
filenames and extensions
If you need to do some serious file renaming – perhaps you have folders
stuffed with horribly named photos – try a bulk file renaming utility. There
’s one called Bulk Rename Utility that’s free to use. It looks pretty
ferocious when you open it up, but don’t worry – although it has enormous
power and flexibility, it makes very light work out of actions such as
changing the case of a bunch of file extensions. If you want a less
intimidating renamer, Better File Rename does the trick, but it’ll set you
back $US19.95.
Here’s how you change the case of all files in a folder using Bulk Rename
Utility:
Open the folder containing the files.
Right-click any file in the folder and choose Bulk Rename Here from the
context menu. The utility will load all the files into its main window, with
a folder tree displayed on the left allowing you to navigate to any other
folder, and a mind-numbing array of options displayed below.
Press Ctrl+A to select all the files in the folder.
Down near the bottom right of the window you’ll see Extension. Select
Lower from the Extension drop-down box. You’ll see the filenames updated in
the New Name column. This is a preview to let you check whether the changes
you’re making are correct.
If you’re satisfied with the displayed changes, click the Rename button
in the bottom right to rename the selected files.
A quick look at Bulk Rename’s other options gives you an idea of the power
of the program. You can even save renaming schemes so that you can reapply
them to other batches of files.
TIP: If you rename a bunch of files using Bulk Rename and the changes don
’t immediately appear within explorer, press F5 to refresh the view of the
window.
All content copyright 2017 by Rose Vines and Geekgirl's Plain English
Computing.
作者 eeeabd () 看板 Test
標題 R
時間 Tue Jan 1 06:17:03 2019
───────────────────────────────────────
--
※ 發信站: 批踢踢實業坊(ptt.cc), 來自: 59.102.169.115
※ 文章網址: https://www.ptt.cc/bbs/Test/M.1546294625.A.AD7.html
16 ~ 23 多雲
17 ~ 21 多雲
16 ~ 23 多雲時晴
17 ~ 23
晚上 多雲時晴
16 ~ 20 陰時多雲短暫雨
17 ~ 19 多雲時晴
16 ~ 18 多雲時陰
17 ~ 20 多雲時晴
16 ~ 18 多雲
17 ~ 19 晴時多雲
※ 編輯: eeeabd (59.102.169.115), 01/04/2019 18:57:10
J
───────────────────────────────────────
1.媒體來源:蘋果日報
2.完整新聞標題:一拖再拖！高志鵬又放檢方鴿子 稱下周二入監
3.完整新聞內文:
民進黨籍立委高志鵬被控利用職權向台中市國產局關說，
藉此向業者收賄50萬元，被依圖利罪判處4年6月定讞，
檢方原傳喚高本月4日報到入監，但他卻突聲請非常上訴要求暫緩執行，
遭檢方駁回後，發監當天神隱未現身。
新北地檢署緊急再發傳票，要求高今天上午10時到案，
否則將拘提，但高又出招，前兩天向北檢二度遞出親筆簽名函聲請暫緩執行，
陳報另一個居住地址，表明下周二才要向北檢報到。
大批媒體今早守候在新北地檢署外，但高志鵬果然沒現身。
新北地檢署檢察官緊急透過調查官聯繫上高志鵬，
希望他今天前來新北地檢署報到，不要再拖延，但高「沒有答覆」。
曾任3屆立委的高志鵬（55歲）2007年間捲入貪污案被查辦，
當時台中有一筆「國有非公用市場用地」，東豐閣公司負責人謝聰烽想取得土地，
因不符承租規定被打槍，於是透過高的助理姚昇志（已改名姚糧鈿）牽線，
拜託高幫忙。高邀約時任國產局局長郭武博等人到立院辦公室關說，
國產局因而函示中區辦事處改為同意東豐閣承租用地，並行賄高50萬
元。最高法院上月依圖利罪判高4年6月定讞，高隨即喪失立委身分。
由於高志鵬戶籍在新北市三重區，
起訴本案的南投地檢署因而囑託新北地檢署代執行發監事宜，
但高志鵬以住居所是立法院辦公室，聲請改到台北地檢署報到，
經檢方協調後，決定改由北檢負責發監作業。
北檢原傳喚高1月4日到案執行，但高志鵬搶先在前1天出招，
以自己要聲請非常上訴討公道、立委事務尚未交接完畢等理由，
向南投地檢署聲請暫緩執行，但南投地檢署收到聲請狀後，
要求高先到北檢報到再決定是否讓他暫緩入監，高卻神隱沒現身，
大批媒體守候一整天均撲空。
由於高志鵬已失去立委身分，住居所已不在北檢轄區的立法院，
北檢無法發拘票拘提他，新北檢得知後緊急接手，
發出傳票交由調查官親送到高的三重住居所，要求高今天上午10時報到入監。
但高志鵬日前又出招，再向北檢二度聲請暫緩執行，
還呈報一個新的台北市居住地址，暫緩執行的理由是有同事要資遣，
有職務要交接。北檢因第一次執行無著，已把卷宗交還南投地檢署，
因此日前收到高二度聲請暫緩執行的資料已轉達南投地檢，
由南投地檢署決定是否同意。（呂志明、吳珮如／台北報導）
4.完整新聞連結 (或短網址):
https://tw.news.appledaily.com/local/realtime/20190110/1498059/
5.備註:
國民黨不意外....唉?
--
可怕的眼神
https://i.imgur.com/wkAsvHP.jpg
--
※ 發信站: 批踢踢實業坊(ptt.cc), 來自: 114.36.183.225
───────────────────────────────────────
北市各局處爆退訂報潮 柯P：全面E化是方向和目標
〔記者沈佩瑤／台北報導〕台北市長柯文哲前天在市政會議上，要求各局處及其附屬機關
「全面檢討」訂閱實體報章雜誌的需求，隨即爆出各局處退訂潮。對此，柯文哲今早受訪
解釋，全面E化是北市府目標，會降低紙本的東西，北市府會再調整、盤整一遍，全面E化
是方向和目標。
此外，柯文哲今早三度親自出席行政院會，談到是否會和中央反映任何事宜？柯說不會，
自己通常只會安安靜靜地看而已，因為少了一個副市長，所以現在有時候就自己去，反正
就是一天24小時把它塞滿，也可以順便聽聽他們（行政院）在幹什麼！
由於賴清德傳出即將卸任，媒體也追問柯是否會給予祝福？柯說「你也不要這樣…人家還
沒宣布你就這樣...」
http://m.ltn.com.tw/news/life/breakingnews/2667360
廠工：不管啦噓爆你
--
※ 發信站: 批踢踢實業坊(ptt.cc), 來自: 223.141.159.173
───────────────────────────────────────
1.媒體來源:
※ 例如蘋果日報、奇摩新聞
東森財金
2.完整新聞標題:
※ 標題沒有寫出來 ---> 依照板規刪除文章
劫富濟貧？5年超徵6千億！400億紅包全靠2大稅收
3.完整新聞內文:
※ 社論特稿都不能貼! 違者刪除(政治類水桶3個月)，貼廣告也會被刪除喔!
對於蔡政府近日拋出規劃發給經濟弱勢族群「大紅包」的消息，引起不少企業界投反對票
。商總理事長賴正鎰指出，「超徵稅收結餘400億元不應該這樣花，這不但對於繳稅的人
不公平，而且也無法達到刺激經濟消費的循環效果」。並強調「應該要用多出來的稅收養
一隻會下蛋的雞，與其撒錢看不到一點效益，不如減稅讓大家有餘力投資，才能挹注經濟
活水」。
不過，究竟400億「大紅包」的超徵稅收從何而來？主要還是以「企業營所稅」和「個人
綜所稅」為兩大來源。財政部統計處長蔡美娜表示，2014年至2017年稅收超徵累計金額已
達5204億元，若再加計2018年稅收將連續5年超徵。並且，若以稅收細目來看，蔡美娜說
，2014年稅收超徵1088億元，主要是營業稅及綜所稅增加所致，而其中的營業稅是因銀行
保險業營業稅調高；2015年稅收超徵1878億元，增加較多的稅目是綜所稅及營所稅。
至於2016年稅收更超徵1278億元，而增加較多的稅目除了營所稅、綜所稅以外，就以公告
地價調漲使得地價稅增加，還有贈與稅增加，主要都是因應稅率可能要調整，有些提前規
畫動作已出現。另外，2017年稅收也超徵960億元，同樣也是受到贈與稅及營所稅超徵的
影響。
此外，根據財政部統計處副處長陳玉豐先前的保守估計，也表示2018年稅收超徵600億元
「沒有問題」，主要是經濟穩定成長、上市櫃公司獲利成長及台股活絡，因此稅收才會超
乎預期。
另外，蔡英文總統也在元旦談話時提到，「今年5月報稅，國人同胞會發現有4項綜所稅扣
除額提高了，月薪3萬元以下的朋友，基本上不用再繳所得稅，大家會感受到，政府真的
很努力在幫大家省荷包」。另外，蔡總統還強調，除了加薪和減稅政策以外，今年更要進
一步減輕民眾的負擔，過去兩年經濟有成長，稅收也超出預期，她已請行政院盡快提出具
體方案，讓收入較少的民眾，能夠優先分享經濟成長的紅利，並表示「這就像公司有盈餘
，就應該優先給員工來分享，一個國家也應該如此」。
然而，對於政府將採「還稅於民」的政策，引發外界出現「劫富濟貧」的質疑聲浪，前行
政院長陳冲也在日前針對稅收超徵與財政盈餘發表最新看法。他表示，對政府要建立「還
稅於民」制度表達肯定，但在中央政府公共債務仍有5兆3千億時，並非是「還稅於民」的
政策時機。此外，陳冲也指出，政府首先應釐清「稅收超徵」與「財政盈餘」，政府稅收
超徵僅僅是表達實際徵稅金額超出年度預算，並不表示國庫目前有盈餘。
而另一方面，長年呼籲政府減稅的財信傳媒董事長謝金河則採支持的態度，並以美國總統
川普上任後力推減稅政策為例。根據UBS（瑞銀集團）統計，川普減稅政策上路不到半年
，就替美國帶來約2.5兆美元（約新台幣77.1兆元）的資金回流，比預期還大很多，而這
可能就是2018年美股強勢的動力。
此外，2018年第2季時，當台灣正在為GDP（經濟成長率）是否如預期而忐忑不安時，美國
的經濟成長率竟然開出有4.2%，使得川普龍心大悅，並認為經濟成長的主因就是來自於減
稅。因此，謝金河也強調，這個結果相當值得小英政府借鏡，並直言「台灣稅率何德何能
可比美國高？」
4.完整新聞連結 (或短網址):
※ 當新聞連結過長時，需提供短網址方便網友點擊
https://fnc.ebc.net.tw/FncNews/life/65926
5.備註:
※ 一個人一天只能張貼一則新聞，被刪或自刪也算額度內，超貼者水桶，請注意
綠色支持者忽略馬英九賺更多稅收
原來每年都超徵稅阿
--
※ 發信站: 批踢踢實業坊(ptt.cc), 來自: 223.137.100.192
[m───────────────────────────────────────
[m1.媒體來源:蘋果日報
[m2.完整新聞標題:一拖再拖！高志鵬又放檢方鴿子 稱下周二入監
[m3.完整新聞內文:
[m民進黨籍立委高志鵬被控利用職權向台中市國產局關說，
[m藉此向業者收賄50萬元，被依圖利罪判處4年6月定讞，
[m檢方原傳喚高本月4日報到入監，但他卻突聲請非常上訴要求暫緩執行，
[m遭檢方駁回後，發監當天神隱未現身。
[m新北地檢署緊急再發傳票，要求高今天上午10時到案，
[m否則將拘提，但高又出招，前兩天向北檢二度遞出親筆簽名函聲請暫緩執行，
[m陳報另一個居住地址，表明下周二才要向北檢報到。
[m大批媒體今早守候在新北地檢署外，但高志鵬果然沒現身。
[m新北地檢署檢察官緊急透過調查官聯繫上高志鵬，
[m希望他今天前來新北地檢署報到，不要再拖延，但高「沒有答覆」。
[m曾任3屆立委的高志鵬（55歲）2007年間捲入貪污案被查辦，
[m當時台中有一筆「國有非公用市場用地」，東豐閣公司負責人謝聰烽想取得土地，
[m因不符承租規定被打槍，於是透過高的助理姚昇志（已改名姚糧鈿）牽線，
[m拜託高幫忙。高邀約時任國產局局長郭武博等人到立院辦公室關說，
[m國產局因而函示中區辦事處改為同意東豐閣承租用地，並行賄高50萬
[m元。最高法院上月依圖利罪判高4年6月定讞，高隨即喪失立委身分。
[m由於高志鵬戶籍在新北市三重區，
[m起訴本案的南投地檢署因而囑託新北地檢署代執行發監事宜，
[m但高志鵬以住居所是立法院辦公室，聲請改到台北地檢署報到，
[m經檢方協調後，決定改由北檢負責發監作業。
[m北檢原傳喚高1月4日到案執行，但高志鵬搶先在前1天出招，
[m以自己要聲請非常上訴討公道、立委事務尚未交接完畢等理由，
[m向南投地檢署聲請暫緩執行，但南投地檢署收到聲請狀後，
[m要求高先到北檢報到再決定是否讓他暫緩入監，高卻神隱沒現身，
[m大批媒體守候一整天均撲空。
[m由於高志鵬已失去立委身分，住居所已不在北檢轄區的立法院，
[m北檢無法發拘票拘提他，新北檢得知後緊急接手，
[m發出傳票交由調查官親送到高的三重住居所，要求高今天上午10時報到入監。
[m但高志鵬日前又出招，再向北檢二度聲請暫緩執行，
[m還呈報一個新的台北市居住地址，暫緩執行的理由是有同事要資遣，
[m有職務要交接。北檢因第一次執行無著，已把卷宗交還南投地檢署，
[m因此日前收到高二度聲請暫緩執行的資料已轉達南投地檢，
[m由南投地檢署決定是否同意。（呂志明、吳珮如／台北報導）
[m4.完整新聞連結 (或短網址):
[mhttps://tw.news.appledaily.com/local/realtime/20190110/1498059/
[m5.備註:
[m國民黨不意外....唉?
[m--
[m可怕的眼神
[mhttps://i.imgur.com/wkAsvHP.jpg
[m--
[m※ 發信站: 批踢踢實業坊(ptt.cc), 來自: 114.36.183.225
[m───────────────────────────────────────
[m北市各局處爆退訂報潮 柯P：全面E化是方向和目標
[m〔記者沈佩瑤／台北報導〕台北市長柯文哲前天在市政會議上，要求各局處及其附屬機關
[m「全面檢討」訂閱實體報章雜誌的需求，隨即爆出各局處退訂潮。對此，柯文哲今早受訪
[m解釋，全面E化是北市府目標，會降低紙本的東西，北市府會再調整、盤整一遍，全面E化
[m是方向和目標。
[m此外，柯文哲今早三度親自出席行政院會，談到是否會和中央反映任何事宜？柯說不會，
[m自己通常只會安安靜靜地看而已，因為少了一個副市長，所以現在有時候就自己去，反正
[m就是一天24小時把它塞滿，也可以順便聽聽他們（行政院）在幹什麼！
[m由於賴清德傳出即將卸任，媒體也追問柯是否會給予祝福？柯說「你也不要這樣…人家還
[m沒宣布你就這樣...」
[mhttp://m.ltn.com.tw/news/life/breakingnews/2667360
[m廠工：不管啦噓爆你
[m--
[m※ 發信站: 批踢踢實業坊(ptt.cc), 來自: 223.141.159.173
[m───────────────────────────────────────
[m1.媒體來源:
[m※ 例如蘋果日報、奇摩新聞
[m東森財金
[m2.完整新聞標題:
[m※ 標題沒有寫出來 ---> 依照板規刪除文章
[m劫富濟貧？5年超徵6千億！400億紅包全靠2大稅收
[m3.完整新聞內文:
[m※ 社論特稿都不能貼! 違者刪除(政治類水桶3個月)，貼廣告也會被刪除喔!
[m對於蔡政府近日拋出規劃發給經濟弱勢族群「大紅包」的消息，引起不少企業界投反對票
[m。商總理事長賴正鎰指出，「超徵稅收結餘400億元不應該這樣花，這不但對於繳稅的人
[m不公平，而且也無法達到刺激經濟消費的循環效果」。並強調「應該要用多出來的稅收養
[m一隻會下蛋的雞，與其撒錢看不到一點效益，不如減稅讓大家有餘力投資，才能挹注經濟
[m活水」。
[m不過，究竟400億「大紅包」的超徵稅收從何而來？主要還是以「企業營所稅」和「個人
[m綜所稅」為兩大來源。財政部統計處長蔡美娜表示，2014年至2017年稅收超徵累計金額已
[m達5204億元，若再加計2018年稅收將連續5年超徵。並且，若以稅收細目來看，蔡美娜說
[m，2014年稅收超徵1088億元，主要是營業稅及綜所稅增加所致，而其中的營業稅是因銀
[m保險業營業稅調高；2015年稅收超徵1878億元，增加較多的稅目是綜所稅及營所稅。
[m至於2016年稅收更超徵1278億元，而增加較多的稅目除了營所稅、綜所稅以外，就以公
[m地價調漲使得地價稅增加，還有贈與稅增加，主要都是因應稅率可能要調整，有些提前規
[m畫動作已出現。另外，2017年稅收也超徵960億元，同樣也是受到贈與稅及營所稅超徵
[m影響。
[m此外，根據財政部統計處副處長陳玉豐先前的保守估計，也表示2018年稅收超徵600億元
[m「沒有問題」，主要是經濟穩定成長、上市櫃公司獲利成長及台股活絡，因此稅收才會超
[m乎預期。
[m另外，蔡英文總統也在元旦談話時提到，「今年5月報稅，國人同胞會發現有4項綜所稅扣
[m除額提高了，月薪3萬元以下的朋友，基本上不用再繳所得稅，大家會感受到，政府真的
[m很努力在幫大家省荷包」。另外，蔡總統還強調，除了加薪和減稅政策以外，今年更要進
[m一步減輕民眾的負擔，過去兩年經濟有成長，稅收也超出預期，她已請行政院盡快提出具
[m體方案，讓收入較少的民眾，能夠優先分享經濟成長的紅利，並表示「這就像公司有盈餘
[m，就應該優先給員工來分享，一個國家也應該如此」。
[m然而，對於政府將採「還稅於民」的政策，引發外界出現「劫富濟貧」的質疑聲浪，前行
[m政院長陳冲也在日前針對稅收超徵與財政盈餘發表最新看法。他表示，對政府要建立「還
[m稅於民」制度表達肯定，但在中央政府公共債務仍有5兆3千億時，並非是「還稅於民」的
[m政策時機。此外，陳冲也指出，政府首先應釐清「稅收超徵」與「財政盈餘」，政府稅收
[m超徵僅僅是表達實際徵稅金額超出年度預算，並不表示國庫目前有盈餘。
[m而另一方面，長年呼籲政府減稅的財信傳媒董事長謝金河則採支持的態度，並以美國總統
[m川普上任後力推減稅政策為例。根據UBS（瑞銀集團）統計，川普減稅政策上路不到半年
[m，就替美國帶來約2.5兆美元（約新台幣77.1兆元）的資金回流，比預期還大很多，而這
[m可能就是2018年美股強勢的動力。
[m此外，2018年第2季時，當台灣正在為GDP（經濟成長率）是否如預期而忐忑不安時，美國
[m的經濟成長率竟然開出有4.2%，使得川普龍心大悅，並認為經濟成長的主因就是來自於減
[m稅。因此，謝金河也強調，這個結果相當值得小英政府借鏡，並直言「台灣稅率何德何能
[m可比美國高？」
[m4.完整新聞連結 (或短網址):
[m※ 當新聞連結過長時，需提供短網址方便網友點擊
[mhttps://fnc.ebc.net.tw/FncNews/life/65926
[m5.備註:
[m※ 一個人一天只能張貼一則新聞，被刪或自刪也算額度內，超貼者水桶
[m綠色支持者忽略馬英九賺更多稅收
[m原來每年都超徵稅阿
[m--
[m※ 發信站: 批踢踢實業坊(ptt.cc), 來自: 223.137.100.192
作者 dean1990 (狄恩院長) 看板 Gossiping
時間 Thu Jan 10 09:53:28 2019
───────────────────────────────────────
自己回
認同有些人覺得酒好喝這件事很不可思議
我自己以前也是如此
但有次喝了一瓶甜白酒後
一去不復返
越喝越入迷
現在只要有機會
每週都會品飲一瓶
不是要消愁練酒或因為應酬而喝
而是真的覺得好喝與有趣
有趣的是原料就是葡萄
但釀成酒後卻能有極為豐富的味覺與香氣
想強調的是
我會喝酒 我喜歡喝酒 而且還真的喝了不少
可是 我絕對禁止自己喝酒後開車
縱使只是去店裡品飲一口濃度20%以下的
我也絕對不敢開車
這是原則問題
我寧可花幾百塊坐計程車回家
隔天再花幾百塊做計程車回去拿車
我也不願意冒著那點風險
可能讓自己名譽掃地的風險
可能讓別人家破人亡的風險
而酒後駕車
這不只是對自己負責
也是對別人負責
要喝酒
就要有最起碼的責任感
否則你根本沒資格喝酒
能喝酒的人
好說也活了十幾年了
卻還不能有這種最基本的認知
我真的是為那些人感到極度悲哀
也為那些人的不負責任感到憤慨
唉
真的希望酒駕垃圾能少一點
能不能有一年完全不要發生酒駕事故
沒有家庭需要為酒駕而痛失親友 悲傷一世
--
※ 發信站: 批踢踢實業坊(ptt.cc), 來自: 42.73.255.154
時間 Tue Jan 1 06:17:03 2019
───────────────────────────────────────
--
※ 發信站: 批踢踢實業坊(ptt.cc), 來自: 59.102.169.115
時間: Tue Mar 20 16:58:54 2018
1.媒體來源:
※ 例如蘋果日報、奇摩新聞
中時
2.完整新聞標題:
※ 標題沒有寫出來 ---> 依照板規刪除文章
被當洩慾工具累了！男求分遭學妹告性侵
3.完整新聞內文:
※ 社論特稿都不能貼! 違者刪除(政治類水桶3個月)，貼廣告也會被刪除喔!
2018年03月20日 11:21亢伄q子報
張國欽
不想被當炮友也被告性侵！台北市有一名黃姓男子的大學直屬學妹有男朋友，還是與他有
曖昧，且見面後都會到上床，因不想再被當成洩慾工具，竟被學妹指控性侵。
不過，台北地檢署調查發現，學妹不但在LINE傳訊息與黃男打情罵俏，甚至傳裸照給他，
雖不是戀人，但早已是「炮友當好當滿」的關係，認定強制性交罪證不足，將黃男不起訴
處分。
據悉，黃男對自己被學妹當作是洩慾工具已感到疲累，某次與學妹激情過後，對她提出「
忘掉我吧」的要求，沒想到學妹竟然激動地說「為什麼每次做完都說不再見面」，不久黃
男就被告。
學妹指控黃男2015年害她懷孕、墮胎，2016年7月和2017年9月，分別在黃男住家頂樓及樓
梯間對性侵，但遭被黃男反駁，並且強調都是你情我願。
檢察官調查發現，學妹在2015年確實有到婦產科墮胎的證明，但這無法當作是2016、2017
年性侵的事證。此外，若學妹真在2016年被學長性侵，2017年為何還要和他出遊，加上學
妹在去年約3、4月和黃男發生關係後，還傳LINE訊息「你想要愛愛喔」、「你雞雞太小」
等打情罵俏的文字，甚至還傳裸照，顯見兩人關係匪淺，檢察官認為沒有足夠的跡證可以
證明黃男對學妹強制性交，因此將他不起訴。
(中時電子報)
4.完整新聞連結 (或短網址):
※ 當新聞連結過長時，需提供短網址方便網友點擊
http://www.chinatimes.com/realtimenews/20180320001787-260402
人帥？
--
※ 發信站: 批踢踢實業坊(ptt.cc), 來自: 111.82.97.191
※ 編輯: eeeabd (59.102.169.115), 01/10/2019 10:18:31
作者 dean1990 (狄恩院長) 看板 Gossiping
時間 Thu Jan 10 09:53:28 2019
───────────────────────────────────────
自己回
認同有些人覺得酒好喝這件事很不可思議
我自己以前也是如此
但有次喝了一瓶甜白酒後
一去不復返
越喝越入迷
現在只要有機會
每週都會品飲一瓶
不是要消愁練酒或因為應酬而喝
而是真的覺得好喝與有趣
有趣的是原料就是葡萄
但釀成酒後卻能有極為豐富的味覺與香氣
想強調的是
我會喝酒 我喜歡喝酒 而且還真的喝了不少
可是 我絕對禁止自己喝酒後開車
縱使只是去店裡品飲一口濃度20%以下的
我也絕對不敢開車
這是原則問題
我寧可花幾百塊坐計程車回家
隔天再花幾百塊做計程車回去拿車
我也不願意冒著那點風險
可能讓自己名譽掃地的風險
可能讓別人家破人亡的風險
而酒後駕車
這不只是對自己負責
也是對別人負責
要喝酒
就要有最起碼的責任感
否則你根本沒資格喝酒
能喝酒的人
好說也活了十幾年了
卻還不能有這種最基本的認知
我真的是為那些人感到極度悲哀
也為那些人的不負責任感到憤慨
唉
真的希望酒駕垃圾能少一點
能不能有一年完全不要發生酒駕事故
沒有家庭需要為酒駕而痛失親友 悲傷一世
--
※ 發信站: 批踢踢實業坊(ptt.cc), 來自: 42.73.255.154
時間 Tue Jan 1 06:17:03 2019
───────────────────────────────────────
--
※ 發信站: 批踢踢實業坊(ptt.cc), 來自: 59.102.169.115
時間: Tue Mar 20 16:58:54 2018
1.媒體來源:
※ 例如蘋果日報、奇摩新聞
中時
2.完整新聞標題:
※ 標題沒有寫出來 ---> 依照板規刪除文章
被當洩慾工具累了！男求分遭學妹告性侵
3.完整新聞內文:
※ 社論特稿都不能貼! 違者刪除(政治類水桶3個月)，貼廣告也會被刪除喔!
2018年03月20日 11:21亢伄q子報
張國欽
不想被當炮友也被告性侵！台北市有一名黃姓男子的大學直屬學妹有男朋友，還是與他有
曖昧，且見面後都會到上床，因不想再被當成洩慾工具，竟被學妹指控性侵。
不過，台北地檢署調查發現，學妹不但在LINE傳訊息與黃男打情罵俏，甚至傳裸照給他，
※ 引述《a3300552 (EYE)》之銘言：
: 男生 29y
: 學歷:前面大學+碩士 電機畢業
: 工作:普通無壓力的電機工程師
: 薪水:80~85萬/year
: 動產:車子(90萬的車子)
: 身高:177cm
: 體重:88kg
: 外貌:像吳孟達+頭髮開始慢慢往上禿
: 這樣子的外在條件真的很難找到的到女朋友嗎?
: 我希望找學歷至少國立碩士+薪水50萬以上+身高160cm以上體重55kg以內+27y以內
: 2018找了半年 只遇到三個有興趣的 不過都感覺被打槍.......
: 是不是我很沒競爭優勢呢?
雖不是戀人，但早已是「炮友當好當滿」的關係，認定強制性交罪證不足，將黃男不起訴
處分。
據悉，黃男對自己被學妹當作是洩慾工具已感到疲累，某次與學妹激情過後，對她提出「
忘掉我吧」的要求，沒想到學妹竟然激動地說「為什麼每次做完都說不再見面」，不久黃
男就被告。
學妹指控黃男2015年害她懷孕、墮胎，2016年7月和2017年9月，分別在黃男住家頂樓及樓
梯間對性侵，但遭被黃男反駁，並且強調都是你情我願。
檢察官調查發現，學妹在2015年確實有到婦產科墮胎的證明，但這無法當作是2016、2017
年性侵的事證。此外，若學妹真在2016年被學長性侵，2017年為何還要和他出遊，加上學
妹在去年約3、4月和黃男發生關係後，還傳LINE訊息「你想要愛愛喔」、「你雞雞太小」
等打情罵俏的文字，甚至還傳裸照，顯見兩人關係匪淺，檢察官認為沒有足夠的跡證可以
證明黃男對學妹強制性交，因此將他不起訴。
(中時電子報)
4.完整新聞連結 (或短網址):
※ 當新聞連結過長時，需提供短網址方便網友點擊
http://www.chinatimes.com/realtimenews/20180320001787-260402
人帥？
--
※ 發信站: 批踢踢實業坊(ptt.cc), 來自: 111.82.97.191
※ 編輯: eeeabd (59.102.169.115), 01/10/2019 10:18:31
※ 編輯: eeeabd (59.102.169.115), 01/10/2019 10:31:08
※ 編輯: eeeabd (59.102.169.115), 01/10/2019 11:41:20
: https://www.ptt.cc/bbs/Test/M.1546926959.A.F29.html
CCSCCCCCVBVVDDCCVNNNGCC4456BBBN
VV
CCC
CVVVVFFFEECCC
CVB
VDDD
CCDD
VVVVCCCVVVVVVDDCVDDCCCCCCCCSS
VVV BBBBBBB
BBBBB
CCSCCCCCVBVVDDCCVNNNGCC4456BBBN
VV
CCC
CVVVVFFFEECCC
CVB
VDDD
CCDD
VVVVCCCVVVVVVDDCVDDCCCCCCCCSS
VVV BBBBBBB
BBBBB
UUUU
File Transfer Protocol
From Wikipedia, the free encyclopedia
Jump to navigation
Jump to search
"FTP" redirects here. For other uses, see FTP (disambiguation).
Internet protocol suite
Application layer
BGP DHCP DNS FTP HTTP HTTPS IMAP LDAP MGCP MQTT NNTP NTP POP ONC/RPC RTP
RTSP RIP SIP SMTP SNMP SSH Telnet TLS/SSL XMPP more...
Transport layer
TCP QUIC UDP DCCP SCTP RSVP more...
Internet layer
IP
IPv4 IPv6 ICMP ICMPv6 ECN IGMP IPsec more...
Link layer
ARP NDP OSPF Tunnels
L2TP PPP MAC
Ethernet DSL ISDN FDDI more...
vte
The File Transfer Protocol (FTP) is a standard network protocol used for the
transfer of computer files between a client and server on a computer network.
FTP is built on a client-server model architecture using separate control and
data connections between the client and the server.[1] FTP users may
authenticate themselves with a clear-text sign-in protocol, normally in the
form of a username and password, but can connect anonymously if the server is
configured to allow it. For secure transmission that protects the username
and password, and encrypts the content, FTP is often secured with SSL/TLS
(FTPS) or replaced with SSH File Transfer Protocol (SFTP).
The first FTP client applications were command-line programs developed before
operating systems had graphical user interfaces, and are still shipped with
most Windows, Unix, and Linux operating systems.[2][3] Many FTP clients and
automation utilities have since been developed for desktops, servers, mobile
devices, and hardware, and FTP has been incorporated into productivity
applications, such as HTML editors.
Contents
1 History of FTP servers
2 Protocol overview
2.1 Communication and data transfer
2.2 Login
2.3 Anonymous FTP
2.4 NAT and firewall traversal
2.5 Differences from HTTP
3 Web browser support
3.1 Syntax
4 Security
4.1 FTP over SSH
5 Derivatives
5.1 FTPS
5.2 SSH File Transfer Protocol
5.3 Trivial File Transfer Protocol
5.4 Simple File Transfer Protocol
6 FTP commands
7 FTP reply codes
8 FTP servers
9 See also
10 References
11 Further reading
12 External links
History of FTP servers
The original specification for the File Transfer Protocol was written by
Abhay Bhushan and published as RFC 114 on 16 April 1971. Until 1980, FTP ran
on NCP, the predecessor of TCP/IP.[2] The protocol was later replaced by a
TCP/IP version, RFC 765 (June 1980) and RFC 959 (October 1985), the current
specification. Several proposed standards amend RFC 959, for example RFC 1579
(February 1994) enables Firewall-Friendly FTP (passive mode), RFC 2228 (June
1997) proposes security extensions, RFC 2428 (September 1998) adds support
for IPv6 and defines a new type of passive mode.[4]
Protocol overview
Communication and data transfer
Illustration of starting a passive connection using port 21
FTP may run in active or passive mode, which determines how the data
connection is established.[5] In both cases, the client creates a TCP control
connection from a random, usually an unprivileged, port N to the FTP server
command port 21.
In active mode, the client starts listening for incoming data connections
from the server on port M. It sends the FTP command PORT M to inform the
server on which port it is listening. The server then initiates a data
channel to the client from its port 20, the FTP server data port.
In situations where the client is behind a firewall and unable to accept
incoming TCP connections, passive mode may be used. In this mode, the client
uses the control connection to send a PASV command to the server and then
receives a server IP address and server port number from the server,[5] which
the client then uses to open a data connection from an arbitrary client port
to the server IP address and server port number received.[6]
Both modes were updated in September 1998 to support IPv6. Further changes
were introduced to the passive mode at that time, updating it to extended
passive mode.[7]
The server responds over the control connection with three-digit status codes
in ASCII with an optional text message. For example, "200" (or "200 OK")
means that the last command was successful. The numbers represent the code
for the response and the optional text represents a human-readable
explanation or request (e.g. <Need account for storing file>).[1] An ongoing
transfer of file data over the data connection can be aborted using an
interrupt message sent over the control connection.
While transferring data over the network, four data representations can be
used:[2][3][4]
ASCII mode: Used for text. Data is converted, if needed, from the sending
host's character representation to "8-bit ASCII" before transmission, and
(again, if necessary) to the receiving host's character representation. As a
consequence, this mode is inappropriate for files that contain data other
than plain text.
Image mode (commonly called Binary mode): The sending machine sends each
file byte by byte, and the recipient stores the bytestream as it receives it.
(Image mode support has been recommended for all implementations of FTP).
EBCDIC mode: Used for plain text between hosts using the EBCDIC character
set.
Local mode: Allows two computers with identical setups to send data in a
proprietary format without the need to convert it to ASCII.
For text files, different format control and record structure options are
provided. These features were designed to facilitate files containing Telnet
or ASA.
Data transfer can be done in any of three modes:[1][2]
Stream mode: Data is sent as a continuous stream, relieving FTP from
doing any processing. Rather, all processing is left up to TCP. No
End-of-file indicator is needed, unless the data is divided into records.
Block mode: FTP breaks the data into several blocks (block header, byte
count, and data field) and then passes it on to TCP.[4]
Compressed mode: Data is compressed using a simple algorithm (usually
run-length encoding).
Some FTP software also implements a DEFLATE-based compressed mode, sometimes
called "Mode Z" after the command that enables it. This mode was described in
an Internet Draft, but not standardized.[8]
Login
FTP login uses normal username and password scheme for granting access.[2]
The username is sent to the server using the USER command, and the password
is sent using the PASS command.[2] This sequence is unencrypted "on the
wire", so may be vulnerable to a network sniffing attack.[9] If the
information provided by the client is accepted by the server, the server will
send a greeting to the client and the session will commence.[2] If the server
supports it, users may log in without providing login credentials, but the
same server may authorize only limited access for such sessions.[2]
Anonymous FTP
A host that provides an FTP service may provide anonymous FTP access.[2]
Users typically log into the service with an 'anonymous' (lower-case and
case-sensitive in some FTP servers) account when prompted for user name.
Although users are commonly asked to send their email address instead of a
password,[3] no verification is actually performed on the supplied data.[10]
Many FTP hosts whose purpose is to provide software updates will allow
anonymous logins.[3]
NAT and firewall traversal
FTP normally transfers data by having the server connect back to the client,
after the PORT command is sent by the client. This is problematic for both
NATs and firewalls, which do not allow connections from the Internet towards
internal hosts.[11] For NATs, an additional complication is that the
representation of the IP addresses and port number in the PORT command refer
to the internal host's IP address and port, rather than the public IP address
and port of the NAT.
There are two approaches to solve this problem. One is that the FTP client
and FTP server use the PASV command, which causes the data connection to be
established from the FTP client to the server.[11] This is widely used by
modern FTP clients. Another approach is for the NAT to alter the values of
the PORT command, using an application-level gateway for this purpose.[11]
Differences from HTTP
HTTP essentially fixes the bugs in FTP that made it inconvenient to use for
many small ephemeral transfers as are typical in web pages.
FTP has a stateful control connection which maintains a current working
directory and other flags, and each transfer requires a secondary connection
through which the data are transferred. In "passive" mode this secondary
connection is from client to server, whereas in the default "active" mode
this connection is from server to client. This apparent role reversal when in
active mode, and random port numbers for all transfers, is why firewalls and
NAT gateways have such a hard time with FTP. HTTP is stateless and
multiplexes control and data over a single connection from client to server
on well-known port numbers, which trivially passes through NAT gateways and
is simple for firewalls to manage.
Setting up an FTP control connection is quite slow due to the round-trip
delays of sending all of the required commands and awaiting responses, so it
is customary to bring up a control connection and hold it open for multiple
file transfers rather than drop and re-establish the session afresh each
time. In contrast, HTTP originally dropped the connection after each transfer
because doing so was so cheap. While HTTP has subsequently gained the ability
to reuse the TCP connection for multiple transfers, the conceptual model is
still of independent requests rather than a session.
When FTP is transferring over the data connection, the control connection is
idle. If the transfer takes too long, the firewall or NAT may decide that the
control connection is dead and stop tracking it, effectively breaking the
connection and confusing the download. The single HTTP connection is only
idle between requests and it is normal and expected for such connections to
be dropped after a time-out.
Web browser support
Most common web browsers can retrieve files hosted on FTP servers, although
they may not support protocol extensions such as FTPS.[3][12] When an FTP—
rather than an HTTP—URL is supplied, the accessible contents on the remote
server are presented in a manner that is similar to that used for other web
content. A full-featured FTP client can be run within Firefox in the form of
an extension called FireFTP.
Syntax
FTP URL syntax is described in RFC 1738, taking the form:
ftp://[user[:password]@]host[:port]/url-path (the bracketed parts are
optional).
For example, the URL
ftp://public.ftp-servers.example.com/mydirectory/myfile.txt represents the
file myfile.txt from the directory mydirectory on the server
public.ftp-servers.example.com as an FTP resource. The URL
ftp://user001:secretpassword@private.ftp-servers.example.com/mydirectory/myfile.txt
adds a specification of the username and password that must be used to access
this resource.
More details on specifying a username and password may be found in the
browsers' documentation (e.g., Firefox[13] and Internet Explorer[14]). By
default, most web browsers use passive (PASV) mode, which more easily
traverses end-user firewalls.
Some variation has existed in how different browsers treat path resolution in
cases where there is a non-root home directory for a user.[15]
Security
FTP was not designed to be a secure protocol, and has many security
weaknesses.[16] In May 1999, the authors of RFC 2577 listed a vulnerability
to the following problems:
Brute force attack
FTP bounce attack
Packet capture
Port stealing (guessing the next open port and usurping a legitimate
connection)
Spoofing attack
Username enumeration
FTP does not encrypt its traffic; all transmissions are in clear text, and
usernames, passwords, commands and data can be read by anyone able to perform
packet capture (sniffing) on the network.[2][16] This problem is common to
many of the Internet Protocol specifications (such as SMTP, Telnet, POP and
IMAP) that were designed prior to the creation of encryption mechanisms such
as TLS or SSL.[4]
Common solutions to this problem include:
Using the secure versions of the insecure protocols, e.g., FTPS instead
of FTP and TelnetS instead of Telnet.
Using a different, more secure protocol that can handle the job, e.g. SSH
File Transfer Protocol or Secure Copy Protocol.
Using a secure tunnel such as Secure Shell (SSH) or virtual private
network (VPN).
FTP over SSH
FTP over SSH is the practice of tunneling a normal FTP session over a Secure
Shell connection.[16] Because FTP uses multiple TCP connections (unusual for
a TCP/IP protocol that is still in use), it is particularly difficult to
tunnel over SSH. With many SSH clients, attempting to set up a tunnel for the
control channel (the initial client-to-server connection on port 21) will
protect only that channel; when data is transferred, the FTP software at
either end sets up new TCP connections (data channels) and thus have no
confidentiality or integrity protection.
Otherwise, it is necessary for the SSH client software to have specific
knowledge of the FTP protocol, to monitor and rewrite FTP control channel
messages and autonomously open new packet forwardings for FTP data channels.
Software packages that support this mode include:
Tectia ConnectSecure (Win/Linux/Unix)[17] of SSH Communications
Security's software suite
Derivatives
FTPS
Main article: FTPS
Explicit FTPS is an extension to the FTP standard that allows clients to
request FTP sessions to be encrypted. This is done by sending the "AUTH TLS"
command. The server has the option of allowing or denying connections that do
not request TLS. This protocol extension is defined in RFC 4217. Implicit
FTPS is an outdated standard for FTP that required the use of a SSL or TLS
connection. It was specified to use different ports than plain FTP.
SSH File Transfer Protocol
Main article: SSH File Transfer Protocol
The SSH file transfer protocol (chronologically the second of the two
protocols abbreviated SFTP) transfers files and has a similar command set for
users, but uses the Secure Shell protocol (SSH) to transfer files. Unlike
FTP, it encrypts both commands and data, preventing passwords and sensitive
information from being transmitted openly over the network. It cannot
interoperate with FTP software.
Trivial File Transfer Protocol
Main article: Trivial File Transfer Protocol
Trivial File Transfer Protocol (TFTP) is a simple, lock-step FTP that allows
a client to get a file from or put a file onto a remote host. One of its
primary uses is in the early stages of booting from a local area network,
because TFTP is very simple to implement. TFTP lacks security and most of the
advanced features offered by more robust file transfer protocols such as File
Transfer Protocol. TFTP was first standardized in 1981 and the current
specification for the protocol can be found in RFC 1350.
Simple File Transfer Protocol
Simple File Transfer Protocol (the first protocol abbreviated SFTP), as
defined by RFC 913, was proposed as an (unsecured) file transfer protocol
with a level of complexity intermediate between TFTP and FTP. It was never
widely accepted on the Internet, and is now assigned Historic status by the
IETF. It runs through port 115, and often receives the initialism of SFTP. It
has a command set of 11 commands and support three types of data
transmission: ASCII, binary and continuous. For systems with a word size that
is a multiple of 8 bits, the implementation of binary and continuous is the
same. The protocol also supports login with user ID and password,
hierarchical folders and file management (including rename, delete, upload,
download, download with overwrite, and download with append).
FTP commands
Main article: List of FTP commands
FTP reply codes
Main article: List of FTP server return codes
Below is a summary of FTP reply codes that may be returned by an FTP server.
These codes have been standardized in RFC 959 by the IETF. The reply code is
a three-digit value. The first digit is used to indicate one of three
possible outcomes — success, failure, or to indicate an error or incomplete
reply:
2yz – Success reply
4yz or 5yz – Failure reply
1yz or 3yz – Error or Incomplete reply
The second digit defines the kind of error:
x0z – Syntax. These replies refer to syntax errors.
x1z – Information. Replies to requests for information.
x2z – Connections. Replies referring to the control and data connections.
x3z – Authentication and accounting. Replies for the login process and
accounting procedures.
x4z – Not defined.
x5z – File system. These replies relay status codes from the server file
system.
The third digit of the reply code is used to provide additional detail for
each of the categories defined by the second digit.
FTP servers
Some popular open source and commercial FTP server implementations are:
FileZilla Server (Windows)
Pure-FTPd (Unix)
Vsftpd (Unix)
ProFTPd (Unix)
CrushFTP (Mac, Win, Linux)
Rumpus (Mac)
WingFTP (Mac, Win)
See also
Comparison of FTP client software
Comparison of FTP server software
Comparison of file transfer protocols
Curl-loader – FTP/S loading/testing open-source software
File eXchange Protocol (FXP)
File Service Protocol (FSP)
FTAM
FTPFS
List of FTP commands
List of FTP server return codes
List of FTP server software
Managed File Transfer
OBEX
Shared file access
TCP Wrapper
References
Forouzan, B.A. (2000). TCP/IP: Protocol Suite (1st ed.). New Delhi,
India: Tata McGraw-Hill Publishing Company Limited.
Kozierok, Charles M. (2005). "The TCP/IP Guide v3.0". Tcpipguide.com.
Dean, Tamara (2010). Network+ Guide to Networks. Delmar. pp. 168–171.
Clark, M.P. (2003). Data Networks IP and the Internet (1st ed.). West
Sussex, England: John Wiley & Sons Ltd.
"Active FTP vs. Passive FTP, a Definitive Explanation". Slacksite.com.
Archived from the original on 4 May 2011.
RFC 959 (Standard) File Transfer Protocol (FTP). Postel, J. & Reynolds,
J. (October 1985).
RFC 2428 (Proposed Standard) Extensions for IPv6, NAT, and Extended
Passive Mode. Allman, M. & Metz, C. & Ostermann, S. (September 1998).
Preston, J. (January 2005). Deflate transmission mode for FTP. IETF. I-D
draft-preston-ftpext-deflate-03.txt. Retrieved 27 January 2016.
Prince, Brian. "Should Organizations Retire FTP for Security?". Security
Week. Security Week. Retrieved 14 September 2017.
RFC 1635 (Informational) How to Use Anonymous FTP. P. & Emtage, A. &
Marine, A. (May 1994).
Gleason, Mike (2005). "The File Transfer Protocol and Your Firewall/NAT".
Ncftp.com.
Matthews, J. (2005). Computer Networking: Internet Protocols in Action
(1st ed.). Danvers, MA: John Wiley & Sons Inc.
"Accessing FTP servers | How to | Firefox Help". Support.mozilla.com.
2012-09-05. Retrieved 2013-01-16.
"How to Enter FTP Site Password in Internet Explorer".
Support.microsoft.com. 2011-09-23. Retrieved 2015-03-28. Written for IE
versions 6 and earlier. Might work with newer versions.
Jukka “Yucca” Korpela (1997-09-18). "FTP URLs". "IT and communication"
(www.cs.tut.fi/~jkorpela/). Retrieved 2016-01-06.
"Securing FTP using SSH". Nurdletech.com.
"Access using SSH keys & PCI DSS compliance". ssh.com.
Further reading
RFC 697 – CWD Command of FTP. July 1975.
RFC 959 – (Standard) File Transfer Protocol (FTP). J. Postel, J.
Reynolds. October 1985.
RFC 1579 – (Informational) Firewall-Friendly FTP. February 1994.
RFC 1635 – (Informational) How to Use Anonymous FTP. May 1994.
RFC 1639 – FTP Operation Over Big Address Records (FOOBAR). June 1994.
RFC 1738 – Uniform Resource Locators (URL). December 1994.
RFC 2228 – (Proposed Standard) FTP Security Extensions. October 1997.
RFC 2389 – (Proposed Standard) Feature negotiation mechanism for the
File Transfer Protocol. August 1998.
RFC 2428 – (Proposed Standard) Extensions for IPv6, NAT, and Extended
passive mode. September 1998.
RFC 2577 – (Informational) FTP Security Considerations. May 1999.
RFC 2640 – (Proposed Standard) Internationalization of the File Transfer
Protocol. July 1999.
RFC 3659 – (Proposed Standard) Extensions to FTP. P. Hethmon. March 2007.
RFC 5797 – (Proposed Standard) FTP Command and Extension Registry. March
2010.
RFC 7151 – (Proposed Standard) File Transfer Protocol HOST Command for
Virtual Hosts. March 2014.
IANA FTP Commands and Extensions registry – The official registry of FTP
Commands and Extensions
External links
Communication Networks/File Transfer Protocol at Wikibooks
FTP Server Online Tester Authentication, encryption, mode and
connectivity.
vte
Uniform Resource Identifier (URI) schemes
Official
about acct crid data file ftp geo gopher http https info ldap mailto nfs
nntp sip / sips tag tel telnet urn view-source ws / wss xmpp
Unofficial
coffee ed2k feed finger irc / irc6 / ircs ldaps magnet rsync ymsgr
Protocol list
Categories:
File Transfer ProtocolApplication layer protocolsClear text
protocolsComputer-related introductions in 1971History of the
InternetInternet StandardsNetwork file transfer protocolsUnix network-related
software
Navigation menu
Not logged in
Talk
Contributions
Create account
Log in
Article
Talk
Read
Edit
View history
Search
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikipedia store
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact page
Tools
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Wikidata item
Cite this page
Print/export
Create a book
Download as PDF
Printable version
In other projects
Wikimedia Commons
Languages
?????
Es+鹆
作者: eeeabd () 看板: Test
標題: Re: [測試] 測uii
時間: Fri Jan 11 09:40:17 2019
hhhy
--
※ 發信站: 批踢踢實業坊(ptt.cc), 來自: 59.102.169.115
※ 文章網址: https://www.ptt.cc/bbs/Test/M.1547170819.A.C02.html
→
01/11 09:40,
7年前
, 1F
01/11 09:40, 1F
→
01/11 09:41,
7年前
, 2F
01/11 09:41, 2F
꾏
※ 編輯: eeeabd (59.102.169.115), 01/11/2019 09:42:37
※ 編輯: eeeabd (59.102.169.115), 01/11/2019 10:39:39
※ 編輯: eeeabd (59.102.169.115), 01/11/2019 11:50:26